do_action( ‘template_redirect’ )

User Contributed Notes

1. Skip to note 4 content

   Rami Yushuvaev 5 years ago

   You must log in to vote on the helpfulness of this noteVote results for this note: 8You must log in to vote on the helpfulness of this note

   Redirect existing pages to other pages:

   function custom_redirects() {
   
   	if ( is_front_page() ) {
   		wp_redirect( home_url( '/dashboard/' ) );
   		die;
   	}
   
   	if ( is_page('contact') ) {
   		wp_redirect( home_url( '/new-contact/' ) );
   		die;
   	}
   
   }
   add_action( 'template_redirect', 'custom_redirects' );
2. Skip to note 5 content

   Steven Lin 4 years ago

   You must log in to vote on the helpfulness of this noteVote results for this note: 0You must log in to vote on the helpfulness of this note

   Example migrated from Codex:

   Following example will redirect all non-authenticated users to a custom ‘signup’ page when trying to visit the ‘goodies’ page.

   function my_page_template_redirect() {
       if ( is_page( 'goodies' ) && ! is_user_logged_in() ) {
           wp_redirect( home_url( '/signup/' ) );
           exit();
       }
   }
   add_action( 'template_redirect', 'my_page_template_redirect' );

   Don’t forget to call exit() ( or die() ) after a wp_redirect() .
3. Skip to note 6 content

   Andrew Lima 7 years ago

   You must log in to vote on the helpfulness of this noteVote results for this note: -3You must log in to vote on the helpfulness of this note

   If you need to remove a template_redirect from within a custom plugin, simply using remove_action( 'template_redirect', 'function_to_remove' ); won’t cut it.

   As a workaround, what you can do is create a function to hook into template_redirect action earlier and then remove the redirect you are trying to remove.

   // remove a template redirect from within a custom plugin.
   add_action( 'template_redirect', 'remove_my_action', 5 );
   function remove_my_action(){
       remove_action('template_redirect', 'function_to_remove', 10 );
   }

   • Is that correct? You cannot remove callback functions before they’ve been registered. In this example you’re calling your remove_my_action() function at a higher priority than when the function_to_remove() function is registered. It’s recommended to hook your remove_my_action() function to an action hook that fires after template_redirect. For example, you can hook it to the after_setup_theme action.

     Salman Ravoof 4 years ago
   • @salmanravoof The callback function in Andrew’s example has been registered on the hook already, but it hasn’t fired yet. In the above example, here’s the list of events: 1) wporg_plugin_init() fires on init action, registering the template_redirect callback (at default priority 10), 2) wporg_theme_template_redirect() fires on template_redirect with priority 5, removing the registered callback (set to fire on priority 10), and 3) action template_redirect with priority 10 is running, but because the callback has been removed, it doesn’t run. Because the plugin’s callback is set to run at priority 10 during the init action, by hooking into template_redirect at an earlier priority, the callback has been registered, and has not yet fired, so it can be removed. Hope that’s helpful.

     crstauf 4 years ago