Plans for the Next Release

As you probably know, Facebook announced some big changes at the
F8 conference. They announced new features that are pretty
interesting and have received a lot of press. They also
announced major simplifications to their APIs.

Simplification is a good thing. And keeping in step with
facebook's changes, the next release of Drupal for Facebook will
be The Simplification Release. Here's some of what's in store
for Drupal for Facebook 3.0.

First, we'll use two new libraries. The new javascript API and
PHP API are both open source, provide a more consistant interface
than the current ones, and are more likely to be future
compatible. Anyone who follows facebook development knows the
APIs have been in major flux since their inception. Now we have
some hope of stability going forward.

Next, we'll drop support for FBML canvas pages. This is a huge
change, and somewhat ironic in that FBML canvas pages were the
total API available when facebook first announced their platform.
Facebook has now deprecated this approach. This simplifies
things for facebook, as they can view Facebook Connect based apps
and iframe based canvas pages as essentially the same thing. And
guess what, we can view them as essentially the same thing, too.
This will have a huge simplifying effect on Drupal for Facebook.

This does mean that anyone building FBML canvas page apps will
have to do some rethinking, or at the very least re-theming.
It's time to create an iframe theme instead of FBML. It also has
some implications for multiple app support and session
management. With the current scheme, all apps hosted on a single
domain will want to share the same session. So to support
multiple apps will introduce some complexity that was not needed
in the current release. Most Drupal for Facebook sites only host
one app, and hopefully this added complexity will never affect
those sites.

Another major simplification has to do with initializing the
APIs. The current version of Drupal for Facebook jumps through
some hoops, as anyone who has looked at fb_api_init() knows.
Most of these changes are behind the scenes, but believe me it is
nice to know that many complex lines of code are going away.

After the simplification, we'll add support for new features.
For example the Like widget and others that Facebook announced.
And of course the Open Graph. Stay tuned for details...

Facebook comments

I'm trying to understand if this module allows for comments to be posted *from* facebook to a drupal site - is that a current function?

User's can post to a drupal

User's can post to a drupal server through a canvas page. For example, you could leave a comment on
http://apps.facebook.com/drupalforfacebook/comment/reply/1976#comment-form

The facebook api has ways to read content from a stream, but you'd have to write some custom code for that.

This is pretty awesome,

This is pretty awesome, looking forward to the next release!

Is there an ETA for this

Is there an ETA for this newer release?

It is in beta. Available on

It is in beta. Available on the Drupal for Facebook project page.

Hi, Just wondered if you

Hi,

Just wondered if you have checked out the FB Social module at http://drupal.org/project/fb_social. I think it rightfully belongs as a component of your more comprehensive module (though the two do play well together).

A quick question:

Let's say we run site A.example.com and B.example.com on a multi-site setup, and define the base domain as example.com on the app, the obvious attraction being that although the subdomain sites deliver different features that are 'sold' to users separately,we don't have to create 2 apps on Facebook. How can we ensure that a user permissioning the app for subdomain A bookmarks the homepage of a.example.com and one permissioning the app for subdomain B bookmarks the homepage of b.example.com.

To see what I mean, see second6.peppervillage.net and second7.peppervillage.net. Both of them have the same app settings. The form on the site you save last is the one that updates the facebook app, making it the default site on the app. The ideal user experience would be to have the user permission the app once, but can bookmark each site's funcitonality separately. Any ideas? Feel free to mess around with the sites - the admin username and passwords are 'admin'.

Thanks in advance for your advice!

Thanks
Srini

limitation of facebook

I do know of fb_social, and I expect they will continue to work well together. I will add more social graph features to modules/fb as needed. But I don't want to re-invent the wheel.

Your other question is a limitation on facebook. each app has only one bookmark URL. So if you want two bookmarks, you need two apps. The same goes for canvas URLs, profile tabs, and anything else that facebook provides only one per app.

Thank you Dave. Best Srini

Thank you Dave.

Best
Srini

Very cool, looking forward to

Very cool, looking forward to it

Nice

Nice

test

test

I like this