Community & Support

EDIPRESSE (an international media company with more than 180 newspapers in the world) launch two major new website under DRUPAL

EDIPRESSE (an international media company with more than 180 newspapers in the world) launch yesterday 2 majors website under DRUPAL :

http://www.24heures.ch

and

http://www.tdg.ch

It's a migration from EzPublish to Drupal after only 1 1/2 year of EzPublish's experience and Drupal win easily the match between the two cms : general performance are excellent and users are happy with it.

For the moment, EDIPRESSE SWISS have 2 others website under DRUPAL :

An another eZpublish's migration to Drupal :

http://www.femina.ch

and (new website).

http://www.lesquotidiennes.com

and we will continue to produce new website with this excellent CMS.

PS :
After only 2 years of experience, no more media big edipresse website are now under eZpublish :
LeMatin.ch switch in March from eZpublish to an swiss's solution handled by IOMEDIA (http://www.iomedia.ch)
Femina.ch switch in February from eZpublish to Drupal.
24 heures.ch switch now from eZpublish to Drupal
Tdg.ch switch now from eZpublish to Drupal
Bilan.ch is made with the help of the wordpress but will move to Drupal in few months.

Comments

Added to the list

wow this is great. I've had

wow this is great. I've had ezpublish on the back burner as a possibility for a while now due to their supposedly superior office integration, document management, and the new media handling stuff. I'd be very curious to hear more details about the specifics of what caused you to leave ezpublish and start using drupal.

===
"Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime."
-- Lao Tzu
"God helps those who help themselves." -- Benjamin Franklin
"Search is your best friend." -- Worldfallz

_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.

The main reason to migrate from eZpublish to Drupal are :

- Performance's problem : the Database structure of eZpublish is too "macro". He want to do a lof of thing and do it bad. A lot of queries are automatically built and procude SQL queries wich are heavy and long (some take some Mo).

We used the cluster system of eZpublish. It's a way for them to handle load balancing putting all in two separate table (one is indexing and the other is the content)........this base with 24heures and Tribune de Geneve have more than 40 GB of data in one table with MySQL.

When you add big and heavy queries with an heavy table you have a big problem.

A funny thing : our server with the old application serving few visitors (all the users who have the old IP, less than 1% of the traffic) have now the same load of our new server with DRUPAL serving 70.000 visitors with the same kind of the server and without load balancing.

After you can ask " but the cache system " ?

The cache system of eZpublish with an heavy "refresh" website is clearly not OK.

It's a clusterised (again) cache system and eZpublish use big queries with its own templating language system forcing PHP to parse string with heavy quantity. It means that we had big memory problem with 8 GB RAM 'server with our frontend. Each applicative modification where we wanted to "decache" (let's appear the thing in the front end) produce an heavy load othe front end server and an heavy load of the database.

For us - we are a team of experienced technical people (10 years exprience of open source programming , we worked at AOL, ORANGE ect..) it was the worst nightmare of our professional life : users not happy, website crashing, server crashing ect...

DRUPAL and for our users is a delivrance.

Cluster and eZ Publish the right way

The actual cluster implementation of eZ Publish might not be a highlight. Fortunately, you're not forced to use the standard cluster implementation. There is an alternative:
http://www.ymc.ch/weblog/some_due_modifications_to_the_ez_cluster

eZ Publish was never built to provide commodity functions out of the box. It is rather a framework, then a one-click-install CMS. So it's not right to compare plain Drupal to plain eZ Publish, but what you can build on top of the systems.