3
1K
38K
0
28 November 2017
16 May 2012
Based on 3 on WordPress.org
Scenario
Sites with high volume of content may have some moved, deleted or badly referenced content. This situation will cause a 404 http error.
Problem
In high performance sites the previously described situation can be a resource problem. It is not necessary that we load completely the site to show a 404 error page.
Solution
Loading a plain HTML page will result easier for our web server than loading a complete CMS instance.
/wp-content/plugins/
directory.
The plugin hooks the normal WordPress workflow in order to determine if the request is processing will cause a 404 HTTP error. Then it makes a redirection to the URL defined in the plugin settings.
/wp-content/plugins/
directory.