Forums / Developer / Tell Us about your experiances upgrading from 3.3 to 3.4

Tell Us about your experiances upgrading from 3.3 to 3.4

Next topic

Author	Message
Mark Gilbert	Friday 25 June 2004 3:00:21 pm I had some trouble trying to upgrade from 3.3 to 3.4. In fact I was unable to log in. After wroking on it for a while I reverted back to my 3.3 instilation. I wanted to know if anybody else has tried and what they had to deal with in getting it to work? Have customized any of your clasess, did you add any fields to say the article class or the product class? Have customized any of the kernal scripts? If so how did it go upgrading them? Did you have to do anything special to convert your 3.3 data to 3.4 database structure? Did you have any dificulty running any of the upgrade scripts? Any other comments you have??
Paul Borgermans	Saturday 26 June 2004 3:16:42 am >I wanted to know if anybody else has tried and what they had to deal with in getting it to work? Done, so, on a production server. >Have customized any of your clasess, did you add any fields to say the article class or the product class? Almost all of them.. >Have customized any of the kernal scripts? If so how did it go upgrading them? Yes, quite a few but with at maximum 15 line changes, re-applied them manually. >Did you have to do anything special to convert your 3.3 data to 3.4 database structure? No, followed the required path from 3.3-2 to 3.3-5 and then to 3.4.1 (SVN version) >Did you have any dificulty running any of the upgrade scripts? No >Any other comments you have?? - Before upgrade check that all the ini settings are specified in the override/siteaccess inis, not the standard ini settings - Make sure all permissions are set correctly for the entire eZpublish directory after file copying - run the database upgrade scripts (I use webmin for that) - Clear all caches - stop Apache, clear accelerator cache files, start Apache - ran bin/php/eztc.php -s <siteaccess> (took around 1 minute on a dual 3GHz PIV) after su to apache deamon user hth -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
John Dalton	Saturday 26 June 2004 8:02:39 pm I've upgraded a development site from 3.3.4 to 3.4.0 (via 3.3.5). The only problem I had was that the upgrade scripts required the cli SAPI version of php to run, and that was unavailable with the vendor packaged version of php on two systems I tried (Fedora Core 1 and Redhat 9). I ended up building php from source and using the compiled php cli binary directly (without installing it first). Other than that the upgrade was pretty smooth.

Author

Message

Friday 25 June 2004 3:00:21 pm

I had some trouble trying to upgrade from 3.3 to 3.4. In fact I was unable to log in. After wroking on it for a while I reverted back to my 3.3 instilation. I wanted to know if anybody else has tried and what they had to deal with in getting it to work?

Have customized any of your clasess, did you add any fields to say the article class or the product class?

Have customized any of the kernal scripts? If so how did it go upgrading them?

Did you have to do anything special to convert your 3.3 data to 3.4 database structure?

Did you have any dificulty running any of the upgrade scripts?

Any other comments you have??

Paul Borgermans

Saturday 26 June 2004 3:16:42 am

>I wanted to know if anybody else has tried and what they had to deal with in getting it to work?

Done, so, on a production server.

>Have customized any of your clasess, did you add any fields to say the article class or the product class?

Almost all of them..

>Have customized any of the kernal scripts? If so how did it go upgrading them?

Yes, quite a few but with at maximum 15 line changes, re-applied them manually.

>Did you have to do anything special to convert your 3.3 data to 3.4 database structure?

No, followed the required path from 3.3-2 to 3.3-5 and then to 3.4.1 (SVN version)

>Did you have any dificulty running any of the upgrade scripts?

>Any other comments you have??

- Before upgrade check that all the ini settings are specified in the override/siteaccess inis, not the standard ini settings
- Make sure all permissions are set correctly for the entire eZpublish directory after file copying
- run the database upgrade scripts (I use webmin for that)
- Clear all caches
- stop Apache, clear accelerator cache files, start Apache
- ran bin/php/eztc.php -s <siteaccess> (took around 1 minute on a dual 3GHz PIV) after su to apache deamon user

hth

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

John Dalton

Saturday 26 June 2004 8:02:39 pm

I've upgraded a development site from 3.3.4 to 3.4.0 (via 3.3.5). The only problem I had was that the upgrade scripts required the cli SAPI version of php to run, and that was unavailable with the vendor packaged version of php on two systems I tried (Fedora Core 1 and Redhat 9). I ended up building php from source and using the compiled php cli binary directly (without installing it first).

Other than that the upgrade was pretty smooth.