tweet shortcode broken due to API sunsetting at twitter #8130
Comments
|
Also encountered this error, but with a slightly different error message: When I try https://api.twitter.com/1/statuses/oembed.json?id=1099215039486140418&dnt=false manually though it works. Seems like this might be an intermittent problem. Is there any way to add a retry to the |
jmooring
added a commit
to jmooring/hugo
that referenced
this issue
Oct 31, 2021
The existing endpoint will be retired and removed on November 23, 2021. References: - https://twittercommunity.com/t/consolidating-the-oembed-functionality/154690 - https://developer.twitter.com/en/docs/twitter-for-websites/oembed-api#Embedded This is a backward compatible change. The existing endpoint requires a single parameter: the id of the tweet. The new endpoint requires two parameters: the id of the tweet, and the user with whom it is associated. For the moment, if you supply the wrong user, the request will be redirected (with a small delay) to the correct user/id pair. This behavior is undocumented, but we will take advantage of it as Hugo site authors transition to the new syntax. {{< tweet 1453110110599868418 >}} --> works, throws warning, deprecate at some point {{< tweet user="SanDiegoZoo" id="1453110110599868418" >}} --> new syntax Fixes gohugoio#8130
jmooring
added a commit
to jmooring/hugo
that referenced
this issue
Nov 1, 2021
The existing endpoint will be retired and removed on November 23, 2021. References: - https://twittercommunity.com/t/consolidating-the-oembed-functionality/154690 - https://developer.twitter.com/en/docs/twitter-for-websites/oembed-api#Embedded This is a backward compatible change. The existing endpoint requires a single parameter: the id of the tweet. The new endpoint requires two parameters: the id of the tweet, and the user with whom it is associated. For the moment, if you supply the wrong user, the request will be redirected (with a small delay) to the correct user/id pair. This behavior is undocumented, but we will take advantage of it as Hugo site authors transition to the new syntax. {{< tweet 1453110110599868418 >}} --> works, throws warning, deprecate at some point {{< tweet user="SanDiegoZoo" id="1453110110599868418" >}} --> new syntax Fixes gohugoio#8130
jmooring
added a commit
to jmooring/hugo
that referenced
this issue
Nov 1, 2021
The existing endpoint will be retired and removed on November 23, 2021. References: - https://twittercommunity.com/t/consolidating-the-oembed-functionality/154690 - https://developer.twitter.com/en/docs/twitter-for-websites/oembed-api#Embedded This is a backward compatible change. The existing endpoint requires a single parameter: the id of the tweet. The new endpoint requires two parameters: the id of the tweet, and the user with whom it is associated. For the moment, if you supply the wrong user, the request will be redirected (with a small delay) to the correct user/id pair. This behavior is undocumented, but we will take advantage of it as Hugo site authors transition to the new syntax. {{< tweet 1453110110599868418 >}} --> works, throws warning, deprecate at some point {{< tweet user="SanDiegoZoo" id="1453110110599868418" >}} --> new syntax Fixes gohugoio#8130
bep
pushed a commit
that referenced
this issue
Nov 1, 2021
The existing endpoint will be retired and removed on November 23, 2021. References: - https://twittercommunity.com/t/consolidating-the-oembed-functionality/154690 - https://developer.twitter.com/en/docs/twitter-for-websites/oembed-api#Embedded This is a backward compatible change. The existing endpoint requires a single parameter: the id of the tweet. The new endpoint requires two parameters: the id of the tweet, and the user with whom it is associated. For the moment, if you supply the wrong user, the request will be redirected (with a small delay) to the correct user/id pair. This behavior is undocumented, but we will take advantage of it as Hugo site authors transition to the new syntax. {{< tweet 1453110110599868418 >}} --> works, throws warning, deprecate at some point {{< tweet user="SanDiegoZoo" id="1453110110599868418" >}} --> new syntax Fixes #8130
|
We've updated the shortcode to use the new oEmbed endpoint; this will be available in the next release. The failure you noted with tweed id 1187377527901360129 is not related to the API. This was simply a page not found (see https://twitter.com/x/status/1187377527901360129). The failure you noted with tweet id 1099215039486140418 is not related to the API. If you continue to experience this problem, please use the forum (https://discourse.gohugo.io) for questions and troubleshooting. We prefer to use GitHub for verified bugs and vetted enhancements. Thanks. |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Hugo are you using (
hugo version)?Does this issue reproduce with the latest release?
Yes
Description
I just went to write my first blog post in over a year, and running
hugo server -Dfailed with the following error outputTrying the link manually I get an error, if I strip part of the url down to
https://api.twitter.com/1/statuses/I get the following responseLuckily I only had 4 instances of the shortcode in my blog so I was able to quickly hardcode in the correct html in order to be productive, but I guess this needs to be fixed to follow the guide here https://developer.twitter.com/en/docs/twitter-for-websites/embedded-tweets/overview if I'm reading this correctly it also seems that it's no longer possible to just use the tweet id by itself.
The text was updated successfully, but these errors were encountered: