Max K

<p>Easy to set-up Login, Logout manager (and soon for Registration)</p>


Login, Logout and Registration Redirects manager

Easy to set-up Login, Logout and Registration manager

Scott Kingsley Clark

<p><em>Important:</em> It is not recommended you leave debugging enabled when you’re done, the debug information exposes file paths of files as well as PHP arguments passed into functions from the PHP <code>debug_backtrace()</code> which may contain sensitive information.</p>
<p>This is useful for those times when you have a lot of plugins / theme functions interacting that cause an unknown redirect. This tool helps you figure out what is redirecting and where it’s redirecting at in the code.</p>
<p>This plugin outputs information about each <code>wp_redirect()</code> and <code>wp_safe_redirect()</code> call done on the front and in the admin area of a site.</p>
<h4>Usage: Enabling with the setting</h4>
<p>You can enable redirect debugging by going to <code>Settings > Debug wp_redirect()</code> on your site or in your network settings (if network activated). You have the option to enable debugging for frontend requests and/or admin dashboard requests. You also have the ability to only show debugging if the person is logged in or is an admin.</p>
<p>If you encounter problems with this plugin blocking redirects you need for logging in or being able to disable the redirect, simply rename the plugin or define this in your wp-config.php file: <code>define( 'DEBUG_WP_REDIRECT', false );</code></p>
<h4>Usage: Enabling through wp-config.php</h4>
<p>You can define constants in your wp-config.php file to enable redirect handling for frontend / admin dashboard requests. Constants override any options set in the admin settings page.</p>
<ul>
<li>To enable redirect debugging on the frontend of a site: <code>define( 'DEBUG_WP_REDIRECT', true );</code></li>
<li>To enable redirect debugging in the admin dashboard of a site: <code>define( 'DEBUG_WP_REDIRECT_ADMIN', true );</code></li>
<li>To only show redirect debugging to logged-in admins of a site: <code>define( 'DEBUG_WP_REDIRECT_LOGGED_IN_ADMIN', true );</code></li>
<li>To only show redirect debugging to logged-in users of a site: <code>define( 'DEBUG_WP_REDIRECT_LOGGED_IN', true );</code></li>
<li>To only show redirect debugging to logged-in user ID(s) of a site: <code>define( 'DEBUG_WP_REDIRECT_LOGGED_IN_USER_ID', true );</code></li>
</ul>
<h4>Usage: Enabling debugging through PHP in your own code</h4>
<p>You can enable/disable debugging when you have your own code you want to start/stop debugging after a certain point.</p>
<p>These functions will start/stop debugging the redirects whether it’s on a frontend or admin dashboard request.</p>
<ul>
<li>Enable debugging: <code>debug_wp_redirect_enable()</code></li>
<li>Disable debugging: <code>debug_wp_redirect_disable()</code></li>
</ul>
<h4>Usage: As an mu-plugin</h4>
<p>Take the debug-wp-redirect.php file and add it to your mu-plugin folder in a location like: <code>/wp-content/mu-plugins/debug-wp-redirect.php</code></p>
<p>You won’t need any other files. The admin settings page will not show up so you will need to use mu-plugin mode specifically with the constants for wp-config.php as documented above.</p>
<h4>Contribute to make this plugin better</h4>
<p>You can help to make this plugin better through <a href="https://github.com/sc0ttkclark/debug-wp-redirect" rel="nofollow ugc">GitHub</a> or <a href="https://github.com/sponsors/sc0ttkclark" rel="nofollow ugc">sponsor my time</a>.</p>


Debug wp_redirect()

Worked really good. I had one issue where an object was echoed out like a string. A quick edit fixed that, and not it works perfectly. 5/5 if not for that error (on line 63).



Saved the day!

What the.. Where'd that redirect come from? This plugin helps to uncover redirects as they happen.

Login, Logout and Registration Redirects manager vs Debug wp_redirect()