why does this instagram link onebox like this?
it also links to nowhere if I don’t use hyperlinked text (you can click on the one-boxed link above)!
the link:
https://www.instagram.com/p/B3jG277hve9/
why does this instagram link onebox like this?
it also links to nowhere if I don’t use hyperlinked text (you can click on the one-boxed link above)!
the link:
https://www.instagram.com/p/B3jG277hve9/
My guess is it is a private account?
Nope, that’s not a private account. Here’s another example from a fully public post:
Wow, I posted https://www.instagram.com/p/B6gUJwDl-lQ/
but the onebox redirects to this topic itself…
(edit my post to repro this in the composer)
What’s different about this photo versus others?
It seems that some Instagram pages have a canonical link with a different url that requires login. The code in the onebox library prefers the canonical url.
https://github.com/discourse/onebox/blob/master/lib/onebox/helpers.rb#L25-L40
For example, these are the canonical urls of the instagrams in this topic:
I’m getting this issue as well. Upgrading my installation now to see if it fixes.
@techAPJ can you fix this please? Basically we have to ignore canonical metadata for Instagram now…
Looks like we’ve regressed here, or Instagram changed something again. We’re back to just showing “Login • Instagram”. cc @techAPJ
Weird, that image on Instagram doesn’t have any og:
meta tags anymore. Couldn’t find any other that would have them missing…
The weird thing is Instagram onebox is working okay for me locally (on latest Discourse version). And I do see OpenGraph (og
) tags in incognito mode.
Reproducing this issue locally will be tricky… investigating more.
Is it specific to that one image?
No, I tried multiple images from multiple accounts and all were oneboxing fine locally.
Here’s an image from an hour ago on NatGeo oneboxing fine locally.
Might be geographical issue?
FWIW, Instagram oneboxing is failing on discourse.codinghorror.com as well, so this issue is not specific to meta.
Maybe the user agent changes the response?
this is broken on our forum as well
I don’t think so. We use same user agent for all the requests made from Discourse codebase as per:
Same issue on ours now here in the UK too.
I am updating Instagram onebox to use official oEmbed endpoints. I have this change working locally and expect to push a fix later today. Hopefully the Instagram oEmbed endpoints will not have geographical restrictions.