It seems like d6 and d7 versions of this cache clear procedure were mostly copied straight from d5 version, while they are no longer relevant or complete, which also causes some unexpected issues with Clone and Migrate tasks. We should use drupal_flush_all_caches() (as used in drush cc all) instead to really clear all caches as expected.
This issue seems to manifest itself when you migrate an existing site into Aegir then attempt to clone and migrate to a new platform. The verify function is not clearing all the cached tables and so the new migrated site is only viewable as a White Screen of Death. This is currently fixed by interacting with the site via drush (enable a module, disable a module, or simply cc all)
Comments
Comment #1
omega8cc commentedFix committed in http://drupalcode.org/sandbox/omega8cc/1074910.git/commit/cd83122
Comment #2
omega8cc commentedMoving it to the correct queue.
Comment #3
anarcat commentedAwesome thanks. It would be great if we had a better idea of what those issues are, if only to allow people to find this issue more easily. :)
Comment #4
omega8cc commentedOf course I will need to re-roll the patch, as that one above is rather for reference only.
Comment #5
omega8cc commentedOps. not intended priority change.
Comment #5.0
frodopwns commentedmore detailed description of issue
Comment #6
frodopwns commentedThanks for looking at this guys. I kept running migrations only to get a WSOD then I would see in the verify output that it was in fact clearing cache so I just couldn't get my head around it.
Comment #7
omega8cc commentedWow, it seems that I have already submitted the correct patch for review here: http://drupal.org/node/1785624#comment-6481480
http://drupalcode.org/sandbox/omega8cc/1111100.git/commit/3ba982a
I'm closing the other issue as a duplicate.
Comment #8
anarcat commentedmerged in...
Comment #10
anarcat commentedsomehow i forgot to push this commit to 2.x, that is now really fixed.
Comment #10.0
anarcat commentedAdd reference to drush cc all