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.
The combination of Global Redirect 1.2 and NodeQueue 2.2 is apparently very bad. If Global Redirect is turned on, the Views UI for nodequeue doesn't work (none of the filter options for nodequeue are visible). Turning off global redirect fixes it.
Comments
Comment #1
Steve Hanson CreditAttribution: Steve Hanson commentedThat note SHOULD have said global redirect 1.3, not 1.2
Global Redirect version 1.2 doesnt seem to cause the problem - just 1.3
Comment #2
ezra-g CreditAttribution: ezra-g commentedSubscribing to keep up to date on this and the corresponding issue at #279439: Global Redirect Module conflicts with Nodequeue
Comment #3
nicholasThompsonI've just installed Global Redirect 1.3 and NodeQueue 2.2 onto a clean Drupal 5.7 install and I cannot replicate this. NodeQueue functions (or appears to at least) as intended.
I'll try to test out ViewsUI with it too... (I need an "active - in progress" status!!)
Comment #4
nicholasThompsonAhh I see - its Views UI which breaks in relation to NodeQueue..
Now whats REALLY interesting is it only fixes if you disable the whole module. If you rename the function
globalredirect_init
to something likeglobalredirect_inits
so it doesn't get executed then the problem still exists...This is VERY peculiar!
Comment #5
John Morahan CreditAttribution: John Morahan commentedWhat's happening is this:
One possible fix is to increase the weight of GR in the system table. This fixes the problem for OG, I haven't tested with NQ but I expect it would work there too.
The reason renaming the function doesn't seem to work is probably because the old stuff is still cached in cache_views.
Comment #6
nicholasThompsonI just spent an hour debugging and realised that the weight solved it. I then refreshed this page to find out you'd posted the solution ;-)
I'm gonna commit this as a 1.3.1 update. This will also fix another issue in the queue at the same time.
Personally I think it would be good practice to have ALL hook implementations in the
.module
file rather than in includes... But that's just me!Comment #7
nicholasThompsonThis should be fixed in 1.3.1 now...
Please note that an upgrade to 1.3.1 will involve running the update.php script. Drupal Administration page will warn you about an out of date schema.
Comment #8
Steve Hanson CreditAttribution: Steve Hanson commentedYes, this seems to have fixed a bunch of problems with organic groups and with nodequeue. Thanks for the quick response.
Comment #9
nicholasThompsonNo probs... I broke it - I should fix it ;-) Plus its not like Views, NodeQueue and OG are particularly rare modules!
Comment #10
christefano CreditAttribution: christefano commented#278469 has been marked as a duplicate of this issue. Thanks for fixing this.
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.