[development] Protecting URLS From Path
nan_wich at bellsouth.net
Tue Nov 23 02:59:51 UTC 2010
I agree. Another option is to use hook_form_alter to add a submission handler
that checks for a path that already exists. It would be more work, but probably
a bit more user friendly.
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Adam B. Ross <grayside at gmail.com>
To: development at drupal.org
Sent: Mon, November 22, 2010 9:55:41 PM
Subject: Re: [development] Protecting URLS From Path
hook_menu_alter() sounds right. You could also use some sort of
detection mechanism in hook_menu_alter() to report that the path was
I am a firm believer that this sort of thing should be handled by
negotiation between module maintainers and documentation, rather than
by beginning a programmatic war for possession of namespaces.
On Mon, Nov 22, 2010 at 6:15 PM, nan wich <nan_wich at bellsouth.net> wrote:
> My first thought would be a hook_menu_alter to set it back to the right
> path. Granted most of the time it will be unnecessary overhead, but if the
> path is critical, it should work.
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
> From: David Metzler <metzler.dl at gmail.com>
> To: development at drupal.org
> Sent: Mon, November 22, 2010 8:24:25 PM
> Subject: [development] Protecting URLS From Path
> I maintain an SSO module that has an alternate login path (cas instead of
> user/login). I recently got a post asking if there was a way for me to
> programmatically protect it from being overridden.
> A user had created a page describing the single sign on process and given it
> the same URL as my menu_hook was registered, thus overriding the behavior
> provided by my module.
> So I thought I'd ask. Anyone know of a way for me to ensure that other menu
> paths (specifically aliases) cannot override the one provided by my module?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development