PHP Fatal error: Call to undefined function _menu_item_is_accessible() in [snip]/modules/globalredirect/globalredirect.module on line 36

I get this error when trying to logout via http://example.com/logout

Comments

sillygwailo’s picture

sillygwailo
Location Toronto, ON
commented

Also, I found I needed to clear the cache_page table in order to see the site again after this.

nicholasthompson’s picture

nicholasthompson
Primary language English
commented
Priority: Normal » Critical

I'll take a look - I thought I'd tested the logout...

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
commented

yep, i'm seeing the same behavior. if you need any more info to address the problem let me know.

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

I need more info - on my clean 5.7 install with just GR enabled (and Path) logout works fine.

What versions of stuff are you running? Any other modules?

EDIT: Have you run the update.php script from the modules page? 1.3.1 updates the system table to set the weight to make GR run last.

dgsiegel’s picture

dgsiegel commented

yes, i ran update.php, but the problem still remains.

i tested 1.3 and 1.3-1, and both are failing. seems like we have to stick to 1.2 until this bug is fixed.

nicholasthompson’s picture

nicholasthompson
Primary language English
commented
Version: 5.x-1.3-1 » 5.x-1.x-dev
Status: Active » Fixed

I have committed a fix to DRUPAL-5 (the dev branch). The fix for #208107: problem with normal mode caching (not just aggressive mode) should solve this. Can you please check.

I will be releasing 1.4 soon hopefully (which should ALSO - in theory - fix a lot of i18n related bugs).

sillygwailo’s picture

sillygwailo
Location Toronto, ON
commented

Did a quick test, first with the "old" module (got WSOD, same error) and updated to DRUPAL-5, and my site runs fine. So in other words, looks good to me.

dgsiegel’s picture

dgsiegel commented

5.x-1.x-dev seems to work for me, thanks!

Anonymous’s picture

Anonymous (not verified) commented

I also had the issue after I updated the module yesterday. The bad news is, google went in between and indexed the error message instead on the main page... ouch.

I installed the dev version and ran the update script. Evrything seems fine now.
Maybe you should prevent people frome downloading the 5.x-1.3-1 version, if it is buggy ? The worst thing with the bug is the fact that an admin won't see it, only anonymous users...

nicholasthompson’s picture

nicholasthompson
Primary language English
commented

The bug itself appears to be triggered by something else. I, for example, am running 1.3.1 on www.thingy-ma-jig.co.uk and anonymous users appear to have no problems that I know of..

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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

fax8’s picture

fax8 commented
Status: Closed (fixed) » Active

Please note that, as of 6 November 2008, this bug is still active in the "stable" version.

As this bug is absolutely critical the fix contained in 5.x-dev should be promoted to a stable version.

nicholasthompson’s picture

nicholasthompson
Primary language English
commented
Status: Active » Fixed

Marking as fixed as this is working in 5.x-dev which is imminently becoming the 5.x-1.4 release.

Status: Fixed » Closed (fixed)

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