The "tweet" shortcode will soon require two named parameters: user and id

hendry · December 2, 2021, 11:16am

Hi there,

I noticed on my site GitHub - kaihendry/dabase.com: Kai Hendry's tech blog

Is there some back story, why? Is there some migration script?

Many thanks!

alexandros · December 2, 2021, 11:25am

This was due to a change that happened upstream.

See the following commit for all the details:

github.com/gohugoio/hugo

Update Twitter shortcode oEmbed endpoint

committed 02:51PM - 01 Nov 21 UTC

jmooring

+191 -79

The existing endpoint will be retired and removed on November 23, 2021. Referenc…es: - 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

alexandros · December 4, 2021, 8:00am

This topic was automatically closed after 42 hours. New replies are no longer allowed.

Topic		Replies	Views
Fetch the latest tweet when compiling support	7	792	January 29, 2022
Hugo fails to build if Tweet is deleted support	8	1339	February 29, 2020
Is there a way to avoid the Twitter shortcode throwing an error if the linked tweet becomes unavailable?	2	1069	September 3, 2019
Resolve Tweet URLs feature	4	1174	January 20, 2022
Embed Tweet	1	2668	August 15, 2018

The "tweet" shortcode will soon require two named parameters: user and id

Related topics