Global navigation

   Documentation Center
   eZ Studio & eZ Platform
     User Manual
     Technical Manual
   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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Current »


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:

ConfigurationAll configuration uses standard yml configuration
  1. Siteaccess (Semantic) configuration is something that has been built on top of Symfony
    1. Standard Services do not support them
    2. They are not cached but lookup 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 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 do not apply at this stage but instead at data retrieval time

Not used out of the box:

DoctrineWe don't currently use Doctrine DBAL. Available 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 install it like any other bundle.
AnnotationsWe don't currently bundle FrameworkExtraBundle which provides support for Annotating routes/firewall rules on controllers and other features. Workaround: customer can add it in composer and install it like any other bundle.
  • No labels