Download the PHP package perfectneeds/seo-single-lang-bundle without Composer
On this page you can find all versions of the php package perfectneeds/seo-single-lang-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download perfectneeds/seo-single-lang-bundle
More information about perfectneeds/seo-single-lang-bundle
Files in perfectneeds/seo-single-lang-bundle
Package seo-single-lang-bundle
Short Description Seo Bundle for Single language websites
License
Homepage http://perfectneeds.github.com
Informations about the package seo-single-lang-bundle
Getting Started With PNSeoBundle for single languages web apps
Prerequisites
- Symfony 3.4
- PNServiceBundle
Installation
Installation is a quick (I promise!) 7 step process:
- Download PNSeoBundle using composer
- Enable the Bundle in AppKernel
- Create your Seo class
- Create your SeoRepository class
- Configure the PNSeoBundle
- Import PNSeoBundle routing
-
Update your database schema
Step 1: Download PNSeoBundle using composer
Require the bundle with composer:
Step 2: Enable the Bundle in AppKernel
Require the bundle with composer:
Step 3: Create your Seo class
The goal of this bundle is to persist some Seo
class to a database. Your first job, then, is to create the
Seo
class for your application. This class can look and act however
you want: add any properties or methods you find useful. This is your
Seo
class.
The bundle provides base classes which are already mapped for most fields to make it easier to create your entity. Here is how you use it:
- Extend the base
Seo
class (from theEntity
folder if you are using any of the doctrine variants) - Map the
id
field. It must be protected as it is inherited from the parent class.
Caution!
When you extend from the mapped superclass provided by the bundle, don't redefine the mapping for the other fields as it is provided by the bundle.
In the following sections, you'll see examples of how your Seo
class should look, depending on how you're storing your seos (Doctrine ORM).
Note
The doc uses a bundle named SeoBundle
. However, you can of course place your seo class in the bundle you want.
Caution!
If you override the construct() method in your Seo class, be sure to call parent::construct(), as the base Seo class depends on this to initialize some fields.
Doctrine ORM Seo class
If you're persisting your seo via the Doctrine ORM, then your Seo
class should live in the Entity namespace of your bundle and look like this to start:
*You can add all relations between other entities in this class
php ymal
app/config/config.yml
doctrine: orm:
search for the "ResolveTargetEntityListener" class for an article about this
resolve_target_entities:
PN\SeoBundle\Entity\Seo: PN\Bundle\SeoBundle\Entity\Seo
pn_seo:
The fully qualified class name (FQCN) of the Seo class which you created in Step 3.
seo_class: PN\Bundle\SeoBundle\Entity\Seo
ymal
app/config/routing.yml
pn_seo: resource: "@PNSeoBundle/Resources/config/routing.yml" sh $ php bin/console doctrine:schema:update --force twig {% set seo = dynamicPage.seo %} {% use '@PNSeo/FrontEnd/seo.html.twig' %}
Reporting an issue or a feature request
---------------------------------------
Issues and feature requests are tracked in the [Github issue tracker](https://github.com/PerfectNeeds/seo-multi-lang-bundle).
When reporting a bug, it may be a good idea to reproduce it in a basic project
built using the [Symfony Standard Edition](https://github.com/symfony/symfony-standard)
to allow developers of the bundle to reproduce the issue by simply cloning it
and following some steps.
All versions of seo-single-lang-bundle with dependencies
symfony/framework-bundle Version ^4.4 || ^3.4
perfectneeds/service-bundle Version ~1.0