I think I will just try an upgrade to Symfony 1.2 with a newer version of
the sfGuardPlugin. I don't want to spend hours debugging Symfony's own code.
On Sun, Mar 6, 2011 at 11:49 AM, Drew Sire nathandrews...@gmail.com wrote:
Ya, it seems like the other modules aren't recognizing the
Reproduce Problem
http://184.73.247.117/backend.php
username = d...@buzzybeemarketing.com
password = testing
File
/var/www/html/
palcheck-1.0.com/plugins/sfGuardPlugin/modules/sfGuardAuth/actions/
Here is the code causing the problem. When originally set to @homepage, it
creates an infinite
I had a similar problem when the login success url was the homepage and the
login page was presented when viewing the homepage.
Any possibility that might be part of the issue?
On Mar 6, 2011 5:09 AM, Drew Sire nathandrews...@gmail.com wrote:
Reproduce Problem
http://184.73.247.117/backend.php
Ya, it seems like the other modules aren't recognizing the cookie/session as
authenticated.
On Sun, Mar 6, 2011 at 9:16 AM, Alex Pilon alex.pi...@gmail.com wrote:
I had a similar problem when the login success url was the homepage and the
login page was presented when viewing the homepage.
Hi Drew,
I think it is one of the most used plugins around so we should be able to
help you here.
Can you provide some more information about where you are being told it
can't redirect?
Can you paste the stack trace?
Chris
--
If you want to report a vulnerability issue on symfony, please
