I get the WSOD (White Screen Of Death) on nodes that have notifications subscription block turned on. Only occurs when Notifications UI is enabled. All other module pieces can be enabled with no problems. Seems the UI Block-format has some kind of problem? I've never actually seen it.

Comments

gregarios’s picture

gregarios commented

Further note: I'm getting a PHP error on it too apparently. Here is the error in my server logs:

PHP Fatal error:  Call to undefined function notifications_ui_user_node() in
/usr/local/apache2/vhosts/<mydomain.com>/htdocs/sites/all/modules/notifications/notifications_ui/notifications_ui.module on line 292

I've narrowed it down even further it seems. I only have the problem when the following setting has a check enabling it:

/admin/messaging/notifications/ui --> Subscribe to content --> Global settings --> In comment form.

I'm running FreeBSD 6.3, Drupal 6.10, MySQL 5.0.75, PHP 5.2.8, Apache 2.2.11.

igorik’s picture

igorik commented

same problem

chawl’s picture

chawl commented

same

igorik’s picture

igorik commented
Priority: Normal » Critical

it is more than critical

indianroo’s picture

indianroo commented

It killed my dev setup yesterday.

I just tried copying the missing function from the version 5 release. I then got an error message
about calls to dsm at line 644 in notifications.module (I have devel turned off at the moment).
I commented out the lines and at least I don't have WSOD anymore and subscription options are appearing.

Obviously a bit of testing to do, but I hope this is the right start.

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Fixed in -dev (new branch)

I'll be fixing this branching mess too and producing a new beta

Status: Fixed » Closed (fixed)

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

equinox’s picture

equinox commented
Status: Closed (fixed) » Active

Don't close this issue. It's not fixed in the current download as I get this message while simply trying to view a user after enabling the module. All it needs is promotion of the fix I hope.

*use of the latest dev download corrected this bug, but doesn't the issue remain open until it's closed by being included in the general release? I don't usually use dev versions unless absolutely necessary.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (fixed)

doesn't the issue remain open until it's closed by being included in the general release?

No.