Updated via drush to 2.0 (was 1.6) and ended up with a borked site. Error is as follows

Fatal error: Cannot unset string offsets in ~/Sites/drupal/sites/all/modules/google_fonts/google_fonts.module on line 138

Marked as major because module needs to be disabled directly via SQL console.

CommentFileSizeAuthor
#2 Screen shot 2011-05-18 at 6.35.12 PM.png41.22 KBBarisW

Comments

retrakker’s picture

retrakker commented

Just some additional info. As I didn't really wanted to disable the module I "fixed" it the following way.

Seemingly drush wasn't able to trigger the db update as the module was already in place. Hence I uncommented the offending line 138, updated the db, re-enabled line 138 and voila it works again.

BarisW’s picture

BarisW commented
Status: Active » Postponed (maintainer needs more info)
StatusFileSize
new Screen shot 2011-05-18 at 6.35.12 PM.png41.22 KB

What PHP version are you using? I tried to reproduce it, but I'm getting no errors. Just a nice message stating 'You need to run the update script to perform required database updates.'

See screenshot.

Can you provide me with some more details? FYI, I'm running PHP 5.2.17

retrakker’s picture

retrakker commented

This is on a XAMP installation with PHP 5.3.1 on OSX - basically my staging area. As it seems you used the Drupal internal update method, which I can't use (no FTP). As mentioned before this was after using drush up (Drush 4.4). Actually I am wondering how you can update via internal, as on my live page the update is visible but can't be used. So is there actually an official update path?

BarisW’s picture

BarisW commented

Then maybe it's PHP 5.3 that's causing the error. I'll try it with 5.3 to see if i can reproduce your error.
I did my update with drush as well, I didn't update via internal.

The module has a check included to see if you already ran the update script (using update.php or drush updb).
Updated or not, your site should not crash because of the module.

But yes, there is a (kind of) update path.

BarisW’s picture

BarisW commented
Status: Postponed (maintainer needs more info) » Fixed

Thanks for reporting. Fixed in 7.1!

See: http://drupal.org/node/1183748

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.