WordPress.org

1. mwaterous
   Member
   Posted 10 months ago #

   I have configured Broken Link Checker to crawl links in a custom field, for well over 30 thousand records, a feat that is by no means fast regardless of how it's configured.

   The problem is that it's pulling all the custom field links and appending them to the web site url (ie the value of custom field "url" is "http://www.othersite.com/" and is subsequently being turned into http://thesite.com/www.othersite.com/" which is returning a 404 as expected). So somewhere the plugin is actually removing the http:// prefix and prepending the url with the blog url prior to checking it.

   I'm going to go hunt around in the code, but I've got three projects on the go today and am hoping somebody else might toss me a cookie on this one. :)

2. mwaterous
   Member
   Posted 10 months ago #

   I discovered the problem was with urls that didn't have the protocol. http://site.com/ would work where site.com would wind up with the blog url prepended and return the expected 404. The fix was a quick SQL query to add the protocol.

   This is a pretty impressive plugin, to say the least. I think the next version could benefit from being able to recognize custom field urls without the protocol and check them appropriately!

Reply

You must log in to post.