Thanks! I did read thoroughly (I thought) :). But if you disable autoRedirect then you lose the nifty feature to auto redirect back to where you were originally going - if someone where to try and directly access a page under auth/acl protection (the opposite of our main goal but you never know what users will want). Again, I'm new to Cake, but I'm sure that I could figure out where cake stores that originally requested URL and handle that redirect myself too - but why go to all the trouble to do something that Cake will do automatically? (BTW, as mentioned - my problem was fixed by dropping the session value in beforeFilter)
It seems pretty simple that if the loginRedirect value == the url you're trying to access then in that one case there's not a need to auto-redirect. :) Why not have cake automatically drop that session value (auth.redirect) if you're already there? Our app works and I don't have an ax to grind. I'm just trying to help out. On Oct 22, 3:48 am, Gwoo <[EMAIL PROTECTED]> wrote: > reading the comment on the ticket thoroughly would provide the > solution...."You can set autoRedirect = false, then handle the > redirect in the login action" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
