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.
When trying to run the update function for this module, I got the following fatal error:
An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page
An error occurred. http://www.mysite.com/update.php?id=21&op=do
Fatal error: Call to undefined function _globalredirect_get_settings() in /path/to/drupal/sites/all/modules/contrib/globalredirect/globalredirect.install on line 31
Comment | File | Size | Author |
---|---|---|---|
#11 | modules_globalredirect.7.x-1.x..local_.patch | 11.51 KB | pillarsdotnet |
#11 | modules_globalredirect.master..local_.patch | 10.05 KB | pillarsdotnet |
#8 | modules_globalredirect.patch | 433 bytes | pillarsdotnet |
Comments
Comment #1
pickerel CreditAttribution: pickerel commentedThe missing function is in globalredirect.module. I copied it over to the .install file and ran update with no problem.
Comment #2
adeb CreditAttribution: adeb commentedThank you, solved my problem.
Comment #3
Dave ReidThe easy solution was to add a drupal_load('module', 'globalredirect') right before calling the function. This has been fixed in the lastest CVS:
http://drupal.org/cvs?commit=434744
http://drupal.org/cvs?commit=434746
Comment #5
SebCorbin CreditAttribution: SebCorbin commentedI got the error back while upgrading from D6, the patch fixed the error.
Comment #6
bfroehle CreditAttribution: bfroehle commentedSebCorbin: This was already fixed in the development branch after 7.x-1.3. See http://ftp.drupal.org/files/projects/globalredirect-HEAD.tar.gz
-Brad
Comment #8
pillarsdotnet CreditAttribution: pillarsdotnet commentedApparently the fix in #3 didn't survive the Great Git Migration.
Comment #9
bfroehle CreditAttribution: bfroehle commentedIt was fixed right here: http://drupalcode.org/project/globalredirect.git/commitdiff/94534de
The confusion is coming from #1045842: Development releases link to wrong branch which is that all of the fixes are going into the master branch which is != to the 7.x-1.x branch.
Comment #10
pillarsdotnet CreditAttribution: pillarsdotnet commentedSo should I be pulling from 7.x-1.x or from master? Or both?
And when I submit a patch relative to "master" which is different from "7.x-1.x" should I set the version to "<none>" since there is no version option labeled "master" ?
Wouldn't it be simpler to just merge the changes in master back into the 7.x-1.x branch?
Or delete the 7.x-1.x branch and then rename master to 7.x-1.x ?
Or rename the master branch to 7.x-2.x and release against that?
Comment #11
pillarsdotnet CreditAttribution: pillarsdotnet commentedWell, I answered my own question. I checked out "master" and it totally broke my site.
Okay, I've created a functional local branch combining the 7.x-1.x branch with the master branch.
So here are two patches.
Comment #12
Dave ReidThis is now fixed on the correct branch, 7.x-1.x.