ezPublish vs Drupal vs Joomla and Typo3

Next topic

Author	Message
Rana Faheem	Monday 21 April 2008 11:48:49 pm Hello All, Some people think ezPublish is not bad. But ezPublish is complex to learn and theming not so friendly yet. and in Joomla too many code errors and incompatibilities between modules installed. Joomla has many inter-operating problems with the modules developed as well as between them too. and in general Typo3 a bit too big... and complex for most sites being produced. and Drupal 5 has an amazing support team and the community is so much friendlier overall and it has tons of documentation and always someone friendly to answer.A great support from the developers community towards the Drupal team. I want to ask the detail comparison of all these and which one is the best in all and why? Finally what is the future of ezpublish developer? With Regards Rana Amir Faheem
Carlos Revillo	Tuesday 22 April 2008 3:04:19 am Months ago there was another discussion about this, especially for Drupal and Ez. http://ez.no/developer/forum/general/ez_publish_vs_drupal/re_ez_publish_vs_drupal__5 There, I said that for some things drupal could be better and ez could be better for others. But now i'm very dissapointed with Drupal. They have released a new version, but api have changed totally from the previous version. The good thing about drupal is all that stuff developed by users around the world. but, it you want to upgrade to a new (and sure better versions) and you have a lot of contribs downloaded or maybe you have done your ones, you will need to change ALL OF THEM. and i'm not talking about a few changes. i'm talking about changing everything... Other things i don't like is how content and presentation are mixed. I mean. let's suppose you want a front page with the last two content you have created. in ez you'll do a fetch and with some parameters yo get only that two last. in drupal, even if you only want two, core looks for the last ten. so, even if you want a design with only two, drupal are quering internally for ten... And also in ez you have "siteaccess". and by default you have your "admin" part and your "public" part of the site. in drupal you don't. you need to add a module and telling to change the theme by the url, and be sure to add any new admin modules you create to that "list of urls who need to be shown with admin theme". I haven´t work so much with joomla, but every time i tried i didn´t find any module for creating new content classes. in drupal you have that cck wonderful module, and in ez this posibility is the core, but where is in joomla? i have tried with typo3 also, but no su much. i think is more difficult to learn than ezpublish, but its just only an impression... Nowadays i prefer eZ.
Rana Faheem	Monday 28 April 2008 4:11:41 am Hello all, Any one who wants to add some more words to make the difference very clear. with regards Rana Amir Faheem
Robin Muilwijk	Monday 05 May 2008 1:10:13 pm Hi, I've been focusing on all the cms'es for several years now. They are hard to compare. I never really liked typo3 because it is complex to setup and use. Joomla! is easy in both setup and use but lacking very important features. Drupal has a lot of features but is missing a true framework, and is not OO coded. Also, as mentioned before, it is not backward compatible with there last release. eZ Publish however has all the features you might want/need, has a framework and can do basically everything all the other cms'es can do. Again, they are hard to compare. You would need to make a proper selection for every project your start, which cms will fit all the needs. Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation. LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk
Betsy Gamrat	Monday 26 May 2008 8:22:17 pm As stated earlier, the best solution probably varies by project. I think eZ's greatest strength is that in a single download, you have an extremely robust CMS with the most commonly required functionality, and the support is excellent. All CMSs that are assembled from community contributed components have the following disadvantages: Potential for version conflicts, both with the core and between components Potential lack of a system level strategy for graceful integration Potential for more varied code, because the code is not from a single source, it may create a greater learning curve. Variations include quality, performance, support, security. eZ is extensible. If you want to add to it, you can, either by downloading from the community (same version issues may apply), or writing your own.