Update script error while upgrading Drupal 5.0 to 5.1 and modules

By anjori on 23 Feb 2007 at 22:27 UTC

I'm trying to upgrade my captcha and textimage modules in Drupal 5.0. After overwriting the respective module directories with the newer versions, I attempt to run the update.php script and receive the following error:

An unrecoverable error has occured. You can find the error message below. It is advised to copy it to the clipboard for reference. Please continue to the update summary

An HTTP error 404 occured. update.php?op=do_update

The update summary page provides the additional info:

warning: reset(): Passed variable is not an array or object in /home/user/public_html/update.php on line 521.

The update process was aborted prematurely while running update # in .module. All other errors have been logged. You may need to check the watchdog database table manually.

I've also received this error while trying to upgrade to Drupal 5.1 from 5.0. Any help would be appreciated.

Comments

I'm getting this error after

fronbow commented 9 March 2007 at 00:03

I'm getting this error after uploading the updates for cck and its' fieldgroups.

warning: reset() [function.reset]: Passed variable is not an array or object in /home/public_html/dev/update.php on line 521

There's also a 403.shtml (type=page not found) error in the logs for "update.php?op=do_update"

As anjori said, any help with sorting this would be appreciated.

After doing a lot of

anjori commented 9 March 2007 at 14:38

After doing a lot of searching and reading about similar problems with updating other modules, and after trying out a few possible fixes, it seems to come down to a JavaScript bug with Mozilla browsers.

I have no technical explanation, but try disabling JavaScript in your browser before running the update script. That did the trick for me.

Yes, doing the update

fronbow commented 14 March 2007 at 11:30

Yes, doing the update without js seemed to do something - although I did notice that some of the tables were empty which could have caused an error (I haven't used fieldgroup yet, so I'm leaning towards this as generating the error)

wow

shunshifu commented 28 November 2007 at 20:58

What a trip, that worked for me. Thanks for posting this

Phil

I can't believe that this is a problem...

calebgilbert commented 18 February 2008 at 23:21

It worked though. Actually just turning off javascript in FF did not work for me (though I didn't restart afterwards so maybe that was the problem). I just ended up doing it in Safari.

~~~
HigherVisibility