I attempted to update to the 7.x-2.x-dev update that was pushed out today. After Drupal downloaded and self-installed the update, I saw the following error message: Deprecated function: Call-time pass-by-reference has been deprecated in drupal_load()

Before I could get to the database updates page, the site crashed entirely. Attempting to load any page would have the server drop the connection. Removing the skinr module immediately solved the problem. I downloaded and re-installed manually from the project page, and the site immediately become totally inaccessible again.

I was only able to bring my site back to life by reverting to the previous 7.x-2.x-dev version, which has a changelog dated 10-27-11.

Something is fundamentally flawed with today's update. I strongly recommend that it be pulled.

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Caused by #1299162: Unable to get theme settings in skinr ui form, see details there.

GeertL’s picture

GeertL commented

Same error over here. I pushed the newer version and got the error Deprecated function: Call-time pass-by-reference has been deprecated in drupal_load() (line 1126 of /Users/geert_laeremans/Sites/acquia/includes/bootstrap.inc). By disabling the Skinr and skinr UI modules, the error went away.
Tried the same on my localhost copy, and the same appeared.
Haven't tried yet to get back to the previpous version. The template I'm using is the one from Acquia - Marine.

GeertL’s picture

GeertL commented

Why are the patches proposed in the #1299162: Unable to get theme settings in skinr ui form, not included in this release?
I had to turn back to the previous version to get rid of the errors.

moonray’s picture

moonray commented
Status: Active » Fixed

The fix is committed, as per #1299162: Unable to get theme settings in skinr ui form.

Taxoman’s picture

Taxoman commented
Title: Today's release will destroy any website that installs it » Skinr Jan 5th dev release makes web site inaccessible

("destroy" makes me think of more serious database corruption or the like... - less scary and more accurate title for future search, etc.)

Status: Fixed » Closed (fixed)

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