Forums / Discussions / Why to choose eZ Publish CMS as a platform for web projects

Sunday 13 March 2011 8:35:59 am - 5 replies

Introduction

As an eZ Publish developer I am often asked to explain why we as a company work with eZ, why have we chosen eZ in the first place and why will we continue to work with it in the future. So I will try to summarize our reason. Dear reader, feel free to contribute with yours.

» Read full blog post

Author Message

H-Works Agency

Thursday 24 March 2011 12:51:39 am

Hello,

eZP is great, its true it can solve an impressive diversity of client's requests through its data model and extension features.

In the other hand i cannot agree with your next two assertion :

- Upgrade process is a nightmare and should be totally automated...i know what i am talking about after a 20 sites migration from 3.x to 4.x. Automation with dependency checking should happen for kernel & extensions (distrib & community).

- eZ override system is great and i discover every day the power of this feature. But its not clear : Loading order for design & settings have to appear somewhere in the debug - without loading unmaintainable extensions. When you load a setting extension stack on your website its very time consuming to find out why a certain variable is not correct because your extensions's loading order is wrong.

Cheers !

EZP is Great

Nicolas Pastorino

Thursday 24 March 2011 1:41:56 am

Quick 2 cents : for upgrades, http://projects.ez.no/ezupgrade is a must-try solution. Very impressive results, event on complex integrations like projects.ez.no.

Cheers,

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

Ivo Lukac

Monday 28 March 2011 12:41:30 pm

"

Hello,

eZP is great, its true it can solve an impressive diversity of client's requests through its data model and extension features.

In the other hand i cannot agree with your next two assertion :

- Upgrade process is a nightmare and should be totally automated...i know what i am talking about after a 20 sites migration from 3.x to 4.x. Automation with dependency checking should happen for kernel & extensions (distrib & community).

- eZ override system is great and i discover every day the power of this feature. But its not clear : Loading order for design & settings have to appear somewhere in the debug - without loading unmaintainable extensions. When you load a setting extension stack on your website its very time consuming to find out why a certain variable is not correct because your extensions's loading order is wrong.

"

- yes, we had issues with upgrades too. Mostly crossing from PHP4 to PHP5, but we know a lot of stories from other CMS on how they have upgrade issues, so these kind of issues are minor comparing to those

- we had some issues with extension order too :) but generally it works ok (we internally have set up procedures so the issue does not happen) and that is being worked on lately AFAIK. I agree that documentation should be more clearer.

http://www.linkedin.com/in/ivolukac
http://www.netgen.hr/eng/blog
http://twitter.com/ilukac

Gaetano Giunta

Tuesday 29 March 2011 1:22:39 am

About extension ordering: since version 4.4 extensions can specify their dependencies, which leads to a correct loading order, automatically calculated by eZ.

Little by little, we improve... ;-)

Principal Consultant International Business
Member of the Community Project Board

Ivo Lukac

Tuesday 29 March 2011 1:27:43 am

"

About extension ordering: since version 4.4 extensions can specify their dependencies, which leads to a correct loading order, automatically calculated by eZ.

Little by little, we improve... ;-)

"

So didn't get it wrong when I wrote: "and that is being worked on lately AFAIK" :)

http://www.linkedin.com/in/ivolukac
http://www.netgen.hr/eng/blog
http://twitter.com/ilukac

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