I'd think you'd need to do something with Dispatcher for that. But I have a feeling that, were you to do that, Auth would want to redirect you to the path you originally tried after logging in, resulting in a loop. The loginRedirect path is used for when the user goes directly to login. When Auth, for whatever reason, redirects the user to that view, it remembers where they were going and forwards them afterwards.
Like I said, that's my gut feeling; don't take my word for it. On Fri, May 16, 2008 at 2:21 PM, Andras Kende <[EMAIL PROTECTED]> wrote: > > hello, > > I have a problem with 1.2 auth: > > http://www.kende.com/test/ -> redirects to login = this is good .. > > but for a missing controller/action/view : > > http://www.kende.com/test/dadadmfsf/ -> shows "Not Found" should also > redirect first to login... > > > <?php > class AppController extends Controller { > var $components = > array('Auth'); > function beforeFilter(){ > if (isset($this->Auth)) { > $this->Auth->userModel = 'User'; > $this->Auth->userScope = array('User.disabled' => 0); > $this->Auth->loginAction = '/users/login'; > $this->Auth->loginRedirect = '/websites/'; > } > } > } > ?> > > > Thank you, > > Andras Kende > http://www.kende.com > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
