Can't control where a user redirects to when they log in

[AaronCampbell]

The 'login' case in wp-login FIRST sets $redirect_to THEN runs wp_signon(). If we switch that, a plugin could hook into wp_signon's wp_login hook, and set $_REQUESTredirect_to? based on user type, capabilities, name, etc. It would be nice, and there is no downside that I see.

[ryan]

(In [7958]) Relocate signon to the top. Props AaronCampbell. fixes #7002

[ryan]

Milestone 2.5.2 deleted

[AaronCampbell]

[8069] reverted [7958] (accidentally I assume)

[ryan]

How about a login_redirect filter called after wp_login(). Altering the redirect before login can mess up the SSL detection stuff. See patch.

[AaronCampbell]

That's fine. I don't think we really need to pass $_REQUEST['redirect_to'] since the only difference would be https vs http right? I would be ok with this:

$redirect_to = apply_filters('login_redirect', $redirect_to, $user);

However, extra data doesn't hurt I suppose. Also, in the 2.6 branch if $_REQUEST['redirect_to'] is set then $_REQUEST['redirect_to'] and $redirect_to are identical.

[ryan]

(In [8736]) Add login_redirect filter. fixes #7002 for trunk

[ryan]

(In [8737]) Add login_redirect filter. fixes #7002 for 2.6

[ryan]

Went ahead and passed redirect_to from the request just in case someone needs to know if it was set or not.

[AaronCampbell]

Since it's a super-global, can't you just check that with $_REQUEST['redirect_to'] inside your function? Again, it doesn't matter to me if you add extra in there.

Thanks for handling it.