Thanks, very helpful. Paul
On 30 July 2010 11:54, Oscar Saraza <oscarsar...@gmail.com> wrote: > I already do something like that... I think. > > My solution: to create a subclass of the symfony class sfActions (in > my case ssActions, placed in the lib folder). This subclass contains > the preExecute method with the authentication routines. > > After that, every sfAction subclass must inherits from ssActions. That > way, you can use $this->getUser() to get information you need to do > your checks and avoid to duplicate your code in every action of your > app. > > Hope it helps. > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
