Redirecting is possible, but if this will work depends where are your users folders placed. If user folder is placed in e.g content structure and it is availalbe for currently logged in user, then use main_node.node_id or main_node.url_alias and redirect after login using RedirectURI field.
I'm not sure you will be able to do this using RedirectURI. You would need to put the hidden RedirectURI form element into the login form. As you cannot know who the user will be <b>before</b> they login it is not possible to redirect them to a page specific to that user using this method.
It does appear that you will be able to do what you require in 3.8. Seehttp://pubsvn.ez.no/nextgen/trunk/doc/features/3.8/advanced_redirection_after_user_login.txt
Thx Bruce, this is exactly what I tought it will be the problem. I just tought that eZ already has a mechanisim for doing such thing. It seems I'll have to wait... :)
--
Nothing is impossible. Not if you can imagine it!
While we're waiting for the 3.8 version I came up with a quick fix for this:
Redirect user after login to a node with special template override in which I fetch the current user, and call the template that displays it's homepage. Should work just fine.
--
Nothing is impossible. Not if you can imagine it!
On the redirect after login in 3.8, is there a reason that hooks for workflow triggers were not added to the user module to achieve this?
It would be a much more flexible solution, allowing for any type of redirection code to be added, and many other opportunities for login restrictions (logging of logins, time based restrictions, ip based restrictions, etc)