> What about defining your own user_login_url method on LoginSystem? That's exactly what I did. See the top of the thread. What I'm trying to avoid is substituting an entire method override for "authenticate" in my extension. I didn't actually modify the LoginSystem file that comes with radiant, just overrode the method from my extension. Unfortunately, this approach requires me to copy the entire block of code (as it appears in your original file) and make a minor modification. If you ever change it, then I don't get your changes because of my complete override. My goal was to leave your code as intact as possible and override the least amount at just the precise location. The only way I see to do that is to reroute the login_url from your backend 'admin/login' to my frontend 'user/login'. I already have a user_login_url, but I need your LoginSystem to acknowledge it.
Thanks for giving this a bit of thought. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
