Posting Running workouts to Facebook Wall (Read 2601 times)

This is what I was hoping for!

You need to click the Publish button and grant the app the necessary permissions to post to your wall.  You then should see a set of 3 radio buttons that lets you control which workouts to publish.  After that, try logging a new workout and see if it is posted to your wall.

This is what I was hoping for!

 

You need to click the Publish button and grant the app the necessary permissions to post to your wall.  You then should see a set of 3 radio buttons that lets you control which workouts to publish.  After that, try logging a new workout and see if it is posted to your wall.

I don't get the 3 radio buttons.  I go to application settings and remove additional permissions so that I can get the Publish button in the Running Ahead Facebook preferences.  I click Publish, and I get the Request for Permission dialog (shown below).  I click Allow, the dialog closes and my Facebook preferences look like they did before.  I click Save, the tab changes from the Preferences tab to the Summary tab.  When I go back to the Preferences tab, there's no longer a Publish button, and my Application Settings for RunningAhead has the Additional Permission tab and both the toggles for Access my data when I'm not using the application and Publish content to my wall are selected.  Just as a side note, everything was working very well until the beginning of September, so my Permissions were set correctly once upon a time.

I looked more into this problem and the javascript error does have something to do with it.  It was a head scratcher until I realized this is a bug in my code that is introduced by Facebook.  Facebook sanitizes each application's javascript code to ensure the application doesn't do anything malicious.  One of the safety precautions involves renaming all the variable names.  FB erroneously renamed a number as a variable and thus breaking everything.  I worked around the problem and the radio buttons reappeared.

Try removing the app's permissions and then re-enabling Publishing again.  You should see the radio buttons this time.

By the way, thank you for the screen shots.  It really helps in tracking down the problems.

eric :-)

Thanks Eric.  RA is posting on Facebook.

Mr. Lopez,

This is for your amusement:

The broken code involves converting distance from kilometers to meters, which is something like "meters = kilometers * 1000".  Simple enough.  I use Google's Closure Compiler to compress all the javascripts.  It reduces the file size, which reduces download time.  A smaller file means less parsing, which means shorter execution time.

The Closure Compiler is very interesting because it actually rewrites the logic to produce smaller code.  I can give you examples of this if you like.  In the unit conversion case, the compressed code looks something like: "m=k*1E3".  As you know, 1E3 is the exponential representation of 1000, and is a valid number in javascript.  When FB does its check, it renames the line as "A5234234_m=A5234234_k*1A5234234_E3".  The "A5234234_" prefix wraps the app's code in its own namespace.  Somehow, the prefix is inserted between 1 and E3.  Since everything is wrapped in a try/catch block, the error is silently dropped.  Great fun!

This still isn't working for me. I get the Publish button. When I click on it, I just get a Loading message, but never get the permission request. Firebug shows that the page makes 2 successful requests for data.

I have tried removing the app's permissions and then re-enabling Publishing again.  Still doesn't work. Please help.