The problem is that when you line them all up the Facebook share button is actually wider than the others which seem to come in at 52px.

Well you can make the Facebook button 52px in width without too much trouble. Facebook only use two classes to style the inner ‘Share’ button which seems to be the decider when it comes to the buttons width.

By shaving a little off the left and right padding we can bring the Facebook share button back down to 52px in width and make it play nice with the other share buttons.

<style type="text/css">
span .FBConnectButton_Small .FBConnectButton_Text 
{
	padding:3px 2px 2px;
}
</style>

The extra span is just enough to beat the included Facebook css with a higher specificity score by 1 single point.

Well the wiki article is quite large but misses a few points I thought it worth noting…

1) You need to escape all forward slashes with a backslash

In the regexp / always needs to be submitted as \/

2) The url they match again is the full callback url you submitted for your app not the canvas url

You aren’t matching just the file names, you can match back down the folders.
So if you use a folder called myapp/ for your index page then your url regexp could be ‘myapp\/$’ for the home page
You could then do ‘myapp\/anotherpage\.php$ for a different file and ‘myapp\/folder\/$ for another folder

3) Whatever keys you use in the submitted array are used as the new $_POST var keys

They take your array key ‘user_app_friends’ below and append ‘fb_sig_’ to it. The final key would be ‘fb_sig_user_app_friends’ in this case

4) You can submit multiple matches in one api request

Although the examples only show:

$fetch = array(
	'user_app_friends' => array(
				'pattern' => 'myapp\/$', 
				'query' => 'SELECT uid FROM user WHERE has_added_app=1 and uid IN (SELECT uid2 FROM friend WHERE uid1 = {*user*})')
		);
$facebook->api_client->admin_setAppProperties(array('preload_fql' => json_encode($fetch)));

You could submit:

$fetch = array(
	'user_app_friends' => array(
				'pattern' => 'myapp\/$', 
				'query' => 'SELECT uid FROM user WHERE has_added_app=1 and uid IN (SELECT uid2 FROM friend WHERE uid1 = {*user*})'),
	'user_friends' => array(
				'pattern' => 'myapp\/.+$',
				'query' => 'SELECT uid2 FROM friend WHERE uid1 = {*user*}'
				)
	);
$facebook->api_client->admin_setAppProperties(array('preload_fql' => json_encode($fetch)));

5) The easiest way to get data back from the new $_POST variables in json_decode

Stick the $_POST variable into json_decode(); and then use var_dump to see what you get. It’s usually pretty obvious.

$user_app_friends = json_decode($_POST['fb_sig_user_app_friends']);
var_dump($user_app_friends);

The publisher interface is what you see on all profile pages and on your home page. It is how you change your status, and can use it to publish link and photos too. The final option is to use one of you applications who offer a publisher.

Because the publisher is now used on the home and profile pages which have different widths, and Facebook have yet to document any explanation of how to make your publisher interface inline easily I spend a bit of time tinkering.

So if your apps publisher interface is currently popping up in a dialog, and you want it inline, there are the steps I know to work. You may need to do more or less.

1) Use a containing div with no width set to it
2) Ensure any tables have width:100% on them
3) Ensure the total maximum width is less than 376px
4) Use as few fixes width as possible

Only once you have completed the steps above, go to your app settings and on the profile tab, change the option to inline instead of dialog. If you are already on inline, switch to dialog, save, and then switch back.

Currently, one big pain in the backside.

Very good questions.

Basically there are none.

You get all the benfits of a group with a page, with the added benefit of being able to send fan updates to all the page fans. With a group you can’t send out messages if there are more than 1000 5000 members.

The only large difference is that a persons groups appear in a large mush of blue text on their info tab, which a persons pages appear nicely separated below that.

So if you are wondering if you should start a group or a page, always go for a page. If you can’t think of a category to add it under, always add it to ‘Brand or Product’ -> ‘Non-profit’.

If you already have a group, with enough members for you to want to keep them then I suggest you request to transfer them over to a page of the same name.

You can so that by selecting ‘Pages’ from the dropdown menu on this page:

http://www.facebook.com/help/contact_generic.php

and sending them your details.

Facebook will want the address of your current group, the name you would like for your new page and the category you would like your page to appear in.

So as long as your group meets certain minimum requirements to become a page you should be sorted and able to contact all your members by using a page update.