BEWARE of updating authcache via update module.

FYI - if you make the mistake of updating more than one module via ftp through the update module, and one of those mods happens to be the "recommended" version is Authcache....BEWARE!

Your site will crash. You wont be sure of which module because you updated multiples. Going into the database and turning Authcache off wont help either. I finally contacted my host to see if they could see what was wrong - authcache.

I then came over to drupal.org/auth cache's page and learned that the "recommended update" was a whole new version that would crash my site.

Hope this saves someone else a day of work.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

znerol’s picture

I'm sorry that this happened to you.

It would be helpful if you could provide more information on what exactly triggered the WSOD. Then it would be possible for me to figure out a way such that other people won't go through all of this.

znerol’s picture

comment removed

znerol’s picture

Okay, I tried to reproduce this:

1. Start out with the outdated Authcache 7.x-1.5 produces this screen on update-status:

2. Then go ahead and update to the latest version. Status update will fetch 7.x-1.7

3. Then return and everything turned green:

4. I do not see a way to update from 7.x-1.7 to 7.x-2.0-beta2 via the GUI. How did you do that?

znerol’s picture

@IWasBornToWin: Could you please check your PHP version? Maybe this is the same issue like #2231877: Can't install the module on PHP 5.2 (White Screen of Death)?

znerol’s picture

Status: Postponed (maintainer needs more info) » Closed (outdated)