I upgraded from the current stable 6.x version to the new beta then ran update.php. I got the following errors:

warning: Invalid argument supplied for foreach() in /srv/www/mysite.com/sites/all/modules/google_fonts/google_fonts.install on line 31.
warning: Invalid argument supplied for foreach() in /srv/www/mysite.com/sites/all/modules/google_fonts/google_fonts.install on line 31.

Comments

bensnyder’s picture

bensnyder commented

same

gthing’s picture

gthing commented

I uninstalled the module, then reinstalled the beta and it seems to have worked.

BarisW’s picture

BarisW commented
Status: Active » Fixed

Fixed in 6.x-2.x-dev. Thanks for reporting!

Status: Fixed » Closed (fixed)

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

austintnacious’s picture

austintnacious commented
Title: Upgrading to 6.x-2.0-beta1 errors during update.php » Upgrading to 6.x-2.0-beta2 errors during update.php
Version: 6.x-2.0-beta1 » 6.x-2.0-beta2
Priority: Normal » Critical
Status: Closed (fixed) » Active

Love the module, don't like what beta2 just done to me.

Your project page doesn't display a 6.x-2.0-dev. Only the 6.x-1.7 and the 6.x-2.0-beta2 releases.
Further, the page displays 3 open bugs, none of which are for the beta-2 version.

Doing a search on the issues page only shows one other beta-2 issue, http://drupal.org/node/1247854.
Why a search on the issue page for version -> 6.x-2.0-beta2 doesn't show this pretty major error . . .

From this I assumed it would be OK to give beta2 a test drive. . . WRONG!
Got the same error

warning: Invalid argument supplied for foreach() in /srv/www/mysite.com/sites/all/modules/google_fonts/google_fonts.install on line 31.
warning: Invalid argument supplied for foreach() in /srv/www/mysite.com/sites/all/modules/google_fonts/google_fonts.install on line 31.

And all my selected fonts and css selectors are gone! Stepping back to the 1.7 release and all my google fonts are still gone and I get the message "Sorry you'll need to pick all your fonts again!" NOT TO MENTION ALL THE CSS SELECTORS!

If the code that is available for download does NOT contain the fix then the issue is not "fixed".
Please don't mark as fixed and close an issue if it is NOT fixed!!!

Luckily, I had a recent DB backup and was able to get back on track but I did lose the time wasted and the work done between the backup and this mess.

If this code (-beta2) remains available for download DO NOT MARK THIS ISSUE AS "FIXED"!
Thanks!

BarisW’s picture

BarisW commented
Status: Active » Needs review

@austintnacious: A beta is a beta, you can always expect it to have bugs. Glad you had a back-up (as recommended: http://drupal.org/node/250790). I thought it was valid to mark issues as fixed when the bugfix has been pushed to dev?

Anyhow: I've re-added the dev to the project page and I've also created a new release 6.x-2.0-beta3. If you'd be so kind to test it for me, that would be awesome!

austintnacious’s picture

austintnacious commented

I would love to test it but first I need to know that upgrading to beta3 will preserve my existing fonts and selectors. . . if I can upload the b3 files, run update.php and continue working from where I am in my flow then I'll happily test.

BarisW’s picture

BarisW commented
Status: Needs review » Fixed

No replies in months so I assume this is fixed.

Status: Fixed » Closed (fixed)

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