Interesting. I've been meaning to look at missing pages as my site grows, but I've mostly been looking for ways to detect missing pages when the links are generated.
Basically I was going to do something similar to your solution, but with the counter happening when a questionmarked link is created. On Jan 23, 9:02 pm, The Editor <[email protected]> wrote: > Wow, very creative solution. It would be a good idea to add a > solutions page with a note of the idea. > > Cheers, > Dan > > On Sun, Jan 23, 2011 at 11:21 AM, Kevin <[email protected]> wrote: > > This is intended as a helpful hint for those dealing with massive site moves > > ... > > > Over the weekend, I activated a large site that has been around for a long > > time. It has links pointed at it from many old sources going back years, > > many of which are still important, but hard to figure out what and where > > they are. It has been a very disorganized site for years, with tons of > > content in the root and other content squirreled away in obscure directory > > trees that mean nothing to anyone just looking at it. On top of that, there > > are copies of the same content in multiple files which were edits done by > > people maintaining the site with little website experience so tons of > > duplicate outdated material. A real mess... > > > On top of all that, the site has had a number of conversions from HTML to > > PHP and now to BW but with pretty much leaving what was there alone and > > making new versions of it... > > so I ended up moving a bunch of old stuff into some save dirs to see what > > would popup missing over time. I could then either move the content into a > > nonBW directory so it can be served as it is or reformat it into the system > > as a new page. A lot of this stuff is verbose going back to the late 90's. > > > So, I have a fairly long mod_rewrite list of old links to new... that works > > pretty well. > > > One problem was watching the logs looking for missing content... I needed > > something that I could view without having to watch the web logs... I also > > wanted to know what was getting hit more often as something that is more > > important that some stray hit over time. > > > So I modified the action.missing page and added in the section where the > > visitor has not write access the following which I made part of the error > > message: > > > [(info counter field={wv-requri} target=info.pagefail)] > > > This uses the same code context that I got from Dan for creating a simple > > page counter, but goes to the different page called info.pagefail. It picks > > up the URI from my webvisitors plugin and adds it to the list. Each missing > > hit has a counter at the end and each time is is hit, the counter increases > > making it easier to see what is getting hit more often. > > > Then by looking at that page, I can see which pages are missed and how often > > they are occurring. > > > Has been very useful... Now all I have to do is look at that page and I can > > quickly see any real missing content without having to parse through the log > > files. > > > -- > > You received this message because you are subscribed to the Google Groups > > "BoltWire" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/boltwire?hl=en. -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
