Need help generating profile box using Drupal for Facebook

Add a button to your template for adding to profile:

http://wiki.developers.facebook.com/index.php/Fb:add-section-button

Once upon a time users would "add" an application and automatically get a profile box. But that was the old way. Now, applications must get permission to do things like write a profile box. Facebook gives more control to users now.

Facebook provides pages where users can grant this sort of permission to each app. Also, applications can give users a chance to grant these permissions, using links and buttons authored in FBML. That means you can create a canvas page which gives the user a link to click on to add a profile box.

Drupal for Facebook, in fb_user.module, provides links for all extended permissions. If you have canvas pages enabled, try visiting app.facebook.com/YOUR_APP/user (the my account page). Then click the edit tab and the app sub-tab. There you should see links for various permissions and buttons for profile boxes. Why links in some cases and buttons in others? Ask Facebook. The idea behind this page, BTW, is that your app can implement hook_form_alter to show only the extended permissions which are actually relevent to your app.

Profile boxes are also weird in that you have to provide some content for the boxes before they can be added. In the Facebook App settings form you can provide a default profile box content.

See the link NigelC provided and also http://wiki.developers.facebook.com/index.php/Extended_permissions

Regarding the profile_setFBML, the action you created to write to the profile box would normally do this. However in your case your app is not requiring users to authorize the app, so I don't think the action will actually fire. Because the DFF modules will not know which users are users of the app.

The /user path is not found because you have things set up so that, as far as Drupal is concerned, the user is anonymous even when logged into facebook. That's OK. But I think you'll need the user to authorize the app before they can add the profile box.

You can create a custom page to accomplish this. Try making a Drupal page, using the PHP input format, with a body something like this:

This page will prompt the user to authorize our app.
<!--break-->
<?php
global $fb, $fb_app;

if ($fb) {
  // This tells Facebook to associate the app with the Facebook user.
  $fb->require_login();

  // And this code will set something in the profile box for the current user.  
  // Consider moving this to a custom module or another PHP page.
  $fb->api_client->profile_setFBML("this was set by a test page!");
  print("<p>profile_setFBML returned.</p>");  // debug
}

?>

<!-- this bit of FBML will present a button.  If clicked the profile box will appear -->
<fb:add-section-button section="profile" />

When you visit this page, facebook should prompt you to authorize the app. Then click the button, then check your profile boxes.

note: I haven't tested it, could be buggy.

take a look here for some examples: http://wiki.developers.facebook.com/index.php/Talk:Profile.setFBML

You may just need the fb:wide or fb:narrow wrapper. Its hard to tell when these problems are facebook bugs you must work around, or an error in the way you've called it.

The app settings on drupal are stored in a node. The node type is Facebook Application. Find that node and edit it. There is a fieldset for user settings. In there you can control whether Drupal for Facebook automatically creates Drupal users for each Facebook user, and whether it "maps" the accounts. Make sure those settings are on.

The uid in drupal will not be the same as the facebook id. In code, I call the facebook ids "fbu".

try this query on your database: SELECT * FROM authmap;
what do you see?

The first of those should map to uid 12, however, since that's the user who was logged on to UrbanMinistry.org (my Drupal site) at the time.

It doesn't work that way. When you visit apps.facebook.com/whatever, it makes no difference whether you're logged into whatever.com. It created a new local user.

it gives the "There are still a few kinks..."

Use your browser's view source feature. As the app developer, Facebook often includes helpful hints on pages with error messages. Probably, it's Drupal not letting you visit user/login, because you're already logged in.

I guess you would need to somehow link the two users - the user who logged in via facebook and the user who logged in via drupal directly. Not exactly sure how this works as I only create users from facebook.

For the FBML profile box, why not do it as a cron job rather than as logged in user?

I guess it depends on what you are trying to do, but for example my profile box is generated based on user editable info in the user profile (and based on cron data). Therefore I updated it when the user updates their profile (so the user is logged on), and based on a cron (it runs through x number of users per cron).

Anyway, regardless I think your problem is that the facebook user is different to the drupal login user. Dave will have to comment on if you can link these (I seem to recall something like that).

The facebook user id and the drupal id are mapped via Drupal's authmap table, but if and only if you select the appropriate checkbox on the Facebook Application node.

facebook did away with profile boxes.