a white screen of death WSOD comes up when when tries to create a new custom subscription after enabling it.
http://www.testsite7.com/admin/messaging/customsubs/new
on checking the apache logs it shows
[Wed Jun 02 15:23:28 2010] [error] [client 192.168.1.33] PHP Fatal error: Class 'Notifications_Custom_Subscription' not found in /work/projects/testsites/testsite7/www/sites/all/modules/contrib/notifications/notifications_custom/notifications_custom.module on line 355, referer: http://www.testsite7.com/admin/messaging/customsubs
Once we clear the cache via http://www.testsite7.com/admin/settings/performance the WSOD goes away.
This is probably due to the the autoload modules needs caches to be cleared as mentioned
on the homepage of the module
http://drupal.org/project/autoload
NOTE: Remember to clear all caches in your module's hook_enable() if your module relies on autoload. Autoload information is cached and your class may not be found if the autoload cache is not cleared.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | notifications_custom.module.patch | 507 bytes | yasheshb |
Comments
Comment #1
yasheshb commentedhere's the attached patch. requesting review.
thx.
yashesh
Comment #2
jose reyero commentedI think the cache will be automatically refreshed after enabling a new module.
Most of the issues we are running into are because of new classes in new versions of the Notificaitons modules so they're actually upgrade issues.
Comment #3
yasheshb commentedIf the caches were refreshed automatically after enabling a new module then there would not have been a need to clear the caches via the admin interface.
i think it's a cache issue as mentioned clearly by the documentation in the Autoload module.
Comment #4
kswan commentedI just had the same issue on beta6.
I updated from a -dev that was a couple weeks old to beta6 (using drush up).
Then enabled Custom Subscriptions (using the modules page).
Next, I went to the Custom subscriptions page and clicked on Add new custom subscription.
The same error that yasheshb had occurred.
After clearing the cache, the error was gone.
Comment #5
alisonI am having this issue with beta6 too, and I just installed this and the Autoload module yesterday. I cleared my cache and ran cron a few times since first experiencing the issue but I'm still getting WSOD. In case it matters, I only enabled Custom Subscriptions today, though I enabled the other subscriptions/notifications/messaging/autoload modules yesterday.
Comment #6
alisonSorry, meant to include the errors...
Here:
(The first error showed up 3 times in a row in my log; the second error showed was listed 6 times in a row after the 3 instances of the first error.)
Thank you!
Comment #7
jose reyero commentedApplied the patch. Thanks.
To fix the error disable and enable the 'Custom' module.