I don't know how to do this without doing stuffs in the plugin folder

Why do you want to overload sfGuardUser?

On Fri, May 15, 2009 at 1:48 PM, H. Tuttle <lacyrhoa...@gmail.com> wrote:
>
> Yes, that's right.  You can make your own sfGuardAuth module.
>
> The other question almost as important is how do you overload the
> sfGuardUser class?  I have tried making my own sfGuardUser.php in the /
> lib/model directory but with no success.  I'd like to be able to stay
> completely out of the plugin folders.
>
>
>
> On May 14, 7:42 pm, Sid Bachtiar <sid.bacht...@gmail.com> wrote:
>> That should be the default behaviour of sfGuardPlugin
>>
>> But if you want to customize the signinSuccess.php, don't do it on the
>> plugin directory.
>>
>> Do it be creating
>> "myproject/myapp/modules/sfGuardAuth/templates/signinSuccess.php" (do
>> this manually, don't use symfony command line, e.g.: don't use symfony
>> init-module).
>>
>> This should override the plugin's signinSuccess.php
>>
>> On Fri, May 15, 2009 at 12:23 PM, nick <lal...@teamlalala.com> wrote:
>>
>> > If someone tries to go to a secure page, and they are not logged in,
>> > they get redirected to the login page, which has this template:
>>
>> > plugins/sfGuardPlugin/modules/sfGuardAuth/templates/signinSucess.php
>>
>> > I'd like to remember where the user was coming from, and then send
>> > them there if they log in successfully. Do I directly edit
>> > signinSuccess.php, or do I override it somewhere else?
>>
>> --
>> Blue Horn Ltd - System Developmenthttp://bluehorn.co.nz
> >
>



-- 
Blue Horn Ltd - System Development
http://bluehorn.co.nz

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

Reply via email to