Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
menu system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Sep 2007 at 01:37 UTC
Updated:
17 Oct 2007 at 13:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
chx commentedI wonder why jjeff have not rolled this trivial patch...
Comment #2
jjeff commentedBecause jjeff is lazy! ...and he has not quite figured out the new menu system yet... and did I mention lazy?
:-)
Thanks chx
Comment #3
gábor hojtsyHm, chx, you proposed to remove the anonymous check on user/login here: http://drupal.org/node/172765 So I'd rather not add it back in now just to play limbo with that fix. Maybe we can come up with something which fits both issues?
Comment #4
Tobias Maier commentedgabor: i don't think you are right.
take a look at comment #13 of the issue mentioned.
it talks about the "user" path NOT about "user/login", like this patch of chx
Comment #5
catchIn that case, setting back to needs review. I agree this is a very useful behaviour to have and it'd be a shame to lose it.
Comment #6
chx commentedThen I think this issue is again RTBC. Yes, the linked issue was about the page user which has double role. Actually that patch broke this one, because before that it inherited from 'user' now it needs explicit definition. user/register has no such problems, it has its own complicated access callback. And user/password also has anonymous check. Only user/login is without an explicit check.
Comment #7
moshe weitzman commentedSeems quite reasonable to me.
Comment #8
gábor hojtsyThanks for the explanation, I really overlooked the fundamental difference between the two patches. This is now committed!
Comment #9
(not verified) commented