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.
Just updated to today's version of OG 7.x-1.1 and got the following:
Class 'OgMetadataController' not found in /sites/all/modules/entity/entity.info.inc on line 23
Marking critical since, well...it hosed everything :)
Comments
Comment #1
Rob_Feature CreditAttribution: Rob_Feature commentedAfter this I got a bunch of notices about migrating data...maybe it was related? (didn't have OG migrate module enabled when I got this error...). Site came back up, so downgrading status.
Comment #2
amitaibuPlease reopen if update.php + cache clear + og migrate didn't help
Comment #3
Rob_Feature CreditAttribution: Rob_Feature commentedIt appears this went away after og migrate.
Comment #4
gumdrop CreditAttribution: gumdrop commentedOK managed to clear cache
Comment #5
amitaibuComment #6
mobonobomo CreditAttribution: mobonobomo commentedWhere can I find "og migrate"? I'm getting the same error:
Fatal error: Class 'OgMetadataController' not found in /sites/all/modules/entity/entity.info.inc on line 23
...on upgrade to OG 7.x-1.1. Also, I upgraded Entity API to 7.x-1.0-beta10; is there a recommended version of Entity API?
Comment #7
stevebab CreditAttribution: stevebab commentedExact same error here -- I can't get to admin/build/modules (or /admin or /* or anything other than the home page) in order to enable og migrate... I get a white screen on every url.
Update.php returns "Fatal error: Class 'OgMetadataController' not found in /sites/all/modules/entity/entity.info.inc on line 23" .
Any help out there?
Comment #8
MGParisi CreditAttribution: MGParisi commentedsame as #7,
Couldnt uninstall OG, hosed everything... Replacing OG, no help... Changing version of Entity, sorry...
Comment #9
MGParisi CreditAttribution: MGParisi commentedThank God for Backup and Migrate, lost 8 minutes of data. Ran Migrate, but cant uninstall without crashing my site.
Edit: OG Uninstalls list?
Comment #10
MGParisi CreditAttribution: MGParisi commentedgot rid of it... I don't know if I can ever install it again:(
I had to remove the node panel, all views (or disable them), and just about everything that was related to it, including fields. Then I un-checked it, got an error, had no uninstall.. after that I went into the database, cleaned out the system table of all og starting fields and deleted all og tables.... I hope it all works right, but I got a backup.
Anything else that has to be cleaned up?
Comment #11
BrightBold@MGParisi - See my comment #1182966-2: Cannot fully uninstall or reinstall OG for all the things I deleted from the database when I was having trouble uninstalling and reinstalling OG (as a result, I believe, of #943772: field_delete_field() and others fail for inactive fields.)
Comment #12
RobKoberg CreditAttribution: RobKoberg commentedAfter updating og, I was having the same problem and now have a related problem. I combed through the DB and removed everything I could find related to OG (download sql dump and search for Og and og_). After cleaning everything(?), I tried to reinstall og, which failed. After cleaning again, I tried og-dev. When I install (through drush or the drupal modules ui) og says it is enabled in the web ui but no og tables are created. drush pm-info og says it is not installed. Entries *are* added to the system, registry and registry_files table, so I assume that is why the web ui says it is installed. Running drush updb and cache-clear and core-cron (last two many, many times) does nothing as I think the code pasted below stops everything?? Any idea on how to fix or further debug? I saw something earlier that said to run an individual update, but how do you run a specific update? I can't find anything relevant about how to do this from google or drupal searches.
It seems the problem is around line 202 of og.module (og-dev):
The relevant part of the stack trace is:
Comment #13
RobKoberg CreditAttribution: RobKoberg commentedBTW, when trying to disable the psuedo-enabled og module, I get this stack trace:
Comment #14
BrightBold@RobKoberg - Your stack trace is over my head, but I noticed you searched your SQL dump for "og" and "og_", but if you look at the link in my comment #11, you'll see that some of the entries used "group" instead of "og." So I'd recommend re-trying your uninstall/delete process but including "group" in your search.
Comment #15
RobKoberg CreditAttribution: RobKoberg commentedStarted fresh... One thing I am seeing is OG and UUID do not work together. I had installed UUID for promoting between staging and/or dev versions. I had hoped to be able to use node export features to get content in my 'new' version.
Initially, I had installed UUID before OG and OG would not install. Started fresh again... and enabled things in very small groups and this is where I noticed the incompatibility. Can't spend time digging too deep right now as I have to have this site up and running tomorrow.
Comment #16
renat CreditAttribution: renat commentedFaced the same problem trying to uninstall OG-7.1, so subscribe. Drupal 7.8, cache was cleared, cron was fired, update.php was fired, OG Migrate was fired, too.
Comment #17
amitaibu> I had installed UUID before OG and OG would not install
I don't know this module, but if you have other updates I'd be happy to hear.
Comment #18
Anonymous (not verified) CreditAttribution: Anonymous commentedSince there hasn't been much help with this, here's a quick and dirty fix to get the site back online...
1) enable og_migrate module manually: UPDATE system SET status=1 WHERE name = 'og_migrate';
2) Create og_migrate table:
3) edit sites/all/modules/entity/entity.info.inc and add the following after line 22, so it looks like this:
4) Remove line from sites/all/modules/entity/entity.info.inc
Congrats, your site should be running again. As far as I can tell from looking at what og_migrate does, I don't believe this should cause any lasting problems and the site should be fine after this, no guarantees though... Also some of these steps may not be necessary or could be done in different order, but this is what I did and it worked so...
Comment #19
WriteCo CreditAttribution: WriteCo commentedMy site is not working at all. I cannot wait to get rid of organic groups. I cannot run cron, I cannot clear caches, I cannot run the update script, I can only see pages that were cached on my system. I have tried the various fixes for OG and I only get new errors.
How do I get rid of OG from the DB or command line or some combination of anything, since the web site is completely hosed?
Comment #20
BrightBold@writeco — Have you tried the database deletions I link to in #11? That worked for me. You can also clear the cache from the database by truncating (not dropping!) all tables that start with "cache".
Comment #21
WriteCo CreditAttribution: WriteCo commentedAlright. I rolled back OG, entity, and views to previous versions in hopes of restoring previous compatibility. When that didn't work, go figure, I disabled those modules in the DB. Like, what's it gonna hurt?, the site is hosed, anyway. I then cleared the main cache and any other cache in the DB that looked like it might be relevant. Still no site, but, woohoo, just shoot me, I got my update page back. No updates are necessary, according to my site, but bookoo errors from OG_Migrate.
I re-enabled entity and views, der (duh), and disabled something that threw off an error. Cleared all caches at the DB again, went through update again for some new errors and no updates, but now I can get a page and, more importantly, my modules page.
I disabled all modules using entity or views... . I deleted the Filtered HTML text format because it threw off errors and I just don't give a flip anymore. I grabbed the latest releases of my rolled back modules, updated the site, and errors begone!
Now I am going back to uninstalling OG completely and I am trying to find the table that contains that disabled text format so I can re-enable it and recover the content that disappeared with the format.
I really had other plans this weekend.
Comment #22
drasgardian CreditAttribution: drasgardian commentedI managed to clear this issue by running the following with drush
The issue relates to #996236: drupal_flush_all_caches() does not clear entity info cache
Comment #23
srsbl CreditAttribution: srsbl commentedAlso getting the message of several classes (OgMetadataController, OgMembershipTypeUIController, OgViewsController) not found in entity.
Comment #24
zhenjan CreditAttribution: zhenjan commentedlooks, that problem is not solved? when i'm trying to uninstall OG module (switch off module on admin/modules page and after delete it in Uninstall tab) i'm getting the same error. i'm using the latest version of the module. any of the solution above doesn't works for me. Is it a way to delete this module?
Comment #25
nicholasyonko CreditAttribution: nicholasyonko commentedThis fixed it for me.
Comment #26
ununpentium CreditAttribution: ununpentium commentedThe solution in #20 worked in making the website accessible again; no need to delete any tables:
OG has a horrible uninstall process.
Comment #27
fagoMake sure you've updated to drupal 7.12, that should fix entity-cache clearing issues.
Comment #28
thinkyhead CreditAttribution: thinkyhead commentedUsing Drupal 7.23 I ran into issues updating to the latest OG and Entity modules. It threw this error, plus complained about the missing field property getter function. To get around it all I installed these related modules manually instead of using drush, and ran updb after each install. Sometimes it's just a matter of OG not having a lower weight than the other modules that depend on it.