Image Status Checker / Dead Image Finder

Note this hack works with vb3.6


What does this do?
It scans all your posts, extracts all the img tags, and scans each of the images to see if they're still valid.


Why?
I had a look at all the images on my site and was alarmed at how many were now gone - deleted from photobucket accounts etc. Since the only way you can check the images on your board is to manually read every post, I decided to come up with a better way... and this is it.


How does it work?
The first part: In the AdminCP, under Maintenance and Update Counters... right at the bottom is this hack. It works by looking up every img tag, then requesting the image, and reading the http status code. So code 200 means 'image ok', 404/410 means 'image gone' etc. That then gets stored in a database table. A server has 15 seconds to reply to the request or the status is labelled as "Unknown"
The second part: The browsing element, imagestatuscheck.php (original filename huh!). This allows you to browse all the images found in the last scan using some powerful filtering (statuses to display, search, order by).


Hack features

• General
• Fully phrased.
• Templates are grouped. Who's online handled.
• Part 1 - Admin
• Reads the post table, scans all the [img] tags on demand and records the actual http status code returned.
• If it gets stuck during the scan, you can restart the section it's currently doing.
• If an image appears in more than one post, it's only checked once.
• Start from, per page and timeout options for scanning.
• Part 2 - Browser
• Status codes are put into one of three descriptions for simplicity: Working, Dead, Unknown. Unknown is if the server didn't respond or similar - on the basis that a temporary timeout doesn't necessarily mean the image has gone.
• In the browser, image urls are force wrapped. Unless people post using all caps, you have a low screen resolution, or the font size is big, the table should never stretch.
• Filtering allows you to show just the working/dead/unknown images, and there's a search facility for a variety of fields.
• Convenient link to edit the post (if a dead link is found). This works by can_moderate - edit links only appear for people who own the post, or can moderate the forum it's in.
• Works by canview - if someone can't view a particular forum (e.g. staff forum) normally, they can't view the images within it.
• Uses css for common stuff to reduce the size of the outputted pages.

Bad Things
It's far from a perfect hack, there are many things to do. Please be aware that I won't be doing them, but if anyone else wants a crack, feel free!

• Only supports http://, not https://
• Can only handle replies like: HTTP 1.x 200 as the first line.
• Only supports [img] tags. If you have HTML turned on in any forums it won't see <img src=> images.
• Biggie: There's no way to update a single post or image without a full re-scan. That means if someone edits their post to update or remove a dead link, it will not change on the browser until a full re-scan is done. I did play with various update methods but most are flawed in one way or another. A planned feature will be to update the table dynamically whenever a post is made, edited or deleted, and on demand using a link.
• No cron job.
• No session variables. (People without cookies will be logged out a lot).

Footnotes
Originally I planned to throw something together quickly just for me to use but it turned into a "I may as well make a nice interface... oh and I may as well put some filtering controls in and I ..."


A [url] link checker can be found here


Installation
Upload imagestatuscheck.php to your vB directory. Install the product, set overwrite to yes.


Customizing

• By default it's set to only allow moderators, super-moderators and administrators to view the browser. This can be changed with the setting in AdminCP > vB Options.
• The phrases all start with ics_ if you want to change them.
• You can add a link to imagestatuschecker.php on the navbar (or anywhere) if you want your members to be able to view it.

Screenies
Shot 1 is AdminCP during scan
Shot 2 is a typical Browser section output
Shot 3 is no results output


Changelog
See attached file for specific changes.
1.00 - 16th August 06
1.01 - 17th August 06
1.02 - 27th December 06

[RedHacker]

This work in 3.8.1....?

[Kolbi]

Is the possibility given that someone can update it to get it workable with vB4?

[TundraSoul]

Originally Posted by Kolbi

Is the possibility given that someone can update it to get it workable with vB4?

Agreed this so needs to be updated for vB4!