Has this been taken care of by the @team?
oEmbed endpoints are now officially deprecated.
I have read about this in some topics here and it was announced by FB a long time ago:
I think a similar approach as for the Twitter oneboxes is required going forward.
Looking at:
This appears to still be working and we are beyond October 24
It appears we are using open graph here:
meta name="description" seems stable even if facebook decide to junk opengraph one day…
I am not really seeing that we need to do anything special here @techAPJ
Is anything actually broken today?
The Instagram oneboxing is currently broken here on meta:
https://www.instagram.com/p/CGyuQuwoMFR
… that is even after we updated the Instagram onebox to use OpenGraph tags.
Instagram oneboxing is currently broken on our hosted sites as well.
Is this going to be addressed at some point or in any kind of backlog?
Yes it is. No timeline, but I have seen discussion going on. I believe right now we’re working to determine if we can obtain the necessary info to onebox without any credentials, or if we’ll need to follow a similar route to Twitter rich embeds.
https://www.instagram.com/p/BZDhAJuFH-b/
We certainly need to debug this (@jamie.wilson is investigating providing better details on why we do not onebox to the end user) … in my case above we have:
<title>
Amazing Kitchen Gadgets on Instagram: “We have only just caught up on the #GBBO 😱😱 Did you watch it the other night or have you not seen it yet? Tell us your thoughts! 🍰🍰…”
</title>
<meta content="11 Likes, 1 Comments - Amazing Kitchen Gadgets (@amazingkitchengadgetuk) on Instagram: “We have only just caught up on the #GBBO 😱😱 Did you watch it the other night or have you not seen…”" name="description" />
<meta property="og:site_name" content="Instagram" />
<meta property="og:title" content="Amazing Kitchen Gadgets on Instagram: “We have only just caught up on the #GBBO 😱😱 Did you watch it the other night or have you not seen it yet? Tell us your thoughts! 🍰🍰…”" />
<meta property="og:image" content="https://instagram.fsyd7-1.fna.fbcdn.net/v/t51.2885-15/e35/21688697_318778721927636_8744554647311613952_n.jpg?_nc_ht=instagram.fsyd7-1.fna.fbcdn.net&_nc_cat=108&_nc_ohc=YpwZaaId-vUAX-03OGr&tp=18&oh=3b6a96f126f5841c524572b0ed062678&oe=5FC8972F" />
<meta property="og:description" content="11 Likes, 1 Comments - Amazing Kitchen Gadgets (@amazingkitchengadgetuk) on Instagram: “We have only just caught up on the #GBBO 😱😱 Did you watch it the other night or have you not seen…”" />
It seems to be to be enough information to build a onebox, we need to debug why we are not getting a onebox here (and we will explain that to end users in a future update)
Thanks you for supporting!
hi, i’m on 66ecefba52f4d907f035bc7c445d98883e1ff792 and something weird is going on with my IG oneboxes, it just creates a single anchor tag with the site domain, then the instagram url which obviously doesn’t exist… now I can’t even disable this behaviour?
i got an app access token from fb/insta oembed via
curl -X GET "https://graph.facebook.com/oauth/access_token ?client_id={your-app-id} &client_secret={your-app-secret} &grant_type=client_credentials"
i tested the oEmbed API w curl -X GET \ "https://graph.facebook.com/v9.0/instagram_oembed?url=https://www.instagram.com/p/fA9uwTtkSN/&access_token=IGQVJ..." and it worked fine… i figured that’s what discourse is using (https://github.com/discourse/discourse/blob/331236d6d790dd41538668469f16f853c5699884/spec/components/oneboxer_spec.rb#L289)
nothing useful or related in /logs either… any way i can debug this?
same image on meta:
tia! 
Did you add the app access token to the facebook app access token site setting?
i think so, it’s the app id (pipe | ) base64 secret, yes?
edit: it’s working on another discourse instance i manage, with the same creds, so i think they’re fine.
i tried /safe-mode and still no luck, i’m just comparing the settings between instances now
this is what /onebox?url=https%3A%2F%2Fwww.instagram.com%2Fp%2FCHxqj3bMxJc%2F&refresh=false&category_id=15&topic_id=21558 returns:
<aside class="onebox instagram">
<header class="source">
<a href="https:/www.instagram.com/p/CHxqj3bMxJc" rel="noopener"></a>
</header>
<article class="onebox-body">
<h3><a href="https:/www.instagram.com/p/CHxqj3bMxJc" rel="noopener">@</a></h3>
</article>
<div class="onebox-metadata">
</div>
<div style="clear: both"></div>
</aside>
Fixed by removing discourse-onebox-assistant
Ooh thanks for the heads up. No time to look at that at mo but will bear in mind when I next get chance. PR welcome.
I’ve pushed an update to include the new Discourse code. Hopefully compatibility is improved.