[development] Anonymous to Authenticated User Cookies
nan_wich at bellsouth.net
Fri Sep 24 00:48:28 UTC 2010
Because if I have to show the code, then I would be disclosing something the
customer owns. I don't know if I can sanitize it enough and have it still be
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
From: Domenic Santangelo <domenics at gmail.com>
To: development at drupal.org
Sent: Thu, September 23, 2010 4:30:30 PM
Subject: Re: [development] Anonymous to Authenticated User Cookies
I too use the destination param. I have noticed that you must be careful not to
let it get lost if you're going to several intermediary pages.
Curious as to why you'd want to take code off-list, surely the solution would be
beneficial to the community?
On Sep 22, 2010, at 8:27 AM, nan wich wrote:
I do this simply by using the "destination" query parameter. If you need more
details on my code, we will have to take this off-list.
>Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
From: AustinCMS <chana at austincms.com>
>To: development at drupal.org
>Sent: Tue, September 21, 2010 8:12:28 PM
>Subject: [development] Anonymous to Authenticated User Cookies
>I have the following scenario:
>1. Anonymous user browses site.
>2. He clicks on link (on Screen A)
>3. He is informed he must login to proceed further (-> to Screen B)
>3. He clicks on "Register" which takes him to account creation (Screen C) and on
>form submit to Content Profile for profile creation (Screen D).
>Client then wants newly-created and authenticated user to be taken back to
>Screen B. In other words - where he was trying to head before
>being re-routed into creating an account and profile.
>There seems to be a lot of discussion and proposed "solutions" for this scenario
>- but none that actually really work. Login Destination module
>doesn't work because of Content Profile incompatibilities. AFAIK, LogonToboggan
>allows you to set a target after login - but not with the intermediate
>step of Profile creation. I can get a user back to the page where he logged in
>IF he is already an authenticated user and logging in from the User Login box.
>But so far, that is the
>only scenario that works even remotely closely.
>I'd like to understand better how cookies are managed in Drupal...especially
>going from an Anonymous session to an authenticated one under the scenario
>I'd appreciate info - or a link to a good resource, if possible...
>Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development