Errors running upgrade scripts for 3.10.0 -> 4.0

Errors running upgrade scripts for 3.10.0 -> 4.0

Monday 24 March 2008 5:35:19 am - 4 replies

Author Message

Kristof Coomans

Monday 24 March 2008 9:01:47 am

Please disable PHP safe mode. Good luck ;)

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Iain MacLean

Tuesday 25 March 2008 3:44:08 pm

)Thanks Kristof,

PHP was in safe mode=off anyway, so the safe mode warning is a mystery.

The datatype warning from ezscript.php seems to be caused by the debug settings in the site.ini file, but I can't make them disappear by adjusting the settings. I don't think it is stopping the scripts from running properly.

I tried the upgrade process again, this time I didn't run updateniceurls.php and updatetipafriendpolicy.php when going from 3.9 -> 3.10. That seemed to stop the fatal error when running updateniceurls.php when upgrading from 3.10 to 4.0.

Is it actually necessary to run these two scripts when upgrading from 3.10 -> 4.0?

When I finally managed to log onto the admin area on one of the sites once the full 4.0 upgrade was complete, I got a kernel(3) error when trying to access the Content area. All the other sections were accessible. Content was not accessible when viewing the public site (another kernel(3) error). Could these two scripts be a possible cause of that?

Cheers
Iain

Kristof Coomans

Wednesday 26 March 2008 12:48:12 am

Hi Ian

Can you double-check your PHP configuration? From command line:

/usr/bin/env php -i

Also, it seems like certain settings can not be read. Please check the file system permissions and maybe also PHP's open_basedir setting. Good luck!

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Iain MacLean

Wednesday 02 April 2008 4:52:57 am

Hi Kristof,

Thanks for your suggestions. Even though /etc/php.ini had Safe Mode = off, it wasn't being read as such. When I added Safe mode = off into the php.ini file I had to put into the root of the eZpublish installation, it worked fine. Go figure?

Cheers

Iain

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

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.