I recently moved my blog's URL from a /blog/ directory to the root domain. I went inside WP and made the changes to it that reflect this(ie WP URL). Everything is working fine. In order to send people who still had the old URL I installe the WP Plugin called Redirection. Again, when I put in the old URL I'm redirected to the new. Fine and dandy-BUT. When I look at the 404 log for it inside WP I have a massive list of 404 errors being reported but I have fire-tested every area of my blog. I had read that this plugin works out of the box and I don't even see where log 404 errors is checked. Does anybody know if there is a configuration problem with this or is there something more sinister involved? I will mention that I was put on to redirection because my awstats had also reported a great number of 404s(before or after the URL change I can't be sure)even though all pages at the new URL were being served fine before the URL change. I'm stumped and don't want to be loading up my server with useless reports.
The third column of your detailed 404 error report in AWStats shows you some of the referrers that contain the faulty links. This is often quite helpful. If there is nothing in the referrer column, the faulty link was possibly created by a misprogrammed web robot or by a user who entered a bad address. Jean-Luc
Jean-Luc, Looking at the third column of my awstats detailed 404 report shows me that of the almost 1400 total 404 errors, almost 1300 of them are referred by the /blog directory of my domain which is where the blog is physically located. Like I said, I have updated the info in WP to reflect that even though the URL hits the root domain that the actual files are in the /blog directory. Do you know what this means? Thanks for your help, Jeff
If you are sure that all URL's from the old /blog directory are redirected, it could be that what you see in AWStats are old events that were recorded during the short period when the blog was at its new address and the redirect was not yet done. Jean-Luc
Jean-Luc, That's what I'm trying to go through here. Awstats and the Redirection plugin are both still writing 404 errors to their respective logs but I can't get one 404 error by clicking anywhere on my blog. Is there some set-up for the plugin that needs to be tweaked or does it work out of the box? Jeff
I would visit several URL's from the third column and analyze what I find there. I don't know the plugin. Jean-Luc
Jean-Luc, I meant to add that from Awstats here is the breakdown of the two largest 404s in case this helps you: 770 /blog/wp-content/themes/cutline-3-column-split-11/custom.css referred by: http://senjomarketing.com/blog/ 489 /wp-content/plugins/blog-linkit/style.css The second error may be static because I don't have that plugin any more but the first one I just checked IS still writing errors.
I looked at the source code of your home page and it includes: <link rel="stylesheet" href="http://***.com/blog/wp-content/themes/cutline-3-column-split-11/custom.css" type="text/css" media="screen" /> Code (markup): This .css file doesn't exist. Jean-Luc
OK. I think we're getting somewhere here. Do you know what this file does? There is a custom.css not at: /cutline-3-column-split-11/custom.css Code (markup): but there is one here: /cutline-3-column-split-11/custom_css/custom.css Code (markup): If I copied it to where it expects will it work?
That's got it, Jean-Luc. That file is just a way to keep changes that you make to the theme. Looks like somebody didn't tell somebody they moved where the call should be made to. I moved it, clicked on a million places on my site and then went back to awstats and told it to update and the number did not increase. It used to call that error EVERY TIME anything was clicked on. Thanks very much for your help. Jeff