Redirect after login cutting off url after '?' character

I have a similar problem when a user resets password. Link redirects to /user without any url parameters.

Please let me know if you find a solution.

Thanks,
Jason

Bumping this. I have pages that receive an essential URL parameter to identify an underlying database record, so a URL might look like http://www.example.com/mypage?group_id=10 for example. Using Present login form on access denied (403) works except that the user ends up on http://www.example.com/mypage without the group_id parameter. Inspecting the action on the HTML form element shows it is correct including the group_id parameter so I can't see why this isn't working.

Note that if I disable Logintoboggan and hack a standard login form to change the action attribute to match, everything works nicely. So I think this is a Logintoboggan specific issue.

Hi,

I am also facing the same issue, I have the redirect url with ?id=cwp attribute the 'id=cwp' attribute, is cut off from the url. Had anyone found the fix.

I'm experiencing this issue as well... I'm sending users a URL via email with a specific value attached. If they are logged in when they visit the site it works perfectly. If they aren't, they hit the login toboggan login page (with the value intact), but logging in redirects them to the right url sans query parameters.... VERY annoying. I'm not sure why this is happening.

Steps to reproduce:

1. Create new site on simplytest.me with Login Toboggan 7.x-1.x.
2. Enable "Present login form on access denied (403)" from {baseurl}/admin/config/system/logintoboggan.
3. Log out.
4. Visit any page behind access control and add something to the query. I use {baseurl}/admin/config/system/logintoboggan?test=me.
5. Log in.

Expected Result:

Logged in and viewing the page WITH the query.
{baseurl}/admin/config/system/logintoboggan?test=me

Observed Result:

Logged in and viewing the page WITHOUT the query.
{baseurl}/admin/config/system/logintoboggan

Workaround:

Although I did find one workaround, it isn't pretty. You can url encode the path you need including the query, then add that as a destination query.
Ex:
{baseurl}/admin/config/system/logintoboggan?test=me&destination=admin%2Fconfig%2Fsystem%2Flogintoboggan%3Ftest%3Dme

The problem with this workaround is that a logged in user will not be redirected to the destination after submitting anything on that page... It makes for a confusing experience for logged in users. If that isn't an issue for your use case, then go ahead and give it a try.

I'm not really sure what to make of the response in the related issue I just added. It seems to me that code should be ensuring that the query string is maintained... And yet, that's apparently why it isn't? drupal_get_destination() appears to specifically preserve the query parameters so they aren't lost... I'm at a complete loss as to why the query strings vanish as soon as I click login... It's even in the form action on the rendered html form...

For those who suffer from this issue, here is the patch to solve this.

In short, drupal core set destination on each not found / access denied before logintoboggan and without query parameter except q.
The patch is to rebuild destination before calling form.

Patch #9 will do the job, but I think it's probably better do to this as a from submit function. That makes it easier for site builders to see how it's done and potentially override with their own submit function if they need an alternative redirect behaviour. I've marked this for review although I appreciate the issue is old now :-(

Testing showed up a bug in the patch at #10. It screwed up destinations containing a fragment, such as user/login?destination=node/1#comment-form. So, here's a re-rolled version that handles both fragments and query parameters.