WordPress.org

The comments addon isn't working!

You have to modify your theme to use the comments plugin.

(Note: If you have WordPress 3.0 and a theme using the new comment_form() method, then this step is not necessary).

In your comments.php file (or wherever your comments form is), you need to do the following.

1. Find the three inputs for the author, email, and url information. They need to have those ID's on the inputs (author, email, url). This is what the default theme and all standardized themes use, but some may be slightly different. You'll have to alter them to have these ID's in that case.

2. Just before the first input, add this code: [div id="comment-user-details"] [?php do_action('alt_comment_login'); ?]

(Replace the []'s with normal html greater/less than signs).

1. Just below the last input (not the comment text area, just the name/email/url inputs, add this: [/div]

That will add the necessary pieces to allow the script to work.

If you're using WordPress 3.0 and the new "comments_form" code (like in the Twenty Ten theme), then this is unnecessary! Check ottopress.com for info on how to upgrade your theme to use the new 3.0 features.

Facebook Avatars look wrong.

Facebook avatars use slightly different code than other avatars. They should style the same, but not all themes will have this working properly, due to various theme designs and such.

However, it is almost always possible to correct this with some simple CSS adjustments. For this reason, they are given an "fbavatar" class, for you to use to style them as you need. Just use .fbavatar in your CSS and add styling rules to correct those specific avatars.

Also note that Facebook "square" avatars are limited to 50 by 50 pixels in size. If your theme uses a bigger one, then it'll get scaled up and may look bad. There's no easy fix for this, as the other avatars offered by Facebook are not square shaped. If it returned those, then it could mess up many more themes. complain to Facebook and tell them to offer larger squared off avatars.

How do I use this Fanbox custom CSS option?

Well, first you have to learn CSS.

Next, try starting with this code in the custom CSS box: .connect_widget .connect_widget_facebook_logo_menubar {} .fan_box .full_widget .connect_top {} .fan_box .full_widget .page_stream {} .fan_box .full_widget .connections {}

That should be enough to get you started.

How do I use this with multi-site across subdomains/subdirectories?

(This is a new feature to 0.21 and it has NOT been really tested well yet. You have been warned.)

Many people want to set up a "network" of sites, and enable SFC across all of them. Furthermore, they'd like people to stay "connected" across them all, and to only use one Facebook Application to connect their users. This is entirely possible with a bit of setup.

First, create your Facebook Application. It should use the base domain field as well as the normal fields. No subdirectories or subdomains anywhere. For this example, we'll use "example.com".

Next, you can add these to your site's wp-config: define('SFC_APP_SECRET', 'xxxxx'); define('SFC_APP_ID', 'xxxxx'); define('SFC_FANPAGE', '(this one is optional)');

These are the exact same settings as on the normal SFC base configuration screen, and they will override those settings for the entire network of sites. In fact, when those are defined, the corresponding settings options won't even appear. This may look odd at first.

With this setup, SFC should work across all your subdomains and subdirectories. So it'll work on example.com or blog.example.com or otto.example.com or whatever. It should also work on example.com/blog.

The "base domain" setting on your Facebook application is important. In this case, it MUST be set to the base domain (example.com), so that the cookies will be set there and thus will let you stay "connected" across the sites.

Leaving the Fan Page setting undefined will allow each site to enter in their own Fan Page, but still using your single Application to publish to them.

Notes: * SFC-Login may or may not work. It's hard to say. Try it, it might work. I need more info to debug this. * Using other base domains with the domain mapping plugin absolutely will NOT work. Period. The redirection to the base domain for login breaks SFC-Login, because there is no way for Facebook to stay connected across domain names.

Email me if you have problems... But only if you're also willing to help solve those problems, I can't reproduce most setups and I can't fix what I can't see.

How do I use Facebook Avatars?

The Comments module will automatically use Facebook avatars for users that leave comments using Facebook.

The Login module can optionally make the system use Facebook avatars instead of Gravatars, for users that have connected their accounts to Facebook.