Closed (fixed)
Project:
Notify
Version:
7.x-1.5
Component:
Miscellaneous
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Mar 2018 at 22:14 UTC
Updated:
18 Apr 2018 at 13:34 UTC
Jump to comment: Most recent
Comments
Comment #2
shadowmihai commentedComment #3
gisleI 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.
Comment #4
nsherzog commentedI'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
Comment #5
allnations2017 commentedI 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()
Comment #6
gisleThanks 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.
Comment #7
allnations2017 commentedFor 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
Comment #8
AgentJay commentedI 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.
Comment #9
gisleThanks 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?
DrupalWebTestCaseis 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.
Comment #10
AgentJay commentedIt 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.
Comment #11
gisleThe 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.
Comment #12
ryanbriscall commentedFatal error: Class 'DrupalWebTestCase' not found in sites/all/modules/notify/notify.test on line 9
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.
Comment #14
gisleThe 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.
Comment #15
shadowmihai commentedInstalling the 7.x-1.4+2-dev branch did NOT break the site.
Comment #16
gisleTHanks for reporting, shadowmihai. Can you tell us what version of PHP your site uses?
Comment #17
shadowmihai commentedphp 5.6
Comment #18
allnations2017 commentedInstalling 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.
Comment #19
gisleThe 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.
Comment #20
allnations2017 commentedRelease 1.5 is ok, thanks.
Comment #21
gisleThere has been no new reports about this bug since the release of 7.x-1.5. Closing.