Basically, it looks like the Auth data is not refreshed on each page load. I can understand why you wouldn't want to do this - performance notwithstanding - but I've run into a few issues with it myself (primarily dealing with having an online store where the customer could change their email address, etc - all stored in the session, so it didn't actually update when they saved the changes).
There's probably an alternate solution, I'm thinking somewhere along the lines of forcing a fresh check against the database every time the page is loaded. Maybe from AppController::beforeFilter(), for example. No idea what form that would take yet though. On May 22, 5:55 pm, "b logica" <[EMAIL PROTECTED]> wrote: > On Thu, May 22, 2008 at 11:28 AM, theandystratton > > <[EMAIL PROTECTED]> wrote: > > >> I don't understand what you're trying to do here. Are you trying to > >> refresh the $user variable or the data in the session? > > > I'm trying to find an easy way to refresh the data held in $this->Auth- > >>user() > > But you're assigning *from* Auth, not *to* it. > > > is that just pointing to the "User" value in the session? > > I'm not sure how the Auth object maps to the values in the Session. > > Yes, Look at the source for Auth::user(). It's grabbing it from the session. > > Strangely though, I'm suddenly seeing an eerily similar problem in my > own app :-/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
