Sutherland Boswell

Version 2.4.1 is out now, please let me know if it works and I hope you’ll consider leaving a review!

I wish there was a better fix right now, but I think I could come up with a way to better solve the problem sometime down the road.

The value stored in the custom field is currently the URL of the full-sized video thumbnail, and that could be compared to the value of the full-size version of the featured image. If they don’t match, you’ll know the featured image isn’t for a video.

Here’s a quick PHP function (haven’t tested it) that might help if you want to go this route:

function test_if_post_thumbnail_is_video( $post_id = null ) {

	if ( $post_id == null ) $post_id = get_the_ID();

	if ( ( $thumbnail_id = get_post_thumbnail_id( $post_id ) ) != '' ) {
		if ( ( $video_thumbnail_url = get_post_meta( $post_id, VIDEO_THUMBNAILS_FIELD, true ) ) != '' ) {
			$thumbnail_src = wp_get_attachment_image_src( $thumbnail_id, 'full' );
			if ( $thumbnail_src[0] == $video_thumbnail_url ) {
				return true;
			} else {
				return false;
			}
		} else {
			return false;
		}
	} else {
		return false;
	}

}

This isn’t really the best solution, but my plan down the road is to create a field with the video thumbnail’s ID. Once that’s in place you’d just be able to compare the featured image ID to the video thumbnail ID to know if it’s for a video.

Unfortunately this isn’t an issue with Video Thumbnails so I don’t know if there’s anything I can do to fix the problem, but I can tell you that I know a photographer who has complained about the unpredictable way Facebook handles thumbnails on shared links.

It’s up to your SEO plugin to control the image size in the meta tags, so they’d be the most likely to help you be able to fix this!

Thanks!

As a note for anyone who gets a server error during a bulk scan, 2.4.1 will include a fix that shouldn’t get stuck in this situation.

I hadn’t considered the length of the file name being a problem, so I’ll include it in a fix I’m already working on.

I’d really like to figure out why it’s stopping on that particular post, but here’s how to skip to a specific post. Using chrome, type the following (you’ll have to actually type these, Chrome won’t allow you to paste it) into the address bar once you’ve started a scan.

javascript:x.toggleScan();

This pauses the scan so we can jump ahead without disrupting other stuff.

javascript:x.currentItem=145;

This jumps to the 146th post (the code starts counting at 0, so you’ll have to subtract 1 from whichever you want to skip to)

javascript:x.toggleScan();

This will tell the scan to resume.

Hopefully this works for you. Let me know if you have any questions, and like I said it’d be great if we could figure out what is going on with that specific post!

Oops! It looks like we were typing our posts at the same time. I was referring to the official code, but I can add support for the flash code in the next version.