completed Playlists and Players in Timeline - Plus Facebook Sharing?

Quote: jrOneAll error 403 sharing to facebook: The Freemium plan of your site does not include the Sharing API. Please upgrade to a higher plan to enable it: https://www.oneall.com/pricing-and-plans/

Quote: The other one is a s full sharing solution which is only available to
our business customers: http://docs.oneall.com/api/resources/social-sharing/

Ken_Rich:
Awesome - thanks - I'll try that.

Is anything planned for the other issues above the line in the post?

I'm talking about JR playlists and song players not embedding in timeline in a functional way? Youtubes also seem to have a height to width issue.

brian:
Ken - I've just updated the OneAll module to version 1.3.0 that now supports the new "simple" sharing endpoint (I'm not sure when they made that change).

Update and let me know if that works for you.

Hope this helps!

Quote: jrOneAll error 400 sharing to facebook: Your request could not be processed due to an error

Ken_Rich:
I'm strictly speaking of the timeline profile activity feed here... Vimeos and pictures seem to post pretty well using the jrEmbed tool... Youtubes seem too tall and narrow, at least in the Nova skin, as if width were shrinking but height wasn't.

JR's song and video playlists (plus single song players), seem to turn into non functional CSS messes for some reason. If there is no way to fix that, they should at least be be pruned from the editor (when it is used in the timeline), to prevent users thinking there are "bugs".

brian:
The timeline player issue should be fixed in the Activity Timeline version 1.6.3 - update, reset caches and you should be good to go.

brian:
a 400 error is coming from the OneAll end - go into your Networks tab (Account Settings -> Networks) and see if you see an error there.

brian:
that should "resetup" the connection in JR. Let me know if that works for you.

Quote: jrOneAll error 400 sharing to facebook,linkedin,twitter: Your request could not be processed due to an error

Quote: ...the developer has in fact only partially checked the response of our API.
As you can post for multiple networks at once, there is a global status and
more specific statuses for each social network.
Here is the full response

{
"response": {
"request": {
"date": "Wed, 26 Nov 2014 22:55:04 +0100",
"resource": "/users/xxxxxxxxxxxxxxxxxxxxxxxxxxxx/publish.json",
"status": {
"flag": "error",
"code": 400,
"info": "Your request could not be processed due to an error"
}
},
"result": {
"data": {
"message": {
"sharing_message_token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"date_creation": "Wed, 26 Nov 2014 22:55:04 +0100",
"publications": [
{
"provider": "facebook",
"user_token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"identity_token": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"status": {
"flag": "error_message_is_not_permitted",
"code": 403,
"message": "The provider did not accept the message: you do not have the permission to post on behalf of the user"
}
}
]
}
}
}
}
}

The interesting part is this:

The provider did not accept the message: you do not have the permission to post on behalf of the user.

In your OneAll Facebook setup you must enable this option:

Publish Actions - Request the permission to post content, comments and likes to a user's stream. Then you need to relogin with Facebook in your Jamroom site to update the permissions. Then it should work.

Ken_Rich:
The module doesn't give me a choice to connect any differently, so how is this ability enabled? If there documentation or something I am missing?