I understand, and you're right that our main goal is a login page that
redirects to a specific location but it would be nice to also
allow users to bookmark or shortcut directly to specific pages where
they would be authenticated before redirection to that page (isn't
Cake great!).
I guess th
I wrote a lengthy reply earlier but I guess it wasn't delivered.
The simplest way to describe our application would be that of a web-based
CRM. Most site pages will be user-specific and most users will access those
pages through a 'login' page that acts as gateway to the application and
redirects
I guess I am having a hard time understanding exactly what you expect
to happen. Initially, I thought you wanted the login to always
redirect to the same location. This would be solved with autoRedirect
= false and handling it in the login action. Maybe you could provide a
better example, with som
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
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" gro
We're working on our first cake app with the latest 1.2 RC3 and we've
run across the situation discussed in ticket 5057.
https://trac.cakephp.org/ticket/5057
We're using both the auth and acl components. If a user accesses a
page that should be auth'ed and acl'ed then they're redirected to the
