Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I HAD a bad habit of creating backups of modules in the same directory the modules reside in prior to extracting the new tar file of the updated module. I would simply mv moduleName moduleName.BAK then tar xvzf moduleName.tar.gz and clean it all up later... But, while trying to get to the bottom of why the update status module was not reporting correctly, I saw that it was actually reading all the old .BAKs that existed in the module's directory. So I fixed that problem, but then learned that somewhere prior to this in, I am sure, a sleep deprived module updating session, I didn't properly rename the Organic Groups module. It was 'og.BAK2' rather than 'og'. When I removed all the .BAK directories from the modules directory, I got the following error:
Fatal error: Call to undefined function og_get_group_context() in /var/www/drupal/sites/all/modules/og_vocab/og_vocab.module on line 109
So, I renamed the latest 'og' module to 'og.BAK2' and the error goes away. Is there an easy fix to this, or am I stuck with a poorly named module?
Thanks
Comments
Comment #1
David Lesieur commentedComment #2
kpm commentedSolved by disabling all OG modules and those that depend on OG or OG depends on... Renamed the misnamed og.BAK2 to og, and the error went away.