Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
Apparently, this issue is related to calling the jQuery helper. I built out an empty action and an empty template, and they work perfectly, until I added a call to the jQuery helper, so I removed everything else, nothing in the action and one line in the template: That allows me to reproduce the issue. However anywhere that I remove the use_helper call (or change it to something besides jQuery) everything works as expected. Unfortunately, I don't have any local changes to the sfJqueryReloadedPlugin. Does anyone have any suggestions as to where I might next look to determine what is happening (or rather, how this is happening)? On Tue, Jul 6, 2010 at 7:05 AM, ashton honnecke wrote: > It is present in only one of five apps (all in the same project). It > is definitely not the server. It happens to all the modules in one > app, except for it seems, when I return renderText directly in the > action. This leads me to suspect (ridiculously enough) that it is > something in the layout, which I am trying to confirm now. > > On Tue, Jul 6, 2010 at 2:59 AM, Tom Ptacnik wrote: >> Did you tried to run this app on a different server? .. then you will >> know if the problem is in the app or in your server. >> >> >> On 5 čnc, 04:31, ashton honnecke wrote: >>> This behavior (Inability to stay signed in) went away in four of five >>> apps when I altered the session_name. However, it remains on one of >>> the apps. That is to say that in my backend app (as well as others) I >>> can login correctly but in the frontend app though, I can only stay >>> logged in for one page load (so I have to login for every page). I'm >>> sure that this is from something that I have done wrong. Does anyone >>> have any suggestions about where to look or how to debug this? >>> >>> >>> >>> On Tue, Jun 22, 2010 at 8:55 AM, ashton honnecke >>> wrote: >>> > I hadn't altered factories.yml at all. >>> > Being in there I tried changing the session_name (it was just the >>> > default 'symfony') and the site stopped exhibiting the broken >>> > behavior. This still doesn't make sense to me, but altering the >>> > session_name certainly fixed things for now. >>> >>> > I have a few apps with the default cookie name, could that be the issue? >>> >>> > On Tue, Jun 22, 2010 at 8:44 AM, pghoratiu wrote: >>> >> The defaults for session storage are defined in apps/frontend/config/ >>> >> factories.yml. >>> >> If there is nothing changed vs. the defaults than the PHP session >>> >> storage is used, in this case you can check >>> >> the serialized sessions stored usually somewhere in /var/lib/php5 (or >>> >> something similar, depending on your Linux distribution). >>> >>> >> gabriel >>> >>> >> On Jun 22, 5:33 pm, ashton honnecke wrote: >>> >>> I'm not sure. How do I check on this? >>> >>> >>> I tried reverting my dev instance to a known version (the same one >>> >>> that is in production and can be logged in to), it still exhibits this >>> >>> behavior, so I think that you are probably right that there is >>> >>> something going on outside of the code. What might that be, and do >>> >>> you have any ideas of how I could check? >>> >>> >>> ashton >>> >>> >> -- >>> >> 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 >> >> -- >> 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 >> > -- 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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
It is present in only one of five apps (all in the same project). It is definitely not the server. It happens to all the modules in one app, except for it seems, when I return renderText directly in the action. This leads me to suspect (ridiculously enough) that it is something in the layout, which I am trying to confirm now. On Tue, Jul 6, 2010 at 2:59 AM, Tom Ptacnik wrote: > Did you tried to run this app on a different server? .. then you will > know if the problem is in the app or in your server. > > > On 5 čnc, 04:31, ashton honnecke wrote: >> This behavior (Inability to stay signed in) went away in four of five >> apps when I altered the session_name. However, it remains on one of >> the apps. That is to say that in my backend app (as well as others) I >> can login correctly but in the frontend app though, I can only stay >> logged in for one page load (so I have to login for every page). I'm >> sure that this is from something that I have done wrong. Does anyone >> have any suggestions about where to look or how to debug this? >> >> >> >> On Tue, Jun 22, 2010 at 8:55 AM, ashton honnecke wrote: >> > I hadn't altered factories.yml at all. >> > Being in there I tried changing the session_name (it was just the >> > default 'symfony') and the site stopped exhibiting the broken >> > behavior. This still doesn't make sense to me, but altering the >> > session_name certainly fixed things for now. >> >> > I have a few apps with the default cookie name, could that be the issue? >> >> > On Tue, Jun 22, 2010 at 8:44 AM, pghoratiu wrote: >> >> The defaults for session storage are defined in apps/frontend/config/ >> >> factories.yml. >> >> If there is nothing changed vs. the defaults than the PHP session >> >> storage is used, in this case you can check >> >> the serialized sessions stored usually somewhere in /var/lib/php5 (or >> >> something similar, depending on your Linux distribution). >> >> >> gabriel >> >> >> On Jun 22, 5:33 pm, ashton honnecke wrote: >> >>> I'm not sure. How do I check on this? >> >> >>> I tried reverting my dev instance to a known version (the same one >> >>> that is in production and can be logged in to), it still exhibits this >> >>> behavior, so I think that you are probably right that there is >> >>> something going on outside of the code. What might that be, and do >> >>> you have any ideas of how I could check? >> >> >>> ashton >> >> >> -- >> >> 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 > > -- > 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 > -- 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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
This behavior (Inability to stay signed in) went away in four of five apps when I altered the session_name. However, it remains on one of the apps. That is to say that in my backend app (as well as others) I can login correctly but in the frontend app though, I can only stay logged in for one page load (so I have to login for every page). I'm sure that this is from something that I have done wrong. Does anyone have any suggestions about where to look or how to debug this? On Tue, Jun 22, 2010 at 8:55 AM, ashton honnecke wrote: > I hadn't altered factories.yml at all. > Being in there I tried changing the session_name (it was just the > default 'symfony') and the site stopped exhibiting the broken > behavior. This still doesn't make sense to me, but altering the > session_name certainly fixed things for now. > > I have a few apps with the default cookie name, could that be the issue? > > On Tue, Jun 22, 2010 at 8:44 AM, pghoratiu wrote: >> The defaults for session storage are defined in apps/frontend/config/ >> factories.yml. >> If there is nothing changed vs. the defaults than the PHP session >> storage is used, in this case you can check >> the serialized sessions stored usually somewhere in /var/lib/php5 (or >> something similar, depending on your Linux distribution). >> >> gabriel >> >> >> On Jun 22, 5:33 pm, ashton honnecke wrote: >>> I'm not sure. How do I check on this? >>> >>> I tried reverting my dev instance to a known version (the same one >>> that is in production and can be logged in to), it still exhibits this >>> behavior, so I think that you are probably right that there is >>> something going on outside of the code. What might that be, and do >>> you have any ideas of how I could check? >>> >>> ashton >> >> -- >> 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 >> > -- 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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
I hadn't altered factories.yml at all. Being in there I tried changing the session_name (it was just the default 'symfony') and the site stopped exhibiting the broken behavior. This still doesn't make sense to me, but altering the session_name certainly fixed things for now. I have a few apps with the default cookie name, could that be the issue? On Tue, Jun 22, 2010 at 8:44 AM, pghoratiu wrote: > The defaults for session storage are defined in apps/frontend/config/ > factories.yml. > If there is nothing changed vs. the defaults than the PHP session > storage is used, in this case you can check > the serialized sessions stored usually somewhere in /var/lib/php5 (or > something similar, depending on your Linux distribution). > > gabriel > > > On Jun 22, 5:33 pm, ashton honnecke wrote: >> I'm not sure. How do I check on this? >> >> I tried reverting my dev instance to a known version (the same one >> that is in production and can be logged in to), it still exhibits this >> behavior, so I think that you are probably right that there is >> something going on outside of the code. What might that be, and do >> you have any ideas of how I could check? >> >> ashton > > -- > 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 > -- 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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
I'm not sure. How do I check on this?
I tried reverting my dev instance to a known version (the same one
that is in production and can be logged in to), it still exhibits this
behavior, so I think that you are probably right that there is
something going on outside of the code. What might that be, and do
you have any ideas of how I could check?
ashton
On Tue, Jun 22, 2010 at 6:14 AM, pghoratiu wrote:
> How does symfony store the session in your case, are you using the php
> session or something else?
>
> gabriel
>
> On Jun 22, 9:19 am, ashton honnecke wrote:
>> I am able to save information to the session manually:
>> print_r($_SESSION['something']);
>> $_SESSION['something'] = array('7');
>>
>> That will save and then print Array ( [0] => 7 ) in a unprotected action.
>
> --
> 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
>
--
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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
I am able to save information to the session manually:
print_r($_SESSION['something']);
$_SESSION['something'] = array('7');
That will save and then print Array ( [0] => 7 ) in a unprotected action.
On Mon, Jun 21, 2010 at 12:14 PM, pghoratiu wrote:
> I would say it's something wrong at the PHP configuration level, what
> is your environment (OS, PHP, symfony version, ...?).
>
> gabriel
>
> On Jun 21, 8:51 pm, ashton honnecke wrote:
>> This is what I have in configuration>user on the page load after sign
>> in (from the webDebugToolbar):
>>
>> attributeHolder:
>> sfGuardSecurityUser: { user_id: '173' }
>>
>> On the next pageload, it goes away (no sfGuardSecurityUser at all)
>>
>> I printed the session at the beginning of an action (right after
>> login) and I got:
>> [sfGuardSecurityUser] => Array
>> (
>> [user_id] => 173
>> )
>>
>> then died before the action was over.
>>
>> Reloading after that got me back to the signin page.
>>
>> I did recently add Profile to the schema (with a 1:1 relationship
>> between User and Profile) and rebuild after that.
>>
>> I tried removing and re-adding the entire plugin with no change in behavior.
>>
>>
>>
>> On Fri, Jun 18, 2010 at 12:57 AM, pghoratiu wrote:
>> > Check the session - the user id should be stored after sign-in.
>> > This can be checked in the web debug toolbar or directly the
>> > serialized session data.
>>
>> > gabriel
>>
>> > On Jun 18, 9:50 am, ashton wrote:
>> >> I'm not sure how I broke things, but I can no longer remain logged in
>> >> beyond one page load (tried clearing cache/using a different browser).
>>
>> >> * When I hit a page, I get the login screen
>> >> * I login successfully
>> >> * The page that I was initially navigating to loads
>> >> * Then next time that I load a page, the signinSuccess form renders
>> >> again.
>>
>> >> Thoughs?
>>
>> >> logs:http://pastebin.com/0302jtfK
>>
>> > --
>> > 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
>
> --
> 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
>
--
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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
Nope, it came back after I cced and rebuilt the models.
On Mon, Jun 21, 2010 at 2:05 PM, ashton honnecke wrote:
> In order to test if the issue lay in the environment or in the code, I
> set up a new vhost and checked everything out again at various
> revisions. I can't seem to reproduce the issue at all on the newly
> checked out vhost. So this issue has been resolved I think.
>
> Thanks!
>
> On Mon, Jun 21, 2010 at 12:37 PM, ashton honnecke wrote:
>> It was working at one point. The issue seems to span all the apps that I
>> have.
>>
>> Red Hat Enterprise Linux Server release 5.4 (Tikanga)
>> PHP 5.2.10 (cli) (built: Aug 6 2009 06:05:50)
>> symfony version 1.4.6-DEV
>>
>> ashton
>>
>> On Mon, Jun 21, 2010 at 12:14 PM, pghoratiu wrote:
>>> I would say it's something wrong at the PHP configuration level, what
>>> is your environment (OS, PHP, symfony version, ...?).
>>>
>>> gabriel
>>>
>>> On Jun 21, 8:51 pm, ashton honnecke wrote:
This is what I have in configuration>user on the page load after sign
in (from the webDebugToolbar):
attributeHolder:
sfGuardSecurityUser: { user_id: '173' }
On the next pageload, it goes away (no sfGuardSecurityUser at all)
I printed the session at the beginning of an action (right after
login) and I got:
[sfGuardSecurityUser] => Array
(
[user_id] => 173
)
then died before the action was over.
Reloading after that got me back to the signin page.
I did recently add Profile to the schema (with a 1:1 relationship
between User and Profile) and rebuild after that.
I tried removing and re-adding the entire plugin with no change in
behavior.
On Fri, Jun 18, 2010 at 12:57 AM, pghoratiu wrote:
> Check the session - the user id should be stored after sign-in.
> This can be checked in the web debug toolbar or directly the
> serialized session data.
> gabriel
> On Jun 18, 9:50 am, ashton wrote:
>> I'm not sure how I broke things, but I can no longer remain logged in
>> beyond one page load (tried clearing cache/using a different browser).
>> * When I hit a page, I get the login screen
>> * I login successfully
>> * The page that I was initially navigating to loads
>> * Then next time that I load a page, the signinSuccess form renders
>> again.
>> Thoughs?
>> logs:http://pastebin.com/0302jtfK
> --
> 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
>>>
>>> --
>>> 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
>>>
>>
>
--
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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
In order to test if the issue lay in the environment or in the code, I
set up a new vhost and checked everything out again at various
revisions. I can't seem to reproduce the issue at all on the newly
checked out vhost. So this issue has been resolved I think.
Thanks!
On Mon, Jun 21, 2010 at 12:37 PM, ashton honnecke wrote:
> It was working at one point. The issue seems to span all the apps that I
> have.
>
> Red Hat Enterprise Linux Server release 5.4 (Tikanga)
> PHP 5.2.10 (cli) (built: Aug 6 2009 06:05:50)
> symfony version 1.4.6-DEV
>
> ashton
>
> On Mon, Jun 21, 2010 at 12:14 PM, pghoratiu wrote:
>> I would say it's something wrong at the PHP configuration level, what
>> is your environment (OS, PHP, symfony version, ...?).
>>
>> gabriel
>>
>> On Jun 21, 8:51 pm, ashton honnecke wrote:
>>> This is what I have in configuration>user on the page load after sign
>>> in (from the webDebugToolbar):
>>>
>>> attributeHolder:
>>> sfGuardSecurityUser: { user_id: '173' }
>>>
>>> On the next pageload, it goes away (no sfGuardSecurityUser at all)
>>>
>>> I printed the session at the beginning of an action (right after
>>> login) and I got:
>>> [sfGuardSecurityUser] => Array
>>> (
>>> [user_id] => 173
>>> )
>>>
>>> then died before the action was over.
>>>
>>> Reloading after that got me back to the signin page.
>>>
>>> I did recently add Profile to the schema (with a 1:1 relationship
>>> between User and Profile) and rebuild after that.
>>>
>>> I tried removing and re-adding the entire plugin with no change in behavior.
>>>
>>>
>>>
>>> On Fri, Jun 18, 2010 at 12:57 AM, pghoratiu wrote:
>>> > Check the session - the user id should be stored after sign-in.
>>> > This can be checked in the web debug toolbar or directly the
>>> > serialized session data.
>>>
>>> > gabriel
>>>
>>> > On Jun 18, 9:50 am, ashton wrote:
>>> >> I'm not sure how I broke things, but I can no longer remain logged in
>>> >> beyond one page load (tried clearing cache/using a different browser).
>>>
>>> >> * When I hit a page, I get the login screen
>>> >> * I login successfully
>>> >> * The page that I was initially navigating to loads
>>> >> * Then next time that I load a page, the signinSuccess form renders
>>> >> again.
>>>
>>> >> Thoughs?
>>>
>>> >> logs:http://pastebin.com/0302jtfK
>>>
>>> > --
>>> > 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
>>
>> --
>> 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
>>
>
--
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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
It was working at one point. The issue seems to span all the apps that I have.
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
PHP 5.2.10 (cli) (built: Aug 6 2009 06:05:50)
symfony version 1.4.6-DEV
ashton
On Mon, Jun 21, 2010 at 12:14 PM, pghoratiu wrote:
> I would say it's something wrong at the PHP configuration level, what
> is your environment (OS, PHP, symfony version, ...?).
>
> gabriel
>
> On Jun 21, 8:51 pm, ashton honnecke wrote:
>> This is what I have in configuration>user on the page load after sign
>> in (from the webDebugToolbar):
>>
>> attributeHolder:
>> sfGuardSecurityUser: { user_id: '173' }
>>
>> On the next pageload, it goes away (no sfGuardSecurityUser at all)
>>
>> I printed the session at the beginning of an action (right after
>> login) and I got:
>> [sfGuardSecurityUser] => Array
>> (
>> [user_id] => 173
>> )
>>
>> then died before the action was over.
>>
>> Reloading after that got me back to the signin page.
>>
>> I did recently add Profile to the schema (with a 1:1 relationship
>> between User and Profile) and rebuild after that.
>>
>> I tried removing and re-adding the entire plugin with no change in behavior.
>>
>>
>>
>> On Fri, Jun 18, 2010 at 12:57 AM, pghoratiu wrote:
>> > Check the session - the user id should be stored after sign-in.
>> > This can be checked in the web debug toolbar or directly the
>> > serialized session data.
>>
>> > gabriel
>>
>> > On Jun 18, 9:50 am, ashton wrote:
>> >> I'm not sure how I broke things, but I can no longer remain logged in
>> >> beyond one page load (tried clearing cache/using a different browser).
>>
>> >> * When I hit a page, I get the login screen
>> >> * I login successfully
>> >> * The page that I was initially navigating to loads
>> >> * Then next time that I load a page, the signinSuccess form renders
>> >> again.
>>
>> >> Thoughs?
>>
>> >> logs:http://pastebin.com/0302jtfK
>>
>> > --
>> > 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
>
> --
> 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
>
--
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
Re: [symfony-users] Re: sfDoctrineGuardUser: Unable to stay signed in
This is what I have in configuration>user on the page load after sign
in (from the webDebugToolbar):
attributeHolder:
sfGuardSecurityUser: { user_id: '173' }
On the next pageload, it goes away (no sfGuardSecurityUser at all)
I printed the session at the beginning of an action (right after
login) and I got:
[sfGuardSecurityUser] => Array
(
[user_id] => 173
)
then died before the action was over.
Reloading after that got me back to the signin page.
I did recently add Profile to the schema (with a 1:1 relationship
between User and Profile) and rebuild after that.
I tried removing and re-adding the entire plugin with no change in behavior.
On Fri, Jun 18, 2010 at 12:57 AM, pghoratiu wrote:
> Check the session - the user id should be stored after sign-in.
> This can be checked in the web debug toolbar or directly the
> serialized session data.
>
> gabriel
>
>
> On Jun 18, 9:50 am, ashton wrote:
>> I'm not sure how I broke things, but I can no longer remain logged in
>> beyond one page load (tried clearing cache/using a different browser).
>>
>> * When I hit a page, I get the login screen
>> * I login successfully
>> * The page that I was initially navigating to loads
>> * Then next time that I load a page, the signinSuccess form renders
>> again.
>>
>> Thoughs?
>>
>> logs:http://pastebin.com/0302jtfK
>
> --
> 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
>
--
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
