After running update.php, I find my blocks revert to their default settings (causing a strange page display obviously) until I flush the cache and it goes back to normal.. any idea what this could be?

Comments

sheena_d’s picture

Project: Fusion » Fusion Accelerator
Version: 7.x-2.x-dev » 7.x-2.0-beta1
Category: bug » support
Status: Active » Fixed

Did you update Fusion Accelerator as well? The latest release of Fusion Accelerator includes schema changes. Once update.php is run, the cache needs to be cleared so that the Skins can be re-generated. This is not a bug.

Anonymous’s picture

Ah OK, I was just talking about updating in general. Thanks for letting me know.

Status: Fixed » Closed (fixed)

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

macman824’s picture

Status: Closed (fixed) » Active

Are we sure this is not a bug? The need to clear the cache after updating any module—even modules other than Fusion Accelerator—is not documented anywhere. I was heretofore unaware that clearing the cache would resolve this issue; any time I updated any module on my site, I would have to disable and then re-enable each of the three Accelerator modules one at a time in order to get the skin to kick back in.

If we can't automate the process of clearing the cache, we should at least prominently document the need to do so after running update.php. This has been a big headache of mine for a long time, going all the way back to Skinr. I could have saved myself a significant amount of aggravation knowing that the solution to skins falling apart was just to clear the Drupal cache.

esmerel’s picture

That's generally a Drupal core issue - it happens throughout Drupal. I'm not sure there's anything in particular that fusion can do about it.

macman824’s picture

Hmm. If we can't do anything about this at the module level, we should consider making this a Documentation issue instead, so that the need to clear the site cache after any update of any item, even those not related to Fusion Accelerator, is made clear to users. At present, I can't find mention of the need to do this in any existing documentation, and update.php doesn't itself say anything about clearing the cache after it's been run. I nearly had a heart attack yesterday when my disable-then-re-enable Accelerator modules trick stopped working.

macman824’s picture

Component: Code » Documentation
macman824’s picture

Category: support » task