Getting started

Once installed, the plugin can assist you in tracking down the cause of the triggered redirect. All you need to do is open the URL that initiates the redirection.

If the redirect is initiated via the WordPress redirect function (which is the case for the majority of plugins and themes), you will see debug data.

The Debug Data #

Now, you have the option to pause the redirect if you would like to examine the displayed information more closely. Unless you do this, the redirect will proceed after 10 seconds.

Interpreting the Data #

Whenever wp_redirect() is used, there are certain WordPress inbuilt functions that are always used, such as do_action or apply_filters. These functions can be disregarded.

The data is shown in the order of the function called last, thus your search for a plugin, theme, or code that calls redirects should begin at the end of the table.

Deactivating the Plugin #

The plugin does not have to be activated at all time. You can enable it just for the debugging process, after which you can either disable in the settings the debug info (displayed in the front-end) or deactivate the plug-in entirely.

Plugin Settings #

There are a few settings available in the plugin under “Tools –> WP Core Monitor”. The first one ("Debug wp_redirect()") lets you deactivate the function that backtraces redirection.

You can use the second one ("Choose a User Role") to grant access to the debug data so a WordPress expert can assist you in debugging and analyzing the redirect.

Security #

Please keep in mind that if you pick the last option ("All visitors and users") under “Choose a User Role”, the debug data will be displayed for everyone who visits any URL that initiates the redirect.

To avoid accidentally disclosing information about the plugins used, it is recommended to use the debug data display for brief periods of time if you decide to make it public.