Persistent redirect_to For Login, Registration, and Lost Password

[sparkweb]

Currently, if redirect_to is passed in to the login screen and then a user clicks Register or Lost Password, the redirect_to gets lost. I think that the redirect_to should be persistent and honored whether the user logs in, registers or gets a lost password.

I've written a hacky filter to do this, but I think this ought to be included in the core. Here's what I did:

//Keep redirect_to in URL
add_filter('site_url', 'foxyshop_add_registration_redirect', 5);
function foxyshop_add_registration_redirect($path) {
	if ((strpos($path, "action=register") !== false || strpos($path, "action=lostpassword") !== false) && isset($_REQUEST['redirect_to'])) return $path . '&redirect_to='.urlencode($_REQUEST['redirect_to']);
	if (substr($path, strlen($path)-12) == "wp-login.php" && isset($_REQUEST['redirect_to'])) return $path . '?redirect_to='.urlencode($_REQUEST['redirect_to']);
	return $path;
}

(I know 3.3 is in freeze now, but there wasn't another version option)

[kawauso]

The Version is for the earliest version affected by the issue, rather than the one you want it fixed in.

[SergeyBiryukov]

#23523 was marked as a duplicate.

[onokazu]

Maybe the following line in wp-login.php (line 709 in WP 3.5.1)

<a href="<?php echo esc_url( site_url( 'wp-login.php?action=register', 'login' ) ); ?>"><?php _e( 'Register' ); ?></a> |

should be

<a href="<?php echo esc_url( site_url( 'wp-login.php?action=register&' . urlencode($redirect_to), 'login' ) ); ?>"><?php _e( 'Register' ); ?></a> |

[chriscct7]

Good First Bug: Attempt to replicate

[ross_ritchey]

Add redirect handling to wp_registration_url

[ross_ritchey]

Just added a partial patch for this.

Looking at things it seems that the Forgot Password link handling already has the logic for passing the redirect through -> though need to test and confirm that this is working as intended.

I added handling to wp_registration_url() to allow for passing a redirect url in (the same way all of the other login-related url functions are working).

What is still needed is to go through the remaining core pieces of the login process and update things to properly pass the redirect through to this function.