Hello,

I just found this module, and have been looking at this one so far:
http://drupal.org/project/fb

how are they related?

Any plans of merging the two projects?

Comments

pvhee’s picture

Interesting to know more about this as well. I think the whole set of Facebook modules that exist for Drupal is very scattered, and that's a pity as they all need to use the same API. Couldn't we all agree on using some Facebook API module (Drupal for Facebook? http://drupal.org/project/fb) and then build our external modules on this API? At least this would allow people to mix the modules for Facebook, which I expect to be incompatible now.

rmiddle’s picture

This is a good question. It would be nice is someone were to take the time to write a comparison between the two version.

Thanks
Robert

pribeh’s picture

Bump what pvhee said in #1. Considering the constantly changing facebook api there could be some serious progress made through cooperation.

MaffooClock’s picture

Well, I tried that module. It's got potential and certainly uses more of the API than any other module. But I had a problem with it that I couldn't overcome, posted here: #484826: Using nodes for FB applications/templates feels "icky"

Writing a comparison isn't as easy as comparing apples to apples, as these modules don't quite have the same features. I agree -- Facebook Connect is great, but I like the potential in the FB module; I would also like to see them merge.

vectoroc’s picture

Status: Active » Closed (fixed)

There is no plans of merging

hanoii’s picture

Component: Miscellaneous » Documentation
Category: support » task
Status: Closed (fixed) » Active

@vectoroc: I searched over the issue queue and I saw a few issues mentioned about this and mainly closed(fixed) without much explanation. It might be very helpful/useful if you can put some kind of description on the project page explaining the main difference between these two modules and it will certainly help newcomers to facebook modules (like me) to decide which one to use. I appreciate this might not be possible because you might not know the other module, but even if that's the case, it's an useful note to have on the project's page. But being the developer of a this module, there's some insight that you may share.. have you tried the other module at all?

vectoroc’s picture

hanoii : in general Drupal For Facebook (D4F) is much more complex module. fbconnect implements only one submodule from D4F ( +/- some other functions ). Year ago I tried to use D4F but it was too unstable (and too monster) and I decided to take ownership over the fbconnect module.

Currently (afaik) D4F uses old facebook sdk. D4F tries to handle all facebook related tasks, while fbconnect goes to be small and simple module that does only connect function

giorgio79’s picture

D4F uses the new sdk since 6.3 :)

giorgio79’s picture

Title: This vs Drupal For Facebook? » This vs Drupal For Facebook - Join forces - Don't duplicate efforts
Version: » 7.x-2.x-dev

Now that there is a new maintainer perhaps it would worthwhile to consider joining forces for 7x to avoid duplication of efforts.

Drupal for Facebook has a Facebok Connect submodule that can be used standalone as well.

The drupal for fb maintainer is looking for company in his development efforts as well

#1166272: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st (a.k.a undefined method Facebook::getSession())

deggertsen’s picture

I would like a solid explanation on the differences between this module and drupal for facebook as well. Seems to me like this module is not necessary and should be depreciated in favor of drupal for facebook. Is there somebody that wants to refute that and explain why? Or are we going to simply continue duplicating our efforts here? At the very least Drupal for Facebook should be added as a Related Project so that people can see the options available.