Global Redirect Module conflicts with Nodequeue [#279439]

I'm a little confused by this - I am running multiple sites off of a common code base. On the one where I had been using NodeQueue all along, everything seems to work fine after upgrading to 2.2. However, on 2 of the sites I am now trying to start using Node Queue and discover that no matter what I try, I cannot get the node queue filters to appear in the views UI - making it pretty hard to build queries based on the node queue. I cannot see any good reason for this that is obvious to me. Anyone have any suggestions on how I might approach this? I've tried dropping node queue completely and re-installing, but that seems to be no help. I'm not seeing any errors in the watchdog or web server logs.

Comments

Comment #1

ezra-g CreditAttribution: ezra-g commented 7 July 2008 at 15:41

Category:

bug

» support

Try clearing your Views cache on both sites and reporting the results here.

**Corrected for a stupid error in the database query -- Please note the correction **
You can clear the Views cache by accessing the database and typing 'DELETE FROM cache_views' (or use a table prefix if necessary).

Comment #2

Steve Hanson CreditAttribution: Steve Hanson commented 7 July 2008 at 15:53

That was one of the first things I tried - no joy there -

Comment #3

Steve Hanson CreditAttribution: Steve Hanson commented 7 July 2008 at 18:45

Title:

Node Queue Filters not appearing in Views UI

» Global Redirect Module conflicts with Nodequeue

Okay - I found the problem.

node queue filters don't appear if the Global Redirect module is enabled. If I turn off Global redirect, life is good. If I turn it on, the node queue filters disappear - Global Redirect 1.3,. Nodequeue 2.2. I'm filing a bug report for Global Redirect 1.3