Instructions don't include the need to download simplexml, which is not included in the php 4/5 client. It requires a separate download from http://sourceforge.net/project/downloading.php?groupname=ister4framework...

Below is the current text file, it should include the following:

Download the simplexml framework from: http://sourceforge.net/project/downloading.php?groupname=ister4framework...
and extract it to the "./modules/fb/facebook-platform/php4client/(simplexml44-0_4_4)" directory

This is an early development release of Drupal for Facebook. Expect
things to change...

More information: http://www.drupalforfacebook.org

by Dave Cohen (dave@dave-cohen.com)

To install:

- Link or move the contents of ./themes/ into a Drupal themes directory.
(The themes are so closely associated with the modules that it seemed appropriate to include them here, rather than download seperately.)

- Download the facebook-platform PHP code from developer.facebook.com.
Extract it into this directory, so you have modules/facebook/facebook-application/
Make sure you extract the client API for PHP4, and simplexml, as instructed by Facebook. Note that even if you are running PHP5, Drupal for Facebook uses the PHP4 client API, and will continue to use it until Drupal supports PHP5.

- Edit your settings.php file (somewhere in the sites directory) to
include settings.inc (in this directory). For example:

require_once "profiles/custom/modules/fb/settings.inc";

- Enable the Facebook modules via the drupal admin pages, as usual.
You must enable at least fb.module and fb_app.module.
You will probably want to enable most of the others.

- It is highly recommended that you enable clean URLs.
If you don't, some links that drupal creates will not work properly on canvas pages.

- Create a Facebook Application (under "create content").
You will have to create the application on Facebook.com first, to get the secret and api key fields. Then fill those values into the form on Drupal. It will suggest a callback URL for you to use. Go back to the form on facebook and fill the callback URL field in.

CommentFileSizeAuthor
#1 Readme.txt115 bytesfrankcarey

Comments

frankcarey’s picture

Status: Active » Reviewed & tested by the community
StatusFileSize
new115 bytes

I Cleared the readme.txt and put in the following:

Drupal for Facebook

Installation and setup documentation now available online
http://drupal.org/node/195035

Figured everyone SHOULD have net access, and it would be easier to keep things updated this way.

robertdouglass’s picture

Just wanted to say that I ran into this issue as well. I would advocate as a first choice having the README, the project page description (drupal.org/project/fb) and the online documentation all being complete. As a second choice I'd advocate making one of the three complete and referencing that source from the other two. The README.txt as is only helps a little bit. I'm a fan of README.txt and the drupal.org project page, less a fan of documentation stored elsewhere.

Dave Cohen’s picture

Status: Reviewed & tested by the community » Fixed

I've added a link to the online documentation in the readme. However, I will not remove all the contents of the readme in favor of the online doc. I'll use the readme to document the very latest changes, and the readme can be specific to a particular version, while the online doc is more one-size-fits-all, if you know what I mean.

frankcarey’s picture

Yes, that seems ok, but a partially incomplete README is tough on first-time users when its not evident that the information is incomplete (hence the idea of just pointing people to the online doc). If we are going to keep 3 major places to get information on the module, we should definitely do a better job outlining the minimum FILE requirements (simple xml, actions, etc.) everywhere, even on http://drupal.org/project/fb the project page. Perhaps it would be easy to just cut and paste the Current Online DOC into the README for each release?

What do you think?

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.