Well if you're not getting multiple cookies and session data isn't being written to the database it's definitely a separate issue. That doesn't help nail down what the problem actually is, but at least it's good that one really is closed.

------------------------------------------------------------------------

        Michael C. Harris <mailto:[email protected]>
May 1, 2011 6:09 PM



No, just a single cookie at /mydomain.com/

--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
IRC: michaeltwofish #habari

------------------------------------------------------------------------

        Chris Meller <mailto:[email protected]>
May 1, 2011 1:15 PM


Are you still getting multiple cookies set in your browser? One for /auth and one for the main site at /?

------------------------------------------------------------------------

        Michael C. Harris <mailto:[email protected]>
May 1, 2011 1:14 AM



Perhaps this is a different issue that only I'm having. This is an
install I moved from its own domain to a sub-directory (still a single
installation).

act_login() correctly finds the user based on the submitted login
form, $_SESSION is correctly set to contain user_id, I get a PHPSESSID
cookie, but nothing is written to the sessions table. The redirect to
/admin therefore fails when User::identify() is called.

I have no idea why the session data isn't being written, nor really
any idea where to look next.

------------------------------------------------------------------------

        Chris Meller <mailto:[email protected]>
April 30, 2011 12:40 PM




Michael C. Harris wrote:
It would be good to have #1403 fixed. It's just a CSS tweak, but
beyond my ability.
It didn't make it into 0.7, if it gets fixed that's great, but I don't think it should hold up any other bugfixes either. If it were as simple as it seems I'd suspect someone would have jumped on it already. Since they haven't...
Also, I'm not sure that the auth issue is actually fixed. I have a 0.7
install patched with r5083 that exhibits the same behaviour, simply
reloading the login page, even though a user is returned.
Can you do some debugging then? Every other instance of people reporting that they were having this problem has been fixed, at least to my knowledge. I can't reproduce it so I'm at the mercy of people who have.
------------------------------------------------------------------------

        Michael C. Harris <mailto:[email protected]>
April 29, 2011 9:44 PM



It would be good to have #1403 fixed. It's just a CSS tweak, but
beyond my ability.

Also, I'm not sure that the auth issue is actually fixed. I have a 0.7
install patched with r5083 that exhibits the same behaviour, simply
reloading the login page, even though a user is returned.

https://trac.habariproject.org/habari/ticket/1403
http://trac.habariproject.org/habari/changeset/5083


--
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/habari-dev

<<inline: compose-unknown-contact.jpg>>

<<inline: postbox-contact.jpg>>

Reply via email to