Call to undefined function _globalredirect_get_settings() [#861994]

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
#11	modules_globalredirect.master..local_.patch	10.05 KB	pillarsdotnet
#11
#8	modules_globalredirect.patch	433 bytes	pillarsdotnet
#8

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

pickerel CreditAttribution: pickerel commented 18 August 2010 at 18:53

The 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 commented 1 September 2010 at 19:13

Thank you, solved my problem.

Comment #3

Dave Reid

he/him

English

Nebraska USA

CreditAttribution: Dave Reid commented 11 October 2010 at 23:30

Status:

Active

» Fixed

The 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 #4

25 October 2010 at 23:40

Status:

Fixed

» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Comment #5

SebCorbin CreditAttribution: SebCorbin commented 31 January 2011 at 21:55

Version:	6.x-1.3-alpha1	» 7.x-1.3
Status:	Closed (fixed)	» Reviewed & tested by the community

I got the error back while upgrading from D6, the patch fixed the error.

Comment #6

bfroehle CreditAttribution: bfroehle commented 2 February 2011 at 03:20

Status:

Reviewed & tested by the community

» Fixed

SebCorbin: 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 #7

16 February 2011 at 03:30

Status:

Fixed

» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Comment #8

pillarsdotnet CreditAttribution: pillarsdotnet commented 26 February 2011 at 01:25

Version:	7.x-1.3	» 7.x-1.x-dev
Status:	Closed (fixed)	» Needs review

File	Size
modules_globalredirect.patch	433 bytes

Apparently the fix in #3 didn't survive the Great Git Migration.

Comment #9

bfroehle CreditAttribution: bfroehle commented 26 February 2011 at 01:36

Status:

Needs review

» Closed (fixed)

It 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 commented 26 February 2011 at 06:05

Category:	bug	» support
Status:	Closed (fixed)	» Active

So 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?