This repository was archived by the owner on Sep 16, 2021. It is now read-only.
File tree Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Original file line number Diff line number Diff line change @@ -30,6 +30,9 @@ the ``SeoMetadata``::
30
30
}
31
31
}
32
32
33
+ If you are using PHP5.4+ you may also benefit from using the trait ``SeoAwareTrait ``
34
+ to plug these behavior into your model.
35
+
33
36
Now you can set some SEO data for this ``Page `` using the metadata::
34
37
35
38
use Acme\SiteBundle\Document\Page;
@@ -220,7 +223,7 @@ object:
220
223
</entity >
221
224
</doctrine-mapping >
222
225
223
- You can also choose to put the ``SeoMetadata `` class into a seperate table. To
226
+ You can also choose to put the ``SeoMetadata `` class into a separate table. To
224
227
do this, you have to enable ORM support just like you enabled PHPCR enabled
225
228
above and add a OneToOne or ManyToOne relation between the content entity and
226
229
the ``SeoMetadata `` entity.
@@ -233,15 +236,15 @@ form type can be used in forms to edit the ``SeoMetadata`` object.
233
236
234
237
.. caution ::
235
238
236
- The bundles requires the `BurgovKeyValueFormBundle `_ when using the form
239
+ The bundle requires the `BurgovKeyValueFormBundle `_ when using the form
237
240
type. Make sure you install and enable it.
238
241
239
242
Sonata Admin Integration
240
243
------------------------
241
244
242
245
Besides providing a form type, the bundle also provides a Sonata Admin
243
246
Extension. This extension adds a field for the ``SeoMetadata `` when an admin
244
- edits an objec that implements the ``SeoAwareInterface `` in the Sonata Admin
247
+ edits an object that implements the ``SeoAwareInterface `` in the Sonata Admin
245
248
panel.
246
249
247
250
.. caution ::
You can’t perform that action at this time.
0 commit comments