This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit ezplatform.com

eZ Community » Forums » General » eZ Publish 4 or eZ Publish 5 in...
expandshrink

eZ Publish 4 or eZ Publish 5 in legacy mode?

eZ Publish 4 or eZ Publish 5 in legacy mode?

Friday 21 June 2013 1:59:37 pm - 8 replies

Hello,

I start a new project soon and I have not time to put myself in Symfony and Twig.

Which version do you recommend between eZ Publish4 (2012.6) and eZ Publish5 (2013.06) in legacy mode?

Thanks

Modified on Friday 21 June 2013 2:06:34 pm by Matthieu MORATILLE

Monday 24 June 2013 7:24:30 am

Hello Matthieu,

I would recommend using the very latest community build (2013.06)! You really want the latest build to take advantage of all the thousands of bugfixes made since the last eZ Publish 4 build.

You can use just the legacy stack part until you are ready to use the newer symfony based ezpublish5 stack.

I did a site where I just pulled out the legacy stack and used it stand alone because we were not ready for the project to use ezpublish5 symfony stack.

I hope this helps!

Cheers,
//kracker

Theme: K.Flay - Don't Wait Up ...
Mirror: https://soundcloud.com/kflay/k-flay-dont-wait-up

Monday 24 June 2013 9:24:31 am

Hello //kracker,

Thank you very much, it fully meets my question.

eZ Publish 5 here I come!

Monday 24 June 2013 2:52:57 pm

Your welcome Matthieu! Happy to help. I hope you enjoy eZ Publish 5 it's truly great!

Cheers,
//kracker

Theme: K.Flay - Appetite For Consumption ...
Mirror: https://soundcloud.com/kflay/k-flay-appetite-for

Tuesday 25 June 2013 4:14:27 pm

Last question, eZ Publish works with legacy stack so I specify my DocumentRoot to ezpublish_legacy folder?

I did not need to put the link assets?

Thanks

Modified on Tuesday 25 June 2013 5:01:53 pm by Matthieu MORATILLE

Wednesday 26 June 2013 1:48:51 pm

Hello Matthieu!

You can do this a number of ways but until you want to use the symfony stack I suggest strongly assigning the DocumentRoot to the ezpublish_legacy folder directly.

This way you are -only- dealing with the ezpublish_legacy stack directly without any other confusion.

I think the 'link assets' you refer to are a symfony stack term / idea. In eZ Publish Legacy those would be design folder assets and handled much more differently. I put things like favicon.ico, images, stylesheets, javascript, custom web fonts, etc all in the design folder for use within an eZ Publish Legacy website.

I hope this helps ...

Cheers,
//kracker

Theme: K.Flay - No ...
Mirror: https://soundcloud.com/kflay/k-flay-no

Thursday 27 June 2013 11:31:37 am

To further add on top of the detailed explanation by cracker: no, you do not need to link any assets when using only legacy stack:

- put design elements inside designs, possibly inside extensions

- use the good ole rewrite rules for eZ4 in your vhost (or .htaccess; vhost preferred)

- no need to run any symfony console command

Thursday 27 June 2013 11:31:50 am

Hello //kracker,

Thank you very much again.

I have all my answers.

Thursday 25 July 2013 9:56:28 am

The reply has been removed because of violation of forum rules.

expandshrink

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

36 542 Users on board!

Forums menu

Proudly Developed with from