I’m not sure I understand your setup, but here are few ideas: A) Display a login link with the redirect_to parameter set: You could add the following to your custom template pages: if( ! is_user_logged_in() ) { printf( ‘<a href=”https://wordpress.stackexchange.com/questions/169704/%s”>%s</a>’, wp_login_url( get_permalink() ), __( ‘You need to login to view this page!’ ) ); } … Read more
function generate_404_somehow() { global $wp_query; $wp_query->is_404 = true; } add_action(‘wp’,’generate_404_somehow’); Of course, that will send all of you page to the 404 template. I don’t know what the conditions are that this should fire or not fire. Or to be more cautious (see comments) … function generate_404_somehow() { global $wp_query; $wp_query->set_404(); } add_action(‘wp’,’generate_404_somehow’);
See the source. It has some additional logic for IIS servers, as well as some hooks. It is also pluggable function, so it might be redefined. Overall it’s just more flexible and gives other developers more options to work with your code, unavailable if you just hardcode things.
This is normal, it is because redirect_canonical(), which makes sure you are always at a “canonical” URL (conforming to your permalink structure), executes redirect_guess_404_permalink() to make a best guess at a post when the URL is incomplete. If you want to prevent this, I think the best way is to hook into the redirect_canonical filter, … Read more
Don’t remove the action but add your own before it. If you remove the action you will never get the message saying it was upgraded successfully. Here you can provide your own info on what to do next. function tp_dont_redirect_to_about_wordpress( $new_version ) { global $wp_version, $pagenow, $action; if ( version_compare( $wp_version, ‘3.4-RC1’, ‘>=’ ) ) … Read more
You can filter the login_redirect function like so, adapt according to your needs. add_filter(‘login_redirect’, ‘redirect_previous_page’, 10, 1); function redirect_previous_page( $redirect_to ){ global $user; $request = $_SERVER[“HTTP_REFERER”]; if ( in_array( $user->roles[0], array( ‘administrator’) ) ) { return admin_url(); } elseif ( in_array( $user->roles[0], array( ‘subscriber’) ) ) { return $request; } return $redirect_to; } Update 1: … Read more
Well, at my situation… I downloaded the company website from production to localhost because I was needed to prepare a development environment for some developers. The production is using https:// and at localhost http://, and when I ran it the first time on localhost, it always redirected me to the https://. And, I have managed … Read more
The correct way to do this is using the template_redirect hook by adding a function to your functions.php: function redirect_to_home() { if(!is_admin() && is_page(‘2’)) { wp_redirect(home_url()); exit(); } } add_action(‘template_redirect’, ‘redirect_to_home’);
It sounds like the site & home URLs are not set correctly. You can set these in wp-admin from the Settings screen, although it sounds like you may not be able to get in there right now, so a workaround is to do the following: Edit your wp-config.php file Search to see if WP_HOME or … Read more
Updated Answer (2020-10-29): The solution has changed with WordPress 5.5. Keeping the old answer for reference below. Short version: Get my pluign from here: https://wordpress.org/plugins/disable-url-autocorrect-guessing/ Long Version: With WordPress 5.5, you can control more precisely if/how the guessing should work. Refer to https://make.wordpress.org/core/2020/06/26/wordpress-5-5-better-fine-grained-control-of-redirect_guess_404_permalink/ for more information. To completely disable guessing, use this code: add_filter( ‘do_redirect_guess_404_permalink’, … Read more