Great progress so far, but…

although I chose to completely ignore links with HTTP status 301,302 – I still get those added to the log. Am I doing something wrong?
I entered comma seperated codes like so: 301,302

What gives?

Anyway, don’t worry.If those posts are visited by someone (including you/or a search engine spider), all the bad/broken links will get logged again.

But if they have already been visited, then you will have to wait until the time interval that you set via the first option.On the expiry of such time interval, if someone visits the same post, the bad/broken links will be logged.Also note that if you want it to be logged asap then make this time interval as 1 day(not earlier than that) temporarily.You can change it back to any other interval greater than 1.note that the default is 10 days.

I think that I’ve answered my own question by reading your doco. Have set the time interval to 1 day and suspect that broken links will once again show up in about 24 hours.

I’m curious as to how your plugin is able to remember how long it’s been (in days) since checking even after uninstalling/re-installing the plugin.

Please enlighten us.

Robert

I cleared out the Broken Links using mysql before fixing those broken links. I then re-installed your plugin but now broken links are not showing.

Any ideas?

Robert

Yes that one is feasible.Have noted it down.

Link to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html somewhere so users can look up what some of the more unusual return codes mean – I got a 503 today!

Ok will do it

think all the return codes indicating temporary problems should NOT be hidden by default. As well as 302 that means 307, 408, 503, and 504 according to my reading of the above list. I might have missed some of course.

You anyway have an option to specify the links, with specific http status codes, that you don’t want to hide

’d like to be able to ignore/hide errors by URL and by protocol as well

Will explore it

You could even do a delete by using SQL (via phpmyadmin).But it is up to you to make sure that you have corrected the errors, before executing a Delete SQL statement.

There is no hard and fast rule and it is your choice

More feature requests (yes, I’m very greedy!):
Make the links on the management page clickable so it’s easy to find out if an error has resolved itself. At the moment the only way is to edit the post, highlight the link, and open it in a new tab. That’s slow!
Link to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html somewhere so users can look up what some of the more unusual return codes mean – I got a 503 today!
I think all the return codes indicating temporary problems should NOT be hidden by default. As well as 302 that means 307, 408, 503, and 504 according to my reading of the above list. I might have missed some of course.
I’d like to be able to ignore/hide errors by URL and by protocol as well as by return code. All “mailto:” links return 302s, for example, and links to certain pages always return 302s also. I don’t want to hide *all* 302s but I’d like to be able to hide say “apple.com/*” and “mailto:*” and “technorati.com/*” from the logs.

Keep up the great work – it’s very much appreciated!

What is the best and quickest way to clear the plugins log? Can I just go into phpmyadmin and clear the tables? Or do you have a recommended procedure?

Thanks.

R

Thanks.

R