eZPublish vs. Drupal - community.ez.no

Monday 14 March 2011 11:26:13 am - 23 replies

Introduction

I have encountered a big deal of discussions abut eZP vs. Drupal, all of them stating different facts and opinions. So I hope this will shed some light on the topic...

» Read full blog post

23 replies

Author	Message
ekes black	Sunday 20 March 2011 2:40:38 pm " Betsy... As far as I've looked Drupal also supports many of this key advantages that you listed. It's true that some of them are supported only in Drupal 7 which was released about two months ago, but it deos have them. As for the version conflicts and upgrade problems I found many different sources (that are more objective than me) stating that upgrade in Drupal can be more diffcult than in eZ. The Drupal team itself and the founder of Drupal, state that they don't preserve backwards compatibility: http://drupal.org/node/65922 http://buytaert.net/backward-compatibility which is something that I personally disagree with. Very, very much disagree. " Yes agree that lots are now in core of 7; but were in contributory modules in 6. The version upgrade thing is true too. If you are a module maintainer you have to update your module, depending on which bits of the Drupal API have changed this can be a major change: some idea of the changes http://drupal.org/node/394070 (coder module is a code style review module - and it does an upgrade suggestion). You then need to write a path for your modules users to upgrade. For the 5 to 6 switch this all took quite some time to be written. 6 to 7 has been much quicker, with more maintainers updating modules and writing an upgrade path, but there are still lots to do.
kirill starikov	Wednesday 30 March 2011 11:47:39 am please note that drupal 7 does not have a working taxonomy translation (at least of feb '11 when i checked it out) which makes its i18n features almost useless.
Christian Rößler	Thursday 31 March 2011 1:33:35 am I would like to add that I found eZPublish modules (content/edit, /) very ugly, very "scriptish" and not that object orientated and class based as praised everywhere. Sure, eZ has a bunchload of classes to work with, but still has a lot of areas which look like hell and where never touched since 1990 (my guess) and that makes it awful to work with - or extend. On the other hand - if you managed the steep learning curve - ez provides you with a solid structure to get something done. $0.02 Hannover, Germany eZ-Certified http://auth.ez.no/certification/verify/395613

Author

Message

ekes black

Sunday 20 March 2011 2:40:38 pm

Betsy... As far as I've looked Drupal also supports many of this key advantages that you listed. It's true that some of them are supported only in Drupal 7 which was released about two months ago, but it deos have them.

As for the version conflicts and upgrade problems I found many different sources (that are more objective than me) stating that upgrade in Drupal can be more diffcult than in eZ. The Drupal team itself and the founder of Drupal, state that they don't preserve backwards compatibility:

http://drupal.org/node/65922
http://buytaert.net/backward-compatibility

which is something that I personally disagree with. Very, very much disagree.

Yes agree that lots are now in core of 7; but were in contributory modules in 6.

The version upgrade thing is true too. If you are a module maintainer you have to update your module, depending on which bits of the Drupal API have changed this can be a major change: some idea of the changes http://drupal.org/node/394070 (coder module is a code style review module - and it does an upgrade suggestion). You then need to write a path for your modules users to upgrade. For the 5 to 6 switch this all took quite some time to be written. 6 to 7 has been much quicker, with more maintainers updating modules and writing an upgrade path, but there are still lots to do.

kirill starikov

Wednesday 30 March 2011 11:47:39 am

please note that drupal 7 does not have a working taxonomy translation (at least of feb '11 when i checked it out) which makes its i18n features almost useless.

Christian Rößler

Thursday 31 March 2011 1:33:35 am

I would like to add that I found eZPublish modules (content/edit, */*) very ugly, very "scriptish" and not that object orientated and class based as praised everywhere. Sure, eZ has a bunchload of classes to work with, but still has a lot of areas which look like hell and where never touched since 1990 (my guess) and that makes it awful to work with - or extend.

On the other hand - if you managed the steep learning curve - ez provides you with a solid structure to get something done.

$0.02

Hannover, Germany
eZ-Certified http://auth.ez.no/certification/verify/395613

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

eZ debug

Timing:	Jan 30 2025 10:57:04
Script start
Timing:	Jan 30 2025 10:57:04
Module start 'layout'
Timing:	Jan 30 2025 10:57:04
Module start 'content'
Timing:	Jan 30 2025 10:57:04
Module end 'content'
Timing:	Jan 30 2025 10:57:04
Script end

Main resources:

Total runtime	0.0277 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	590.2813	151.0547
Module start 'layout'	0.0053	0.0044	741.3359	221.2188
Module start 'content'	0.0098	0.0162	962.5547	1,006.6172
Module end 'content'	0.0260	0.0017	1,969.1719	33.9766
Script end	0.0277		2,003.1484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	10.4201	14	0.0002
Check MTime	0.0011	3.8779	14	0.0001
Mysql Total
Database connection	0.0009	3.1348	1	0.0009
Mysqli_queries	0.0028	10.2051	3	0.0009
Looping result	0.0000	0.0473	1	0.0000
Template Total	0.0012	4.3	1	0.0012
Template load	0.0009	3.3834	1	0.0009
Template processing	0.0003	0.9374	1	0.0003
Override
Cache load	0.0007	2.4992	1	0.0007
General
dbfile	0.0041	14.7031	8	0.0005
String conversion	0.0000	0.0258	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs