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.
I encountered the following error while disabling the 'field collection' module. Now I can't log into my site (on test server though) :(
Fatal error: Class 'FieldCollectionItemMetadataController' not found in D:\xampp\htdocs\mysite.com\sites\all\modules\entity\entity.info.inc on line 23
Along with this module I was also disabling the 'Hierarchical Select' module, simultaneously.
I also tried to remove the 'field collection' folder from the modules folder and refreshed, it didn't work. What could have gone wrong?
Comments
Comment #1
flexicode CreditAttribution: flexicode commentedComment #2
flexicode CreditAttribution: flexicode commentedA wait of four long days and no answer yet! ****sigh*****
Comment #3
4kant CreditAttribution: 4kant commentedSame here - right after disabling the module 'field collection'.
What I did then was:
Commented out lines 23 and 24 of entity.info.inc and went back to activate the module
So how can I deactivate it?
And before that I had another scenario (with another backup of the database):
1. I deleted the field "field-collection" in admin/structure/types/manage/nodetype/fields (but had not deleted 3 Fields in that collection beforehand - I simply had forgotten that)
2. tried to deactivate 'field collection' - but couldn´t even uncheck it.
In the Status report it said that there are still some fields left --> now I remembered those fields...
What is the correct way to deactivate this module?
Thanks!
Comment #4
baby.hack CreditAttribution: baby.hack commentedI had the same issue. I commented out lines 23 and 24. Then I disabled Field Collection and saved the changes to modules list.
I disabled the Entity API and uncommented the lines. Then enabled Entity again. Silly to have to do this, but seemed to be the only way to disable Field_Collection.
Comment #5
robcarrSame for me, although didn't have to disable Entity module to get error to clear - it was just a case of commenting out lines 23 and 24 in entity.info.inc. Then Drush could do its business and uninstall the modules.
Just an aside thought though: why the need to disable Field Collection in the first place? For me the module just didn't work at all, and I thought the turn-it-off-turn-it-on-again approach might help (it didn't). Feel another issue bubbling up...
Comment #6
robcarrBTW @flexicode - you shouldn't delete a module folder until you have completely uninstalled the module, otherwise you may be left with orphaned tables and rows within tables in you site database. If you have erroneously deleted it, re-download the module code and try the uninstall process again.
Comment #7
robcarrComment #8
baby.hack CreditAttribution: baby.hack commented@arrrgh: My purpose for disabling Field Collection was part of disabling all modules during a core upgrade.
Comment #9
Ludo.RI just got the same issue.
What is wrong?
Comment #10
luco CreditAttribution: luco commentedwell, field collection defines a new entity. that entity should be uncreated during module uninstall - and seems like it isn't. that's my guess. but where do we manage entities as we do node types?
Comment #11
luis_san CreditAttribution: luis_san commentedHey, I doesn't have time to solve this, but I could make to my Drupal works again.
You need to enable your module into DB.
and your Drupal instalation works again! ;-)
Comment #12
Jessica A CreditAttribution: Jessica A commentedhave this error too, any solutions?
Comment #13
fago#1325126: uninstallation troubles due to outdated entity info got committed, so best try updating to 7.12 and clear caches. Please re-open if problems persist.
Comment #14.0
(not verified) CreditAttribution: commentedAlong with this module I was also disabling the 'Hierarchical Select' module, simultaneously.