eZ Community » Forums » Discussions » Migrating from eZ Publish 4 to eZ...
expandshrink

Tuesday 17 December 2013 3:21:45 pm - 8 replies

» Read full blog post

Introduction

Architecturally, eZ Publish 5 is not a simple evolution but a revolution. eZ Publish 5 is based on the Symfony2 PHP framework and completely changes how you develop an eZ Publish website in a powerful and fun way. All versions of eZ Publish 5 take a dual-kernel approach that enables developers to work in both the “new stack” and the “legacy stack” at the same time. This ensures backwards compatibility and helps make the migration process to the new stack as smooth as possible.

This blog series is for existing eZ Publish 4 (or eZ Publish 5 legacy stack) users who are familiar with key eZ Publish concepts and are looking at migrating to the new stack in eZ Publish 5. In this series, we will explore how to migrate your legacy stack extensions to the new stack. We will explain the core new concepts and highlight the differences when compared to the legacy stack.

Wednesday 18 December 2013 2:44:46 pm

In addition to what is mentioned in this post, it's also possible since 5.2/2013.7 to use a custom controller to display a content or a location. This is a very interesting extension point and which also helps getting rid of the fetch functions.

Modified on Wednesday 18 December 2013 2:46:16 pm by Damien Pobel

Wednesday 18 December 2013 2:53:46 pm

I just can't use the translation system, I don't know how to configure ez to set the default locale just for the current siteaccess. I can translate the content objects but not the template strings, it uses my default locale, unless I set it calling a function in php to set the default locale. I would like to know where can I set the locale for a certain siteaccess, not the default locale.

Modified on Wednesday 18 December 2013 3:03:00 pm by Thiago Campos Viana

Friday 20 December 2013 3:17:21 pm

Hi Lukasz

Thanks for this informative post. One thing that's worth mentioning is the View provider configuration, which resembles the override mechanism of eZ 4. Together with the possibility to use a custom controller for a location (as Damien pointed out), you have a unprecedented flexibility.

One learning from a large project which we just finished is that you will likely end up with a custom controller for each content type full view.

Regards,
Donat

Friday 20 December 2013 4:05:15 pm

Quote from Donat Fritschy :

One learning from a large project which we just finished is that you will likely end up with a custom controller for each content type full view.

How did you find it ? I mean writing a custom controller is a breeze, but was it simple enough to use ? I'm curious happy.gif Emoticon

Friday 20 December 2013 4:59:29 pm

Well, we had proficient Symfony programmers writing the stuff blunk.gif Emoticon

They felt at home with eZ 5 very easily. But actually they first produced an abstract controller to eliminate much of the redundancy and verbosity present in the demo bundle.

The demo bundle has much improved, but I wish it would evolve towards best practices - the redundancies in code and settings are not the best guidelines for migrants from the eZ 4 world.

Friday 20 December 2013 5:01:36 pm

Thanks Donat, very useful feedback happy.gif Emoticon

Monday 23 December 2013 11:22:33 am

Very useful indeed.

Our objective regarding the demo bundle really is to make it the de facto reference when it comes to integrating features and following best practices.

We really welcome any suggestion or pull request, even if it's just a proof of concept, and it is clear that this goal can not be reached unless we get feedback from the actual demobundle's target: developers and integrators.

Please keep it coming, we can take it blunk.gif Emoticon

Tuesday 31 December 2013 3:16:21 pm

There is a presentation at slideshare about this topic:

http://www.slideshare.net/lserwatka/migrating-ez?from_search=1

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from