Check the referring URL and the user agent. Usually these are caused by robots that found a link to the draft or happened to be scanning your site while you were previewing the posts. I wouldn’t worry about it unless it was an actual user that was getting the error.
I am answering my own question so others can find it in the future. defining NOBLOGREDIRECT in wp-config.php to point to the url of your choice will correct this problem. Sample: define(‘NOBLOGREDIRECT’, ‘http://www.my-domain.com’);
Posting as an answer from the @OneTrickPony comment above: Verify that mod_rewrite is enabled on your server. Assuming that mod_rewrite is enabled, ensure that the root WordPress install directory is WordPress-writeable, or that, if it exists, the .htaccess file in the root WordPress install directory is WordPress-writeable. (See file permission scheme for WordPress, and Hardening … Read more
If I am not mistaken in PHP Array commonly comes up when array variable is wrongfully used where string is expected. But from this information I have trouble suggesting where exactly that can go wrong.
When you use W3TC with Nginx, it wants to write a nginx.conf file into your server root, do you have that file in place, writable by the nginx user? Also, did you add an include directive in your primary nginx config to pull that file in? For example, in my /etc/nginx/sites-enabled/dougal.gunters.org config file, I’ve got … Read more
Sometimes hosting providers will implement mod_security (and not mention anything). Or else, mod_security was already on but a recent installation of a plugin or theme may have exposed this new problem for you. You can try these four things… Add the following to your .htaccess file (add to .htaccess, don’t replace the other stuff already … Read more
If you’ve got access to the database (via phpMyAdmin or the like) you can change those two values in the wp_options table. Look for siteurl and home in the option_name column.
The issue wasn’t caused by WordPress, I found out that my httpd.conf file had a default setting of AllowOverride None which was causing my rewrite rules in my .htaccess file not to work. Probably something I should have checked in the first place, but easy to overlook as well.
Set the WordPress index.php as error handler in your .htaccess (if you are using Apache): ErrorDocument 404 /wp/index.php Make sure the path matches the path to the WordPress directory.
Problem fixed YAY. I had to edit the permalinks on the three main pages that were generating the server 404s. In other words, I changed about to about-client-name, changed services to services-page, and changed contact to contact-us. The 404 behavior went away. This also fixed the subordinate services pages and the subordinate about page.