Yes, but that 1% where it IS needed is critical ;-) I agree that a refresh method would be useful, and if present would allow me to add it to the App Controller to get the effect I'm after. That way everyone is happy :-)
Anyone know how to refresh the user record? Is it simply a case of setting the Auth Session User var? On Jul 14, 9:58 am, AD7six <[EMAIL PROTECTED]> wrote: > On Jul 14, 10:24 am, RichardAtHome <[EMAIL PROTECTED]> wrote: > > > How can this be the preferred behaviour? > > > What do you do if you get a 'bad' user? Even if you delete his user > > record you are helpless to stop him until he voluntarily logs out! > > > Or, what if you have a regular user who needs his 'role' changing? > > > Granted, profile edits and changes in roles are required less often, > > but the security issue alone is enough to warant a refresh on every > > page. A quick read of the database is hardly going to kill the system. > > And is, as Jonathan Snook pointed out, needless 99% of the time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
