Closed (fixed)
Project:
Entity API
Version:
7.x-1.x-dev
Component:
Core integration
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Oct 2011 at 15:56 UTC
Updated:
29 May 2017 at 10:22 UTC
Jump to comment: Most recent
Comments
Comment #1
fagoThis is probably caused by a menu_rebuild working with stale entity info - see #996236: drupal_flush_all_caches() does not clear entity info cache
Comment #2
fagoComment #3
fagoThe Drupal 7 patch at #996236-45: drupal_flush_all_caches() does not clear entity info cache (#45) should fix the issue, but it needs to be applied before disabling modules. Afterwards, manually clearing the cache should help.
Comment #4
alan d. commentedWould this be related to #1274692: Error on Disabling Module. I got a fatal error when uninstalling the field collection module.
Comment #5
fagobumping priority
Comment #6
ouyang1512 commentedI had the same problem when I tried to disable module Profile2. The error message is:
Fatal error: Class 'Profile2MetadataController' not found in /usr/local/apache2/htdocs/drupalfolder/sites/all/modules/entity/entity.info.inc on line 23
I was no longer be able to access the site.
Then I had to follow the suggestions in this thread "#1274692: Error on Disabling Module" commenting out line 23 and 24 in /sites/all/modules/entity/entity.info.inc to get the site back, and then turned the Profile 2 back on. Very frustrating.
Any final solution to this issue?
Comment #7
MrsWho commentedI too have been unable to get rid of the mains of profile2 (see my issue here: http://drupal.org/node/1294200). I also have been unable to get rid of linkit in the modules list after uninstall. Looking at phpmyadmin, the trace linkit fragments are in the system table.
Comment #8
fagomarked #1357640: SOS unchecked some modules related to support ticketing leads to critcal failure ... as duplicate
Comment #9
Anonymous (not verified) commentedI ran into the same issue while disabling profile2. As it was an my local testing environment, I decided to simply truncate all cache tables (all tables beginning with "cache_" as well as the table "cache").
The site is now accessible again and seems to do fine. Would somebody please comment, if this procedure could cause any side effects or if it's feasible for production sites, too?
Comment #10
alan d. commentedShould be safe. I've done this 1000 times. The only danger is that the timeout is set too low, it may take 30s or more to repopulate these tables. If you hit a timeout, try hitting refresh a few times :)
Comment #11
marktheshark commentedHad the same issue, also had to truncate cache tables in phpmyadmin to get the site operational again, as per the suggestion in #9.
Comment #12
kenorb commented+1
Comment #13
ressaThanks for the tip, truncating all tables beginning with "cache_" fixed it.
Comment #14
leex commentedTuncating cache tables worked for me as well.
Step 1: Uninstall module, an error will appear.
Step 2: Truncate cache and cache_ tables
Step 3: Everything should be working normally now.
If you have any complications, just try installing the module again, then following the steps.
Comment #15
fago#1325126: uninstallation troubles due to outdated entity info got committed. Thus update to drupal 7.12 and your problems should be gone now :)
Comment #17
roynilanjan commentedThis is an issue related to entity module + cache API
referring to https://www.drupal.org/node/1370046