This is more of an FYI than anything else. Since I have upgraded to Drupal 6.11 Login Toboggin has quit working. Going through a number of issues I came across the following exchange about how Drupal core is now redirecting all users to their User Account page.

http://drupal.org/node/449386.

Any ideas on a possible fix or work around so that Login Toboggan will again handle the this redirection?

Comments

sagannotcarl’s picture

Version: 6.x-1.4 » 7.x-1.x-dev
Component: Miscellaneous » Code
Category: support » bug

I am also having this issue with the dev version, and this seems to me like this is a bug (even if it was drupal core's fault!).

If you watch the address bar of the browser you can see it flash the address to try the redirect that loggin toboggan used to do but then redirect again to the user page.

sagannotcarl’s picture

Title: Login Toboggan no longer functions after upgrade to 6.11 » Login Toboggan no longer performs redirects after upgrade to 6.11

The immediate issue I'm seeing is that loggin toboggan no longer redirects the user to after login.

Changing the title because it appears other parts of the module still work fine.

sagannotcarl’s picture

Status: Active » Postponed

It looks like the folks who broke it are trying to fix it: #292565: Regression: Can't set /user to 403 page (was: login destination is broken)

There is a patch here that fixed this issue for me. http://drupal.org/node/292565#comment-1553222

I'm marking this postponed because it looks like a core issue not a Login Toboggan issue.

EvanDonovan’s picture

Yes, this is definitely a core issue. The patch called regression.patch from #292565-87: Regression: Can't set /user to 403 page (was: login destination is broken) fixed it for me as well, but I had to apply it manually because of the differences between D6 & D7. Is a Drupal 6.12 perhaps in the offing? :)

marquardt’s picture

Looks like the patch is in 6.12: commit and applied patch.

hunmonk’s picture

Status: Postponed » Fixed

then we can put this issue to bed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.