If you add a menu item with a same path as a non cacheable menu item you get weird acccess problems [#54974]

This is ugly. We ripped 'access' TRUE for security reasons. So custom items have no access attribute any more. When a non cacheable (contextual) menu item is added, it won't override the one that's already there (ops) so it will walk up the menu tree until it finds an access . For node/nid items, it'll find node which means that it'll end up with TRUE. If there were no parents defined in the cacheable tree then you are hosed: you get access denied.

Comment	File	Size	Author
#1	menu_29.patch	699 bytes	chx
	menu_28.patch	698 bytes	chx

Comments

Comment #1

chx commented 20 March 2006 at 18:51

Status	File	Size
new	menu_29.patch	699 bytes

I forgot a $

Comment #2

chx commented 21 March 2006 at 22:29

Status:

Reviewed & tested by the community

» Needs work

damn! this is not applicable for 4.6, this bug was introduced in 4.7 with the callback separation patch. But why then some 4.6 sites are broken? Back to drawing board.

Comment #3

dww

we/he/they

commented 27 March 2006 at 11:06

chx, any idea if this bug might be related to #55457? just curious what you think. i haven't had a chance to dig into that other one yet (it's a pretty rare bug, not critical), but i stumbled upon this issue and thought they sounded somewhat similar. let me know what you think.

thanks,
-derek