Skip to content

Vanilla apps are broken #14

zeke opened this Issue Apr 12, 2013 · 6 comments

5 participants

zeke commented Apr 12, 2013

I thought it might be the restler dependency of faceplate getting quietly updated to a version with breaking API changes, but restler hasn't been updated in quite some time.

I tried updating faceplate from 0.0.4 to 0.5.0, but that doesn't solve anything: a request to / just hangs and times out.

This callback doesn't get fired:

To get up and running with a localhost:5000 OAuth setup:

git clone
cd facebook-template-nodejs
heroku config:pull -a glacial-falls-8460
npm install
foreman start

Open localhost:5000.

zeke commented Apr 14, 2013

After much tinkering, I was able to get the app running. There were two bugs: one in faceplate, one in facebook-template-nodejs. Here are two pull requests that should solve it:

Note: I updated to the latest version of faceplate and edited the vendored faceplace dependency files right inside the template app. Once the faceplate pull request is merged, the template app will need to be updated to the new faceplate version, presumably 0.6.0.

Note2: If you're testing this locally, you may need to (counterintuitively) flip sandbox mode to disabled on your facebook app.

cc @ddollar @jesperfj @mmcgrana @jonmountjoy

zeke commented Apr 16, 2013

This has been fixed in #15 and deployed to Heroku, but sandbox mode still needs to be disabled for the app to work:

Sandbox is mode is enabled by default. The Youtube screencast in the devcenter article is now out of date, as it doesn't mention this now-necessary step.


Are the vanilla facebook templates still broken? I get an error right away when creating a facebook template app - Cannot read property 'name' of undefined.

Heroku member

Received a ticket about this still being broken. Same error as above.

friism commented Jul 10, 2013

There's also a Stackoverflow issue.

The PHP template is not broken out of the box. The issue is fixed when using the node.js template if one disables sandbox mode, as @zeke points out.

Since the PHP template can work without this, I'm sure the node.js one could be made to do the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.