|
Author
|
Message
|
|
Ben Overmyer
|
Tuesday 19 October 2010 12:24:10 pm
In trying to upgrade from eZ Publish 4.0.1 to the latest version, it's taking my company way too long to just get our development mode upgraded. The convoluted mess of PHP scripts, database queries, and Apache modifications is simply unfriendly. Does "eZ" have any plans of ever making their product as easy to upgrade as, say, Wordpress, or are we doomed to a lifetime of usability nightmares?
|
|
kracker (the)
|
Tuesday 19 October 2010 12:39:12 pm
Well Hello you must be new to these here parts! Cause other wise you would know already that we are doomed. DOOOOOOOOMMMMEDDDD. //kracker
Member since: 2001.07.13 || http://ezpedia.se7enx.com/
|
|
Ben Overmyer
|
Tuesday 19 October 2010 12:44:33 pm
Oh dear.
|
|
Robin Muilwijk
|
Tuesday 19 October 2010 12:51:08 pm
Hello Ben, Can you elaborate on the problems that you encounter while upgrading? There are clear instructions with each release, and depending on the extensions and possible custom scripts it should not take too long to upgrade to another version. Have you also checked out the eZ Upgrade extension? See http://projects.ez.no/ezupgrade. Thanks and regards, Robin
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
|
|
Heath
|
Tuesday 19 October 2010 2:45:10 pm
I too am confused by your comments Ben. eZ Systems has really improved their documentation of eZ Publish scripts and the upgrade process over the years. These days it's simply fantastically written help through the entire process. Frankly I love doing eZ Publish upgrades because they are so well documented, straight forward and simple to understand. And if you never want to do upgrades yourself, buy a hosted solution from eZ Systems or a Community Partner. Cheers, Heath
Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org
|
|
Ben Overmyer
|
Wednesday 20 October 2010 12:31:19 pm
I'll clarify, then, though I was not aware of the ezupgrade project and that may invalidate my comments. We had the expectation of an upgrade process consisting of two steps: 1) Overwrite existing distribution files with upgrade files, and 2) Run upgrade scripts to upgrade the database Discovering that we needed to run a number of scripts and SQL queries, some of which apparently needed modification in order to even run without error (speaking specifically of system upgrade scripts from 4.0.3 to 4.1.x), was a bit of a shock.
|
|
Nicolas Pastorino
|
Thursday 21 October 2010 12:04:25 am
Hi Ben, I'd strongly recommend, as others did, to take a look at http://projects.ez.no/ezupgrade. It will transparently handle most of the upgrade complexity for you. The first time i saw this working (demo by Eirik at the eZ Conference in Berlin ), it literally got me to softly sing Queen's "Its a Kind of Magic" ... :) 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
|
|
kracker (the)
|
Thursday 21 October 2010 12:06:49 am
Ben, If that (above) is how you upgrade your going to run into problems. You must copy your existing custom extensions and override / siteacess settings -into- a fresh copy of eZ Publish. Which is different than what you described you were expecting. I've seen people who upgrade badly and they all eventually find out months later with corrupt or dirty installations of eZ. Be certain to follow the great upgrade documentation more closely as not to miss the intent of key steps throughout the process. Cheers, //kracker
Member since: 2001.07.13 || http://ezpedia.se7enx.com/
|
|
cliffp pratt
|
Tuesday 26 October 2010 3:46:21 pm
"
Ben, If that (above) is how you upgrade your going to run into problems. You must copy your existing custom extensions and override / siteacess settings -into- a fresh copy of eZ Publish. Which is different than what you described you were expecting. I've seen people who upgrade badly and they all eventually find out months later with corrupt or dirty installations of eZ. Be certain to follow the great upgrade documentation more closely as not to miss the intent of key steps throughout the process. Cheers, //kracker
"
I have trying to upgrade EZP from 3.8 to 4.2 for months. It is simply wrong to say that the upgrade documentation is 'great'. It is confusing and in places just plain wrong. As an example, the URL Alias migration stuff is messy and confusing.The steps necessary to do this migration are mentioned in several of the upgrade steps but should only be performed in one step. It is in the upgrade notes for 3.10 (3.10.x to 3.10.y). The steps are mentioned in the upgrade notes for Upgrading to 4.0 (4.0.x to 4.0.y). If you do run it twice the result is disaster! In any case, I can't possibly upgrade manually since it would take far too long. Even with a script to preform the steps it takes more than 8 hours, and the site is used 24x7. Having to edit database update scripts by hand is silly. It is not clear in the update notes what needs to be run and what can be skipped if you have done it in a previous step. Currently I am trying to work out why all objects become read-only, even to the admin when the system is upgraded from 4.0.7 to 4.1.4.There are steps left out too. I find the comment about the 'missing the intent of key stops' through the process ironically amusing. How is someone reading the documentation supposed to know the intent of the steps if it is not made explicit? Especially if they are touching eZPublish for the first time? I'm trying to use ezgrade now, having finally stumbled across it, but I can't get past step one: PHP Parse error: syntax error, unexpected ')', expecting '(' in /blahblah/ezupdate/classes/ezupgrade.php on line 716 Cheers, Cliff
|
|
Nicolas Pastorino
|
Wednesday 27 October 2010 8:42:09 am
Hi Cliff, Glad to see you got feedback on ezupgrade's forums ( http://projects.ez.no/ezupgrade/forum/general/parse_error ). Let us know how your marathon migration goes. 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
|
|
cliffp pratt
|
Wednesday 27 October 2010 8:25:05 pm
Nicolas, Let me get this straight. I have unbounded admiration for the people who write eZPublish, those who help people on the forums, those who write extensions and projects and additionally, those who do the documentation. I couldn't do it. As regards the upgrade process, I don't agree that it is simple and easy, BUT I admire those who have worked out how to get ordinary users from one release to another, easy or not. I'm not happy with people saying it is easy and advising people who find it hard to go elsewhere. My last comment on the matter. As regards ezupgrade, I am unsure about using it as I've already written some Perl scripts to do much the same, and it needs PHP4 and PHP5 CLI installed on the server. Currently I have some issues around that, because of the configuration of the server. When I get the server to 3.10.1 I may revisit the issue. Cheers, Cliff
|
|
Nicolas Pastorino
|
Thursday 28 October 2010 1:55:44 am
Hi and thanks for these kind words, I must confess upgrading eZ Publish is not straightforward, and might require some focus and time. Your case is a touch tougher even, since it involves system-level changes. Also, the upgrade processes by the 3.x generation were not as smooth as for the 4.1 and above versions. Captain obvious would repeat that once you will have reached the 4.1 bar, life will be much easier. 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
|
|
cliffp pratt
|
Thursday 28 October 2010 9:26:02 pm
Thanks Nicolas. The current problems I have relate to the 4.0.7 move to 4.1.4. But that's for another topic. Cheers, Cliff
|