Donald Gilbert

I went ahead and “liked” your page again, so it shows the 8 on your site. ?? (yay – I CAN do something!)

So, I looked into it, and it’s actually a problem with facebook.

If you look at your regular iframe fanbox url ( https://www.facebook.com/plugins/fan.php?connections=8&id=170388796337902&locale=en_US&stream=false&width=255 ) you’ll see what I mean.

Notice how the URL says to show 8 and the fanbox only shows 7? Apparently, there’s a limit on facebook’s side that causes this. Sorry it wasn’t something I did, then there’s the potential that I could fix it. But not this. ??

Weird…

I went ahead and “liked” your page, and now I’m in there, rounding out the 8. Interesting. Being that I get the original iframe via cURL, and then just regex over it to get the info out that I need, there’s really only two options:

1. Facebook limits the number of fans that can be shown in a fanbox for pages that have less than X. (somewhat unlikely)

2. A problem with my regex that reveals itself when used on a fan page that has less than X. (highly likely)

Let me look into it.

@peteratomic – glad you like it. That was one of the problems I was facing and one of the reasons I created it.

Your issue could be the size of your div container for the fanbox being set too small. Check the HTML and count the actual number of connections it’s showing. (I use https://www.getfirebug.com and Firefox for that sort of stuff.)

What’s your site? I could take a look when I get a chance.

oops – you’ll also have to change a couple other lines, adding double quotes around $vars['url'] in two places. Probably better to just wait unless your comfortable with doing that.

Well, that’s embarrassing. ??

Apparently, I didn’t account for fan pages that didn’t have /pages/ in the url.

Your page, being https://www.facebook.com/hungarband, didn’t match my regex looking for facebook.com/pages/*/*.

I’ve updated it, and it should now work out for you. If you update to 1.1 when it comes out, it’ll work fine.

If you don’t want to wait until the release is approved, you can fix the regex yourself. In the _parseHTML function, change
$urlExp = '/"http:\/\/www.facebook.com\/pages\/(.*?)\/(.*?)"/';
to
$urlExp = '/<div class="connect_top clearfix"><a href="(.*?)" target="_blank">/';

Also change $this->_url = $url[0]; to $this->_url = $url[1];

Sorry about that. I’ll get the fix pushed live asap.

Thanks Aaron! Glad you like it. FYI – I added a donate link just for you!

Sorry, but with the upcoming release of WP 3.1 with the included Admin Bar, I’m going to have to rethink the development of this plugin. I’ll see what’s missing from the final 3.1 admin bar, and do what I can to make it more like the WordPress.com bar. The most notable thing missing was the login, and I don’t think that that is actually going to be implemented in 3.1.

I vote for better/easier media handling. CSS3 is always nice. Dropping Hello Dolly is a great idea to lighten the load. Akismet is up in the air for me. +1 for WordPressLite.

oops – looks like you may need to put an ‘echo’ before ‘freeultimate_video_render’, like this:

echo freeultimate_video_render

After taking a look at the plugin, they are implementing the shortcode in an outdated way, so it is not obvious what the php function is to a novice user.

The PHP function you need to add to a page is:

<?php
$video_id = 'VIDEO ID HERE';
freeultimate_video_render(array('conta' => '0', 'id' => $video_id));
?>

Like I said, it wouldn’t be obvious as to what the function is to a novice user, so please, copy the code exactly and change only the VIDEO ID HERE and it should work.

*note – untested

If there’s a shortcode, there is a php function that process it. Adding the shortcode is an easy way add PHP functions to your pages.

Was there a shortcode or not?

andrewkro, in Thesis 1.7, the option was moved to the Page Options screen, located at /wp-admin/admin.php?page=thesis-pages

Hope that helps. ?

While manually inserting PHP code is the most flexible, you are kind of limiting your audience to those who know how to do that and/or want to.

It would be nice to see an option on the option page that automatically inserts the code into the proper hook (probably after post content), but have it turned off by default. That way, you retain the ability to place it anywhere in the template, but if you are an End User that doesn’t really want to mess with stuff like that, you can still enjoy the plugins functionality as well by simply checking a box.