Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
base system
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Jan 2011 at 14:29 UTC
Updated:
16 Jul 2013 at 06:01 UTC
Jump to comment: Most recent
Comments
Comment #1
cpforbes commentedI ran into the same problem it seemed to be a corrupt cache of some sort. The entity.inc file was not being loaded.
Truncating the cache tables by hand did not change the behavior.
I could not run drush or connect to the site. Eventually I seeded the lookup_cache entry in the cache_bootstrap table with an entry from a different Drupal install.
I have no idea what the root cause was.
Comment #2
topdawg commentedWhat if I don't have another install, do I need to do a full restore from a couple of days ago?
Comment #3
adamdicarlo commentedOne cause of this type of error is modules being moved to new locations.
I had moved a module, then Drupal wouldn't bootstrap, so I manually fixed the system table's "filename" entries (D6 thinking) -- to no avail, because the code registry was still invalid. So I cleared the registry and registry_file tables, thinking they'd get rebuilt automatically. WHOOPS -- they don't.
What I did to fix it was piece together this script (run it from within your Drupal 7 root directory):
The error I'd gotten was slightly different: Error: Class 'DrupalDefaultEntityController' not found in
/path/to/drupal/modules/user/user.module, line 281
Not sure if this would've completely worked if I hadn't already fixed the system table entries manually.
If you're on Windows, look at the comment near the top of /scripts/drupal.sh for basic instructions on getting a shell script to run. (I haven't tried this on Windows.)
Comment #4
misscosmic commentedi'am having the same error... although that is what I think. I hardly know anything about PHP. My error log says:
I get a blank page http://localhost:8888/... Do you think you can help me..?
Comment #5
bfroehle commented@misscosmic: Drupal 7 requires at least 32mb of memory -- see System Requirements: PHP and Increase PHP memory limit.
Comment #6
jhedstrom@adamdicarlo, you should consider merging that script with Registry Rebuild (a drush command) if there are parts that aren't already in there.
Comment #7
mattwmc commentedI get the following error when trying to run the script:
Parse error: syntax error, unexpected T_STRING in /home/content/xxxx on line 20Line 20:
Comment #8
Anonymous (not verified) commentedwhile update my core from 7.10 to 7.12, I got this error too, occurring in
user.module, line 296, :
I tried the above script but didn't help... then I found another similar script at http://drupal.org/node/1253402. after some editing , it fixed my the problem! Thank!
Here is the rescue script I used:
Comment #9
mitchell commentedThis error seems to occur from many sources during the update process, see #1190842: 7.x-2.0-beta2 (and 2.1) breaks EntityAPI for another example. Much like #3 and #8, Registry Rebuild is a project dedicated to providing a rescue script in the event of registry crashes.
If it's possible to check the registry for this problem and perform a
registry_rebuild()during the update process, then that would solve this problem in later Drupal versions. Even if it's not possible to do it automatically, update.php could provide this function to site maintainers who need to run it manually.Comment #10
catchDuplicate of #534594: [meta] system info cache writing and registry rebuilding is broken without a full bootstrap.
Comment #11
mikeytown2 commentedI had to add this in to #8