Thursday 24 February 2005 10:37:01 am - 12 replies
I placed this as an article comment as well, sorry (don't know how to remove it).
I'm following the complete upgrade-path from 3.3-4 to 3.5.0 (via 3.3-5, 3.4.0, 3.4.1, 3.4.2, 3.4.3, 3.4.4). Installation of 3.3-5 went well, but when I tried to run the update-scripts from 3.3-5 to 3.4.0 I get the following message:
PHP Fatal error:  operator not supported for strings in EZP/lib/ezutils/classes/ezini.php on line 632
Anyone know how to solve this?
Friday 04 March 2005 12:54:20 am
Given the error message and the file it occured in I suspect that ez is reading an ini file value, expecting an array and getting a string.
You may have to add some debugging to lib/ezutils/classes/ezini.php to file which var in which file is causing the issue.
Which update script are you running when this error occurs?
Friday 11 March 2005 8:31:50 am
> They all produce the same error message.
It seems there is a string in an ini file where ez is expecting an array. Given that it is happening for all update scripts I'd start checking the siteaccess and override site.ini files against the distribution ones in the settings directory.
Monday 14 March 2005 10:56:52 am
I moved all my *.ini.append.php files to a different folder, after which the updatescript runs. This would indicate that there is indeed something wrong with my *.ini.append.php scripts. I then minimalised the site.ini.append.php file to:
And placed this file in /settings/siteaccess/mysite/
This is now the only file in this directory. I ran the updatescript again and the same errormessage appeared. To minimalise even further, I even took out the text above, and still the updatescript gives the error. It seems that the only way that I can avoid the errormessage is to remove all *.ini.append.php scripts. I'm guessing that's not the way to go about it, though.
I'm stumped, please help .
Wednesday 23 March 2005 9:30:16 am
OK, I don't like adding another entry just to get this post back in the picture, but I'm still not able to run the upgradescripts, even with minimalised *.ini.append.php scripts.
Does anyone have an idea what the cause of this strange (and apparently unique) behaviour is?
Wednesday 13 April 2005 10:54:01 am
OK, again kicking this post back to the top. I REALLY want to upgrade, but apparently am not able to when I have override scripts in the settings/siteaccess/design directory. As mentioned before, I tried with a completely stripped down version of site.ini.append.php and that didn't work either. Is it possible to upgrade without the scripts in the directory and after the upgrade place them back? Bit of a hack, but I'm at my wits end. Once again: please help .
You must be logged in to post messages in this topic!