I started work on a module for 4.6 that would redirect a user once logged in to a pre-defined page. These pages would be different url paths based on the role of the logged in user.
This enables admins to go to the admin/settings straight away, content editors get redirected to the content workspace (provided by the nice workspace.module) etc.
The only issue I still had to overcome was what to do when a user was assigned multiple roles. Maybe weighting of the redirection urls/roles?
I think this functionality might fit nicely in to this module though.
Comments
Comment #1
jjeff commentedYes! That sounds like just the kind of thing that this module should handle.
But you know that with the 403 stuff enabled in Login Toboggan, if a non-logged-in user goes to http://www.example.com/admin (or whatever permissioned page), they will be presented with a login form and redirected to the page they requested on login (although there's currently a bug with this). I realize that this isn't quite the same, but it sort of solves the same problem.
If you want to roll up a patch to incorporate this functionality, I'd be happy to take a look. Let me know if you've got any questions or need any help.
-Jeff
Comment #2
Ogredude commentedI'd just like something that notifies the user that they have indeed logged in successfully.
Currently the only notice they get that the login was successful is no error. Which confuses many users. I've had over 10% of my active userbase already emailing me that they can't login... When indeed they are logging in just fine, they just don't realize it because there's no notification that it was successful.
Comment #3
aaron commentedI just made a patch that allows you to designate a page in the settings to redirect upon successful registration. If it's left blank, then the default behavior is followed instead (which is either to the front page, or to the user page if 'Initially login' is selected earlier).
Comment #4
aaron commentedMade a new patch for registration AND confirmation redirection. Not sure it's in line with what the original requester wanted anyway, so I made a new ticket at http://drupal.org/node/58084
Comment #5
aaron commentedoh, here, changed the status if anyone wants to take over this ticket
Comment #6
hunmonk commentedduplicate of http://drupal.org/node/58084