Check that you have not leading or trading spaces.
http://bin.cakephp.org/saved/33005

On Tue, Jun 17, 2008 at 10:53 AM, Chris Hartjes <[EMAIL PROTECTED]> wrote:
>
> On Tue, Jun 17, 2008 at 9:43 AM, Aaron <[EMAIL PROTECTED]> wrote:
>>
>> Thanks for the quick response but I have already tried that and it
>> doesn't make a difference.  I've moved the beforeFilter() stuff into
>> app_controller.php, into users_controller.php and other combinations.
>> Looking at the stack trace it is getting into the Auth component but
>> the component's $this->user() comes back null.  $sessionKey isn't
>> found in the session.  The session appears to get corrupted or isn't
>> set properly.  _loggedIn is also blank.
>>
>
> I'm using Auth just fine with a constantly-updated version of Cake
> from SVN, but aren't using anything other than the conventions.  I
> have also seen users experiencing problems with sessions when the
> security level in config/core.php is set to high.  I always roll with
> it set to medium, but your mileage may vary.
>
> If you setting Auth-related things in your app_controller's
> beforeFilter function, you should have a beforeFilter() method in your
> other controllers that inherits from app_controller.  I have always
> done this and never experienced any problems with Auth, even when
> going with non-standard Auth configurations.
>
> If the problem still persists, I suggest that you file a ticket at
> trac.cakephp.org so that the issue will get looked at it.
>
> --
> Chris Hartjes
> Internet Loudmouth
> Motto for 2008: "Moving from herding elephants to handling snakes..."
> @TheKeyBoard: http://www.littlehart.net/atthekeyboard
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to