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
September 15th 2015

eZ announces the availability of 5.4.5, a maintenance release available for all users of eZ Publish Platform 5.4.


5.4.5 is currently in public beta as it introduces new features, Solr search engine Bundle and new Recommendations Bundle, and as it is a beta and undergoing both internal and external testing it is not supported for use in production. 5.4.5-stable is planned to come out 1 month after the first beta, depending on feedback we get on these features.

For reporting issues, mark them as affecting "5.4.5-beta".

Installing the beta

To be able to get access to the beta you will have to change stability flag on affected/added packages (Solr and Recommendation are optional new packages):

After this has been done follow the 5.4.x Update Instructions to apply this update to your platforms, but after executing `composer update`, further actions are needed for Solr Search Engine Bundle, and Recommendation Bundle in order to correctly install them.


Highlights: New Features

This maintenance release introduces two new eZ Platform features to 5.4.x: Solr Search Engine Bundle and Recommendations Bundle, besides this there are several maintenance issues fixed as listed below both coming from support issues and pull requests from community.

Improved Search engine powered by Solr


New in 5.4.5, and part of the upcoming eZ Platform release this fall, is support for running API Search queries on top of Solr instead of SQL based search engine (specifically "Legacy" search/storage engine). As Search is essentially powering all Search and Querying ("fetch") operations in Platform stack (aka 5.x/Symfony stack), this specifically means you can expect much more stable performance from your searches and your system*, and much better possibility to scale out for your search needs using Solr.


'* See 5.x Architecture diagram for further information about how persistence load operations are cached by Persistence Cache, and Search queries now are delegated to Solr, meaning database is less affected by system load to mainly deal with content updates.

Further reading: Installation documentation for Solr Search Engine, developer info and source code in our Solr Search Engine Bundle repository, and further resources on Apache Solr.

Improved Recommendations integration

A new Recommendation Bundle has been made, completely changing how the service is done. Recommendations are now served directly from the Recommendations service, avoiding cache and load problems on your server that was a problem with the previous ezreco extension. Tracking has similarly been improved to track directly to Recommendations service, and aligns with how tracking is done with other solutions like Google Analytics.

This first iteration of Recommendation Bundle focuses on personal content recommendations with tracking of user traffic, tracking of user actions like shopping behaviour is possible using our Recommendations Service API.

Limitation: Recommendation Bundle currently requires Symfony 2.6 or greater so is limited to eZ Publish Platform 5.4.3+ and eZ Platform/Studio 15.07+. We plan to reduce this requirement to Symfony 2.3 so the bundle can be used with any version of eZ Publish Platform 5.1+.

Further reading: Documentation on our Recommendation Service, developer documentation and source code in our Recommendation Bundle repository.


Package Details

Resolving known issues

Being this release is a beta it contains some known issues that we are working on to document, and when possible to roll out as new updated beta tags via composer update as soon as we can.

Known for both Solr and Recommendation:

  • Exception if Binary files in database has invalid path prefix
    • Make sure ezpublish.yml configuration var_dir is configured properly, and that you specify siteaccess when indexing content for Solr via command line.
  • Exception on unsupported Field Types
    • Make sure to configure all FieldTypes (datatypes) in your installation as NullType
  • Content not immediately available 
    • Solr Search Engine Bundle is on purpose not committing changes on Repository updates, but letting you control this using Solr configuration.
      Adjust Solr autoSoftCommit to control this.
    • For Recommendation service same is the true, 

If you still have problems, pop into our Slack channel at to discuss.

Package updates

Here are the ezsystems packages that have received an update as part of this release:

packageversionprior version

Updates and fixes in this release

Key Summary T Created Updated
EZP-24915 Solr Search Engine: cleanup structure and use standard bundle naming Task Oct 07, 2015 Jan 20, 2016
EZP-24932 Add an optional locationId parameter to the contentView route Sub-task Oct 08, 2015 Oct 08, 2015
EZP-24804 Search: Implement Ancestor criterion Improvement Sep 14, 2015 Nov 27, 2016
EZP-24878 ezflow: Filter blocks per zone Improvement Sep 25, 2015 Oct 05, 2015
EZP-24933 Avoid loading API ContentType to validate Field SortClauses Improvement Oct 08, 2015 Oct 09, 2015
EZP-24952 HttpCache: Make X-User-Hash the same for "Anonymous" role and varnish. Improvement Oct 12, 2015 Oct 04, 2016
EZP-24504 Solr search engine fails to index images Bug Jun 15, 2015 Oct 28, 2015
EZP-24516 ezxmltext ampersands are incorrectly turned into htmlentities twice Bug Jun 17, 2015 Jan 12, 2016
EZP-24692 Video content object leaves unused video files on the server Bug Aug 05, 2015 Nov 17, 2015
EZP-24779 ezxmltext converter crashes on rendering links pointing to the non-exsiting URL IDs Bug Sep 08, 2015 Oct 15, 2015
EZP-24796 eZ Publish 5.4 installation documentation update with regards to security vulnerability CVE-2015-5723 Bug Sep 10, 2015 Apr 14, 2016
EZP-24809 Create documentation related to the upgrade of eZ Find (to 5.3 & 5.4) Bug Sep 15, 2015 Oct 21, 2015
EZP-24854 Varnish VCL banishing wrong node_ids Bug Sep 23, 2015 Apr 22, 2016
EZP-24867 Undefined offset when trying to build insconsistent content from SPI Bug Sep 24, 2015 Sep 28, 2015
EZP-24868 Autoload generation fails if "<ClassName>::class" is used in a parsed file Bug Sep 24, 2015 Sep 29, 2015
EZP-24889 Delayed indexing script crashes on large subtree move Bug Sep 28, 2015 Oct 01, 2015
EZP-24893 Delayed indexing breaks when a node is moved and then trashed Bug Sep 29, 2015 Oct 07, 2015
EZP-24897 First draft preview in eZ Publish 5.4.4 Bug Sep 30, 2015 Nov 23, 2015
EZP-24906 Link to pdf/list kernel module un breadcrumb is wrong Bug Oct 05, 2015 Oct 05, 2015
EZP-24918 Delayed indexing: moved nodes logic skips normal pending objects Bug Oct 07, 2015 Oct 15, 2015
EZP-24982 Generating links when previewing content in siteaccess with URI matching doesn't work Bug Oct 18, 2015 Jan 07, 2016
EZP-25014 Impossible to update a policy with no limitations Bug Oct 21, 2015 Oct 23, 2015
EZP-25019 Image aliases are always generated with the new path Bug Oct 22, 2015 Oct 28, 2015
EZP-25045 Wrong doc instruction on registering Solr Bundle Bug Oct 30, 2015 Nov 11, 2015
EZP-25053 The Dashboard refers the version as being 5.4.3 Bug Nov 03, 2015 Nov 09, 2015


  1. Regarding "5.4.5 is currently in public beta as it introduces new features":

    Will 5.4.4 upgrades be upgraded to 5.4.5 when running composer update ezsystems/ezpublish-kernel, or just to If so, how can be prevent upgrade to 5.4.5 for the month its beta?

  2. By default this should not be a problem. Meaning as long as your requirements and minimum stability flag in composer.json is not specifying a unstable version, you are fine. We have been tagging rc and beta tags for internal testing all the way back since 5.3.0, and these have been publicly avaiable for anyone that wants to test, only difference now is that we communicate on it as this release deserves some more widespread testing. Specifically we are looking for feedback on how Solr is performing compared to SQL for custom installations, and if RecommendationsBundle is covering the most important use cases.

    You can read more about Composer package versions and  stability here: