This is what I have learned, a little bit of "good practice" for drupal 7: 

If you use any classes in your own modules, always put them in an include file. Drupal will autoload them when they are needed. 

Using the autoloader protects you from WSOD should the ancestor class move to a new file, because it will not attempt to set up the classes the moment the module is enabled in the bootstrap. 





On 24 January 2011 17:51, Greenman <greenman@the-organization.com> wrote:
Sorry for the spam. 

The registry is not just in the cache_bootstrap, it's also in the main registry tables. 

I have only been able to get around this issue by disabling modules in the db, running "drush updatedb", and then re-enabling my modules. 

Fun with registries! 

 

On 24 January 2011 17:32, Greenman <greenman@the-organization.com> wrote:
I will now answer my question: 

The object registry is in the bootstrap cache. Clear that and things should work. 




I would have had some success earlier had I been running my queries on the correct database. Thwak!




On 24 January 2011 16:50, Greenman <greenman@the-organization.com> wrote:

I keep hitting this problem: I update or move a module and everything breaks. Most of the time the issue is to do with Drupal’s cache of files, objects and includes.

How do I update this list ? Unfortunately Drush is even more sensitive to this issue than core, so a drush script is probably not the best way to go.

Any ideas on how to re-build the file list ?


Peter