Set up and manage an HTTP 301/302 Redirect from the URL of any post type to another URL, either on your site or externally.
In short, very easily. But before you read any further, take a look at Asking For WordPress Plugin Help And Support Without Tears before firing off a question. In order of preference, you can ask a question on the WordPress support forum; this is by far the best way so that other users can follow the conversation. You can ask me a question on Twitter; I'm @vicchi. Or you can drop me an email instead. I can't promise to answer your question but I do promise to answer and do my best to help.
There isn't one! All the settings and options for the plugin are in the Redirect This Post meta box that you'll find on the Edit Post page.
It's probably just what your browser is telling you. WP Avertere can set up the redirection for you and can check that your redirection URL is well formed. But what it can't do is actually check that the redirection URL points to a web page that actually exists. Now might be a good time to copy and paste your redirection URL into your browser and see if that shows a 404/Page Not Found error. If it does, then the page wasn't found. But if it was found, then you might have found a bug, so get in touch and let me know about it.
WordPress defines a set of acceptable URL protocols which are returned by the
wp_allowed_protocols API call. WP Avertere uses the
esc_url API call, which acts on this set of allowed protocols to determine which URLs are allowed and which are not. At the time of writing, the set is defined as
telnet. If your redirect URL is not for one of these allowed protocols the redirection will not be set up correctly. You can add to, or even limit, the list of allowed protocols via the
wp_avertere_protocols filter that the plugin provides. See the Filter Support And Usage section for more information on this.
Check that the redirection URL is well formed by clicking on the Check URL button on the Redirect This Post meta box. If the URL isn't well formed and you save the post anyway then the redirection will be ignored. Check that the URL actually exists in another browser window and behaves as you'd expect. If the redirect still doesn't work, now would be a good time to get in touch.
A permanent redirection means that the current and all future requests for the original URL should be directed to the new, redirected, URL. A temporary redirection means that the current request for the original URL should be directed to the new, redirected URL but subsequent requests can continue to use the original URL.
It's important to note that both permanent and temporary redirects can, and do, cease and the act of cancelling (or in other words, removing) a redirection, be it permanent or temporary, means that the behaviour for a URL reverts to how it was before any redirection was put in place. See the next FAQ for how to cancel a redirection.
In short, very easily. Edit the post that the redirection is set up on and then either delete the redirection URL or, even easier, click on the Clear Redirection URL button. Then just save the post and your redirection is gone.
There's nothing wrong with using the
REFRESH HTML meta tag to redirect to another URL but it's not as easy or efficient as using the plugin. Here's why. The
REFRESH meta tag lives in a page's header section. You not only need to inject this into the page (you could use the
wp_head action hook) but you need to wait for the entire page to load before your browser will take note of and act on the
REFRESH meta tag. WP Avertere hooks into the WordPress
template_redirect hook and issues an HTTP
Location header on your behalf; this means that the decision to redirect and the act of actually redirecting takes place before the page even loads, which is faster and more efficient.
This is a classic case of industry practice contradicting the standard (according to Wikipedia). The HTTP/1.0 standard defined HTTP 301 as Moved Permanently and HTTP 302 as Temporary Redirect. With the introduction of HTTP/1.1, HTTP 302 changed to Found and added HTTP 307 Temporary Redirect. But the majority of web services still use HTTP/1.1 302 as the original intent of the HTTP/1.0 meaning.
The current version of the plugin doesn't touch comments but after a redirect is set up they won't be visible due to the inherent nature of a redirect. The next version of the plugin will support the ability to copy comments from the source URL to the redirected target URL as long as that URL is on the same WordPress powered site.
WordPress and this plugin use the gettext tools to support internationalisation. The source file containing each string that needs to be translated ships with the plugin in
wp-avertere/lang/src/wp-biographia.po. See the I18n for WordPress Developers page for more information or get in touch for help and hand-holding.
Totally; this plugin is licensed under the GNU General Public License v2 (GPLV2). See http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt for the full license terms.
WP Avertere is named after the latin for "divert", meaning to turn aside from a path or course.
Requires: 3.4 or higher
Compatible up to: 3.4.2
Last Updated: 2012-11-8
Active Installs: 300+
Got something to say? Need help?