Global navigation

 •  Documentation Center
 •  eZ Studio & eZ Platform
   •  User Manual
   •  Technical Manual
   •  Glossary
 •  eZ Publish 4.x / legacy

 
eZ Publish (5.x)

eZ Publish 5.x | For eZ Platform & eZ Studio topics see Technical manual and User manual, for eZ Publish 4.x and Legacy topics see eZ Publish legacy

Versions Compared

Old Version 12

changes.mady.by.user André Rømcke

Saved on

compared with

New Version Current

changes.mady.by.user André Rømcke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For a eZ Publish 4.x vs 5.x comparison, see here.

...

All Symonfy features are essentially working also in eZ Publish 5; this page describes features used out of the box however with limitations due to the eZ Publish 5 features developed on top, and features not used out of the box for a reason described here.

Limitations of eZ Publish 5 features:

FeatureSupportedNoteLimitations
ConfigurationAll configuration uses standard yml configuration
  1. Siteaccess (Semantic) configuration is something that has been built on top of Symfony
    1. Standard Services does do not support them
    2. They are not cached but lookup occures occurs based on cached Symfony configuration
  2. Unit tests currently use ini files and own configuration system
Dependency injectionInjection Supported for all services
  1. See known issues (eg. missing possibility to inject Criterion)
  2. Unit tests currently use own dependnecy dependency injection system driven by own ini system
SecurityOwn Firewall voter that uses eZ Publish user rights
  1. eZ User is not the same as a Doctrine provided user
  2. Limitations does do not apply at this stage but instead on at data retrieval time

Not

...

used out of the box

...

:

FeatureUnsupportedReason
Doctrine We don't currently use Doctrine DBAL, options: use Zeta Database/Persistence until we switch or be ok with several database connections. If the latter you can use it like described in symfony doc by adding doctrine/orm & doctrine/doctrine-bundle via composer and installs it like any other bundleORMWhile the full ORM is not used out of the box, as of 5.3 we use Doctrine DBAL making it possible to share connection and connection settings between eZ Publish and regular Doctrine ORM use.
AnnotationsWe don't currently bundle FrameworkExtraBundle which provides support for Annotating routes/firewall rules on controllers and other features, workaround. Workaround: customer can add it in composer and installs install it like any other bundle.