Donald Gilbert

Facebook has updated the markup for the fanbox again. I’ll work on a fix asap, as I need it for my site as well.

OK, very strange indeed. I’ll take a look. There are some outstanding issues with some users not even downloading remote images, this may be linked. I might have to bite the bullet and refactor the plugin to utilize WP_Http sooner rather than later.

Sounds like it. Let me do some testing. Can you tell me what browser, WP version, and PHP version you are using for your website? If you want, you can email them to me at don at dongilbert dot net with the info, or post it here.

It’s not a major issue. What I can’t figure out is why it is erroring. The file it’s trying to load does exist, it’s just the getaddrinfo function is failing, so it doesn’t know where to route the remote request. It may be an issue with your hosting environment.

I’ll look into possible solutions when I get a chance.

You can specify image size via CSS, as all the thumbnail sizes are the same. However, if you’d like to specify image sizes on the actual <img> tag itself, then you would need to make modifications to the plugin code.

That is weird, it shouldn’t be trying to add the CSS file when inline is selected, what version are you using?

Which version of the plugin are you using?

The reason you get the issue each time the cache is cleared is that file_get_contents is only called when generating the local cached version, so you would only see it when a new cache is being generated.

It’s a limit from facebook, it doesn’t always return the numbers you’re asking for. I don’t know how to force it.

Marking as resolved due to no reply.

this has been fixed in the latest version, 2.5. Facebook updated the HTML markup generated by their fanbox, so my parser wasn’t working anymore.

The reason it hasn’t been working is Facebook updated the HTML markup that is produced by their fanbox generator. This has been addressed in the latest version, and it will be live shortly. Version number will be 2.5.

You could use CSS to set a hard width on the grid item, and then set overflow to hidden. I’ll work on a fix for the next release.

It’s not an intentional attack. After we released this plugin, our site became targeted for spam attacks for some reason.

We have resolved this now though.

Sorry about that – I’m not sure what the issue is as I’m not experiencing it.

What is your server/website configuration. PHP Version, WP Version, etc.

Well, this plugin removes all the extra css and js that is required to load the FB Like Box, and then caches that so it’s super fast. Removing the *like* feature was a consequence of this.

So many people are requesting this feature, I think I have to include it in the next update. I’ll see what I can do.

To answer your question, yes – using this in tandem with the FB Like Box should speed up the site since it doesn’t need to load the user images, but not by much since you still loads in the JS files.