Updated to latest version, site broke, fails to load anything. Clearing caches/cookies/ running update.php has no effect. Only getting unresponsive white screen. Removal of module from modules directory brings site back. Drupal 7.57.

Comments

shadowmihai created an issue. See original summary.

shadowmihai’s picture

Issue summary: View changes
gisle’s picture

Status: Active » Postponed (maintainer needs more info)

I am very sorry to hear that. I've 17 production sites that all have Notify 7.x-1.4 installed - and none of them is able to reproduce this problem.

Since the problem cannot be reproduced by me, I need more information to be able to fix this. Unfortunately this means that it has to be postponed until someone can provide more information about the problem.

Can you (or anyone else who experience this problem) please post the latest Watchdog messages that appear when you experience the WSOD by installing this module. You find those by navigating to: Home » Administration » Reports » Recent log messages.

Any other information you may have that may help me debug this will also be welcome.

nsherzog’s picture

I've also updated to 7.x-1.4 and had it break my site (WSOD).

I'm running Drupal 7.5.7 with PHP version 5.3.3

allnations2017’s picture

I also have this problem.

Tried to update my site to 7.x-1.4 and I get a white screen with an Internal server Error.

I am running Drupal Core 7.57 with PHP version 5.3

The only message in the log file is

User warning: The following module is missing from the file system: notify. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging()

gisle’s picture

Thanks nsherzog and allnations2017,
the common denominator is that you are running PHP 5.3. I have no sites with a version of PHP that old (it reached EOL in August 2014). My sites use either PHP 5.5.9 or PHP 7.0.22.

I'll try to find a server that let me run PHP 5.3 to do some debugging, but I am not sure where to find one. I have yet to find a provider of IaaS that let me set up a standard instance with a version that old.

This may work: ServerFault: How to install old PHP version - but from past experience I know that pulling in a legacy PHP on a modern Gnu/Linux server makes other parts of the LAMP-stack (in particular Apache) break.

allnations2017’s picture

For Drupal 7 the supported PHP version is 5.2.5 and higher.

Www.drupal.org/docs/7/system-requirements/drupal-7-php-requirements#php_required

AgentJay’s picture

I am getting this issue on a development sever using php 5.4.16 it gives the error:
PHP Fatal error: Class 'DrupalWebTestCase' not found in /srv/www/biopama/sites/all/modules/notify/notify.test on line 9

I turned off Notify through the database and had to clear my cache tables and I'm up and running again, but without notify.

gisle’s picture

Thanks for your feedback AgentJay. Do you get this error during install (as reported by the OP)? Or do the error message appear in some other context?

DrupalWebTestCase is part of the Drupal API - https://api.drupal.org/api/drupal/modules!simpletest!drupal_web_test_cas... - so I find it strange that it is "not found".

Also DrupalWebTestCase: 1) is not invoked during install; 2) should work with PHP 5.4.16.

It may be that this error message provides some clue about what is wrong with this release, but I need more context to be able to debug this.

AgentJay’s picture

It happened after I updated from Notify 1.3

Indeed it's strange that it's unable to find DrupalWebTestCase as I know other modules I have use it in the same fashion... Some Googleing of the error makes it look there may be an issue with matching file/class names.

gisle’s picture

The test cases is one of areas where the project has changed between 7.x-1.3 and 7.x-1.4, so this is certainly worth pursuing.

ryanbriscall’s picture

Fatal error: Class 'DrupalWebTestCase' not found in sites/all/modules/notify/notify.test on line 9


Call Stack
#	Time	Memory	Function	Location
1	0.0003	383464	{main}( )	...\index.php:0
2	0.0081	721824	drupal_bootstrap( $phase = 7, $new_phase = ??? )	...\index.php:35
3	0.1996	7599416	_drupal_bootstrap_full( )	...\bootstrap.inc:2538
4	23.4992	76191392	module_invoke_all( $hook = 'init' )	...\common.inc:5313
5	23.5267	76418112	mailsystem_init( )	...\module.inc:957
6	23.5267	76418112	mailsystem_get_classes( )	...\mailsystem.module:17
7	23.5501	76603080	drupal_autoload_class( $class = 'TestNotifyMailSystem' )	...\mailsystem.module:286
8	23.5501	76603080	_registry_check_code( $type = 'class', $name = 'TestNotifyMailSystem' )	...\bootstrap.inc:3399
9	23.5501	76603080	class_exists ( 'TestNotifyMailSystem' )	...\bootstrap.inc:3436
10	23.5501	76603120	spl_autoload_call ( 'TestNotifyMailSystem' )	...\bootstrap.inc:3436
11	23.5501	76603200	drupal_autoload_class( $class = 'TestNotifyMailSystem' )	...\bootstrap.inc:3436
12	23.5501	76603200	_registry_check_code( $type = 'class', $name = 'TestNotifyMailSystem' )	...\bootstrap.inc:3399
13	23.5545	76719848	include_once( '\sites\all\modules\notify\notify.test' )	...\bootstrap.inc:3494

Even with reverting the code changes, this issue is still occurring. I can't even use Drush without getting this same error. I had to manually disable the mailsystem and notify modules from the database directly.

For those having this issue, use these database queries:
UPDATE `system` SET `status` = 0 WHERE `name` = 'mailsystem'
UPDATE `system` SET `status` = 0 WHERE `name` = 'notify'

If you're on MSSQL, then use this query instead:
UPDATE [system] SET [status] = 0 WHERE [name] = 'mailsystem'
UPDATE [system] SET [status] = 0 WHERE [name] = 'notify'

Then clear Drupal cache, and re-enable the mailsystem and notify (v1.3) modules.

  • gisle committed 51dd486 on 7.x-1.x
    Issue #2949893 by gisle: Debug version without the testing framework -...
gisle’s picture

The latest snapshot of the 7.x-1.x-dev branch is identical to 7.x-1.4, but without the test framework.

If the tagged release 7.x-1.4, broke your site, it would be appreciated if you will help out by testing this version.

Please see #2952467: Test if bug in 7.x-1.4 is related to tests for further instructions.

shadowmihai’s picture

Installing the 7.x-1.4+2-dev branch did NOT break the site.

gisle’s picture

THanks for reporting, shadowmihai. Can you tell us what version of PHP your site uses?

shadowmihai’s picture

php 5.6

allnations2017’s picture

Installing 7.x-1.4+2-dev (www.drupal.org/project/notify/releases/7.x-1.x-dev) on my PHP version 5.3 Drupal Core 7.57 site did NOT break the site.

gisle’s picture

Version: 7.x-1.4 » 7.x-1.5
Status: Postponed (maintainer needs more info) » Needs review

The bug that broke some sites is in the automated tests (notify.test).

Automated tests has been removed and a release 7.x-1.5 has been pushed to the repo.
This release is identical to 7.x-1.4+2-dev.

Plaese review this release to confirm that the the bug is gone.

allnations2017’s picture

Release 1.5 is ok, thanks.

gisle’s picture

Status: Needs review » Fixed

There has been no new reports about this bug since the release of 7.x-1.5. Closing.

Status: Fixed » Closed (fixed)

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