...
Summary on the ways to use eZ Publish 5
| Anchor | ||||
|---|---|---|---|---|
|
Using eZ Publish 5 in "pure legacy" setup
...
In this way, your vhost is setup to go directly to legacy stack, and developers will see almost no differences.
| Tipwarning |
|---|
In this setup you can not use any of the new Symfony and or Platform features as the , and legacy bundle ( "bridge") is will not be used used for integrating the two system together. So this is more of a first step toward eZ Platform, getting your legacy code to work with eZ Publish 5.x. If you choose this because of performance concerns setting up a combined setup, recommendation is to move to PHP 7.x when moving to Platform setup which will result in a overall faster setup then a pure legacy setup on PHP 5.x. |
...
, see our recommendations in Legacy code and features on how to alternatively handle those. |
Anchor Usingezpublish5.0throughthelegacystackbutrelyingonthenewcontrollerandnewtemplatesystemaswellasthenewkernel. Usingezpublish5.0throughthelegacystackbutrelyingonthenewcontrollerandnewtemplatesystemaswellasthenewkernel.
Using eZ Publish 5 with both legacy & platform stack to start to take advantage
This way offers a transition and allows to combine old template and new templates in the same application. In this case, the users will rely on the administration interface of eZ Publish as well as on the ez tool bar for front-end editing, through the legacy templates, but the front end will be either based on legacy or new twig based templates.
...
In this model, the two kernels can be used and the system can this way benefit from the Public API and the new REST API built on top.
| Tip |
|---|
This setup can be configured in "legacy mode" per siteaccess, if enabled legacy handles dynamic url alias lookups and page layout handling, it's what is used out of the box where admin is configured in this mode and demo frontend is not. See Legacy code and features for how to take advantage of this for gradual transition your siteaccesses. |
...