solved Facebook API advice gives me the heebie-jeebies

researchcooperative
@researchcooperative
4 years ago
694 posts
Hi... I received the message below from FB today. I can read the words but the sentences make my mind go blank. The overall impression I get is this: "FB has done something to something. This might affect you or not. You can do something to something to find out if you need to do something to something." When I log in to my dashboard at FB, I see the same message.

Do I need to do something about something, and where should I begin?

Peter

3.1 Upgrade Notice
YOURSITE has now been upgraded to Graph API v3.1.
Graph API v3.0 reached the end of the 2-year deprecation window on 28 July, 2020. If you've already upgraded your code to call API v3.1, your app shouldn't be affected by these changes.

To make sure your app isn't impacted by API version upgrades in the future, use the new Version Upgrade Tool to understand your app's API calls and stay current with the latest version. You can also visit the changelog to see the full list of changes in all Graph API versions.
You can ask questions and give feedback in the Facebook Developer Community group.
You can view this and other developer notifications related to your app in the app dashboard.
Visit app dashboard



--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)

updated by @researchcooperative: 01/19/21 11:42:43AM
michael
@michael
4 years ago
7,714 posts
Nothing you need to worry about. It's saying: "the way we used to do things has changed and all that effort you put into getting it to work is probably broken now. Please re-do all the effort to match the new way of doing things. Vent your complaints and frustrations HERE where other developers can see them(we're probably going to ignore your comments though)"
researchcooperative
@researchcooperative
4 years ago
694 posts
Thanks. With your prognosis, I'm all fixed and only need to attend therapy for post-operative recovery


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)

updated by @researchcooperative: 07/29/20 09:31:40PM
michael
@michael
4 years ago
7,714 posts
lol. :)
researchcooperative
@researchcooperative
4 years ago
694 posts
More joyful messages from Facebook (20th October 2020):

Changes to token requirements will break your applications function

Action required: You need to generate a client or app token to access user pictures starting October 23, 2020 @ 10AM PDT

(Following the links provided led me deeper into a jungle where I suspect snakes and tigers are lurking. Perhaps I should turn off social sign in and let all my Facebook members fade into ghostly ciphers). Can I ask for help with this?


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
michael
@michael
4 years ago
7,714 posts
You can pretty much ignore it. You needed to agree to get the key, so they send you the messages. But its the module that does the connecting, and even then its OneAll that takes care of the connection.

Years ago we tried to make native connection scripts but got so sick of having to update it just to keep it running everytime facebook or other decided to change it, this time we found OneAll who handle that part for us. :)

So as long as the connection between your Jamroom site and Oneall is working (which has been pretty stable for many years) then they will take care of the connection necessities to facebook at their end. Thankfully.