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.
Cannot update or install og where og is already installed on server.
--It won't overwrite the installed module and removing the og moduel will kill the site.
--It did successfully overwrite on my home installation.
I have all og sub modules off but cannot switch og off because it reports: needed in fields shown in field list.
Have previously tried removing og fields from content types and found it renders content types invisible to Add Content.
On my home site I cannot use og migrate tool as it finds errors in membership, Dont know what to do about that
Comment | File | Size | Author |
---|---|---|---|
#6 | Screen Shot 2015-05-29 at 2.07.11 PM.png | 135.15 KB | kyletaylored |
og-migrate-failed.png | 51.18 KB | arelem | |
fieldlist.png | 54.89 KB | arelem |
Comments
Comment #1
amitaibuDid you execute update.php?
Comment #2
JonnyAnderson CreditAttribution: JonnyAnderson commentedI believe I'm having the same issue. Whenever I attempt to run the og-migrate, I am returned to the administrative configuration page/overlay with the same
message displaying.
I have run the update script and have run it multiple times just to be sure. I either get the "No pending updates" message or I receive the following error:
Comment #3
amitaibuPlease read the fatal error message -- it's not OG.
Comment #4
JonnyAnderson CreditAttribution: JonnyAnderson commentedI understand that update error isn't OG, however, that doesn't occur normally, nor does it explain why the og-migrate isn't executing.
Comment #5
jastraat CreditAttribution: jastraat commentedThe og_create_perms module is calling a function that was defined in the OG module but doesn't exist in the new 7.x-2.x version.
og_create_perms is not compatible with the new 2.x version of OG, but you shouldn't need it anyway since OG added group-based create permissions. Just disable the og_create_perms module.
Comment #6
kyletaylored CreditAttribution: kyletaylored commentedSo we're actually upgrading a site from OG 7.x-1.4 to 2.7 and we're getting this error during the migration.
Any help with this? I've tried 2.x dev as well, but no luck.
Comment #7
jastraat CreditAttribution: jastraat commentedI'm not sure about the first part, but the 2nd half of the error is due to a change the migration module made: https://www.drupal.org/node/1928956 It depreciated the syntax that the og migrate script is using, but it shouldn't make it fail. That must be from another cause.