|
Author
|
Message
|
|
Vivienne van Velzen
|
Thursday 24 February 2005 1:37:01 am
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?
|
|
Roy Bøhmer
|
Thursday 24 February 2005 1:42:57 pm
I've had similar trouble with the update-scripts using phpMyAdmin. Manually removing the comments starting with -- do the trick for me. roy
|
|
Vivienne van Velzen
|
Thursday 24 February 2005 11:26:33 pm
Thanks for the reply, but I don't have a problem with the MySQL update scripts. It's the PHP scripts (in /update/common/scripts) that produce the error. Sorry, should have said. Has anyone else come across this problem?
|
|
Vivienne van Velzen
|
Monday 28 February 2005 12:23:00 am
Can anyone help? I'd really like to upgrade to the latest release, but it just won't work. If you need more information, please ask.
TIA, Vivienne
|
|
Vivienne van Velzen
|
Thursday 03 March 2005 1:11:11 am
Maybe someone from the EZ team? I can't imagine that I'm the first one to experience this problem.
|
|
Bård Farstad
|
Thursday 03 March 2005 3:54:49 am
Which PHP version are you using? Please check the PHP version of the CLI (command line) version of PHP as well. --bård
Documentation: http://ez.no/doc
|
|
Vivienne van Velzen
|
Thursday 03 March 2005 6:31:13 am
PHP as shown in EZP admin-interface: 4.3.3
PHP as shown on CLI: 4.3.3
|
|
Bruce Morrison
|
Thursday 03 March 2005 3:54:20 pm
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?
Cheers
Bruce
My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
|
|
Vivienne van Velzen
|
Monday 07 March 2005 11:54:05 pm
Hi Bruce,
I tried all the scripts that are mentioned in the upgrade-documentation for 3.4:
- updateremoteid.php
- updatesession.php
- updatetoplevel.php
- addorderemail.php They all produce the same errormessage. Vivienne
|
|
Bruce Morrison
|
Thursday 10 March 2005 11:31:50 pm
Hi Vivienne
> 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.
Cheers
Bruce
My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
|
|
Vivienne van Velzen
|
Monday 14 March 2005 1:56:52 am
Hi Bruce, 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:
[DatabaseSettings]
Database=ezpublish_tmp
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 :-(. Vivienne
|
|
Vivienne van Velzen
|
Wednesday 23 March 2005 12: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?
TIA, Vivienne
|
|
Vivienne van Velzen
|
Wednesday 13 April 2005 1: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 :-(. Vivienne
|
