Page History

You have different options to avoid this:

1. Migrate your pagelayout to Platform stack, in order to be able to disable legacy mode and take advantage of HttpCache
   • In this setup, any kind of content type which is missing override rules in Platform stack, eZ Publish will always fallback to the legacy kernel, looking for a legacy template.
   • Same goes for custom legacy modules, if URL's are not handled by Symfony or by url alias, fallback goes to legacy for handling the url.
     
   However legacy admin will still be affected as it's in legacy mode, so the recommendation is to consider this in combination with next point.
2. Upgrade to PHP 7, in order to hide the performance degradation and as a bonus reduce memory by half and gain 1.5-2x performance on Symfony routes.
   This avoids editors complaining about the slower backend and allows you to gradually do step 1 across several SiteAccesses. This can be done in one of two ways:
   1. Update to latest 5.4.x release in order to be able to use PHP 7.0 with a version of eZ Publish which has been made compatible with PHP7.
   2. Or: Upgrade to eZ Platform v22.5LTS, install the legacy bridge and continue to use legacy admin, get an with it comes eZ Publish legacy 2017/82019.x 03 release which supports PHP 7.1 and higher, but for that .
      In both cases you'll need to adapt your eZ Publish legacy PHP code a bit.for PHP 7 changes (7.0, 7.1, 7.2, 7.3)
3. Last resort "Pure Legacy": Point web server directly at eZ Publish legacy, lose access to all Symfony/Platform/Legacy-bridge feature-set in order to postpone dealing with options above.
   In this setup you use ezpublish_legacy/ folder as your DocumentRoot, meaning the installs will have 99.9% the same behavior as 4.x with except changes done to deprecated features.
   Recommended for: Large projects coming from 4.x and which first needs to bring legacy code base as a small effort up to 5.x legacy, before evaluating further steps either on 5.x or to eZ Platform with or without Legacy Bridge.
   Not recommended for: Future compatibility, as this is "pure legacy" setup (see Architecture) it will not be officially supported in the future on either eZ Platform or eZ Platform Cloud.