Closed (fixed)
Project:
Nodequeue
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Jul 2008 at 20:31 UTC
Updated:
31 Aug 2008 at 03:12 UTC
Jump to comment: Most recent file
Comments
Comment #1
coltraneWould a variable_get() around the nodequeue tab item in hook_menu() do the trick?
Comment #2
coltraneI tried this, but no it doesn't seem to be enough. Likely because of menu caching ... hmmn.
Comment #3
coltraneIf the cache is cleared problem is solved. So, patch attached wraps the menu item in a variable_get() on nodequeue_use_tab. What's preferred, on submit of the admin setting do menu_rebuild() or tell the user (dsm or otherwise) to clear the cache themselves?
Comment #4
ezra-g commented#289683: Queue Names Missing in node-edit-tab and #281040: Subqueue name changes don't affect individual subqueues may be symptoms of the same problem that this patch addresses.
Comment #5
ezra-g commentedWhile this patch should address cases where the site-wide setting is not observed, it does not resolve individual nodes that have tabs even though they are not eligible for any queues. That's because nodequeue_node_tab is being called regardless of whether a node is eligible.
Comment #6
ezra-g commentedI rerolled this and defined a custom nodequeue_node_tab access callback, which took care of the problem in more cases, however the tab still lingers in the menu cache after a node has become ineligible. We'll need to make this callback non-cache-able.
Comment #7
ezra-g commentedI think we got it here.
Comment #8
ezra-g commentedThe solution to this involves writing a new access callback function, and should have been incorporated into #278609: Forward port Modular Access Control to 6 . I will re-roll that patch to include this solution. Leaving this issue open as the bug described here is not a dupe.
Comment #9
ezra-g commentedFixed as part of #278609: Forward port Modular Access Control to 6.
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.