Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hello.
This morning I updated Drupal core 7.59 to 7.60 and get a 500 error.
User warning: The following module is missing from the file system: path. For information about how to fix this, see the documentation page. in _drupal_trigger_error_with_delayed_logging() (regel 1143 van /home/filmhuis/public_html/includes/bootstrap.inc).
Second website I updated from 7.59 to 7.60 the same 500 error occured.
Anyone any idea what's going on here?
Comments
Comment #2
djowright CreditAttribution: djowright commentedI've tried the update on two of my sites with same results. What I'm getting is the white screen that says Drupal is already installed, and I can't log in to my site. Please someone help! Thanks in advance.
Comment #3
BrianLP CreditAttribution: BrianLP commentedSame wsod here. Tried multiple times. I recovered from backup so can't say any error messages.
Comment #4
scott_euser CreditAttribution: scott_euser as a volunteer and at Soapbox Communications Ltd commentedLooking at the warning, it looks like your database thinks that the 'Path' module should exist but when it searches in ./modules/path for instance, it does not find it. Can you confirm that the Drupal Core path module exists at `./modules/path/path.module`?
If so, maybe you can double check that the 'system' database table is actually looking for it there:
SELECT filename FROM `system` WHERE `name` = 'path'Should give you `modules/path/path.module`
Assuming it is looking in the right place, and the file exists, you can try emptying the cache_* database tables (drush cc all may not work if it's hitting that error).
All a bit of shots in the dark as in testing, I was able to update from 7.59 to 7.60 without issue with the path module.
Comment #6
stephencamilo CreditAttribution: stephencamilo as a volunteer commentedComment #7
hestenetReset issue status.
Comment #8
apadernoComment #9
hemant-gupta CreditAttribution: hemant-gupta commentedYou can see the below solutions for WSOD:
Firstly, enable errors reporting in settings file to find out the reasons.
Or, access the error file directly on the server to check issues.
Suggested fixes:
1. Clear the cache using admin UI/drush command
2. Restart web server
3. Increase PHP Memory Limit if needed
4. Increase PHP execution time limits if needed
5. Check missing few database tables manually & also using command like- 'drush status' to fix it
6. Remove a non-recommended module version it used there
7. Remove a white space given above PHP tag in the root index file if so
8. Check and remove the same hook used twice in the theme/module
I hope it helps you!
Comment #10
cilefen CreditAttribution: cilefen commentedThe OPs did not reply with information.
Comment #11
hemant-gupta CreditAttribution: hemant-gupta commentedIt was fixed by the patches.
Comment #12
apadernoThe OP has not said this was fixed by patches.