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

Versions Compared


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


note: missing integration doesn't mean the system can not use the feature in a new installation relying on the new stack, but if it needs, it shall rely on a fallback to the legacy stack and the legacy kernel. For instance: a website with a shop system could be done in twig and rely on legacy only for the fallback.

RatingUser Rating not currently supported by API, planned to be implemented later when some convention for FieldType provided API's are established
ShopNo shop or field(/data) types related to shop currently supported by API
Commentezcomments is not supported by API, and is not planned to be supported either. Instead of having it part of the API, we are replacing it in 5.2 with a bundle that will provide an agnostic system to integrate 3rd party comment services. It will out of the box show Disqus and Facebook integration but can also integrate other 3rd party as well as home made or even, why not, a port of the legacy eZ Comment system (which is not the way we will pursue for the product).
Content EditingContent editing module is not implemented yet, so currently only raw editing support needs to be implemented on top of REST/Public API directly or on top of the JS library that wrap the REST API and expose it to javascript code simply.
Module PermissionsController / Bundle Permissions is not integrated with eZ Publish permission system yet, currently standard Symfony firewall rules need to be used
UrlAlias RoutingUrlAlias has the same model as before and hence does not support routing directly to a bundle:controller:action
WorkflowPlanned for future version
Information CollectorPlanned to return as a new Form feature in future versions
Package systemPlanned to return as a import/export system which uses either API or SPI directly to replicate some or full amount of content from one repository to another
Menu managementCould be re introduced in the future as a multi site safe Site configuration feature
PDF ExportNot currently planned, should be re-implemented outside of Core
RSS feedsCurrently no API for managing RSS feeds
Frontend Editing

See "Content Editing".

Be aware that eZ Flow timeline feature is not available in the legacy admin (only in front end editing), hence not usable on the new stack.

SearchSearch API exists, but front end is currently using legacy fallback (ezfind) and 5.x Solr implementation is currently not finished yet
User moduleUser login, login handlers, change-password, forgot-password, register, profile and editing currently uses legacy fallback
Oauth 1oAuth 2.0/2oAuth 1.0 (REST)supported in REST v1, planned for new stack for future 5.x version.
Extensions(aka Bundles)
eZ TagsWe are working on either integrating more deeply eZ tags or rebuilding a solution as part of the API. (note: eZ Tags is not clearly supported in 4.x), still community supported in legacy stack on 5.x.
eZ SIeZ SI is purely legacy, not required in Symfony as it support ESI natively. We lost a differentiation for the Enterprise version here, still supported in legacy stack on 5.x.
eZ Content stagingNo equivalent yet on the new stack, still supported in legacy stack on 5.x.
eZ Style editorNo equivalent on the new stack. Because Mamut-like project it is not anymore our core focus, we will not reimplement as is but might build solutions on top of the theming support. It wont be similar., still supported in legacy stack on 5.x up until 5.1.
eZ SurveyNo equivalent yet on the new stack, still supported in legacy stack on 5.x.

Note: All missing features are still available in legacy stack bundled with eZ Publish 5.x, this fact sheet is purely about 5.x vs 4.x (legacy).

For additional on supported legacy features see: