-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Twitter/X Embed Block Not Working. #96010
Comments
Another case here: zd-8960105 |
8945481-zen |
User wants updates on when this is working again: #8990777-zd-a8c |
Support References This comment is automatically generated. Please do not edit it. |
This was reported here as well: 8985064-zd-a8c Quoting a relevant portion from the user's message:
|
This issue has also been reported here: 8989953-zd |
This thread is being discussed in slack-C07RS1SCKBK |
8997955-zd |
Workaround for Atomic sites would be using the manual embed feature from X: Alternatively, going to https://publish.twitter.com/# |
This has also been reported in |
Another report here: 9009327-zen |
Another report here: 9017138-zd-a8c The embed displays in the editor but converts to a link only on the live post. Simple site. |
A user reported this on X here. -- 9021072-zd-a8c |
Simple site - reported here 9040424-zd-a8c |
Update via slack-C07RS1SCKBK Currently, it may be possible the oEmbed cache is regenerated when a post is loaded by the author / an editor/admin. This means that if an embed is 'bad' on first load, a refresh or two of the post from the author (in the editor or frontend) can repopulate the embeds. |
I also made Slack announcement with the above here: p1732003945715219-slack-CB0B2G43X |
9063095-zen |
Reported in 9071401-zen Shared workaround. |
Raising priority on this one. |
Another report in 9083985-zd-a8c (Atomic Site). Shared workaround. |
Reported in 9084286-zd-a8c (via X). 9084356-zd-a8c 9088351-zd-a8c 9089207-zd-a8c |
9082819-zd |
9071401-zd |
Another report in 9167987-zen |
Another report in 9176848-zen ; however, this happens on a simple site with a Premium plan and a Block theme. It seems to work with a Classic theme. Custom HTML workaround does not work. When my test Premium site is downgraded to a free site, the block works. |
9166470-zen |
Another report: 9215065-zd-a8c |
9286282-zd-a8c @oskosk noting I closed this near-duplicate issue, which was about the classic editor; the underlying problem with both seems to be the same: we change an x.com link to twitter.com and break the embed. [Classic Editor] X embeds not working #98474 |
Reported in 9297202-zen. The site is atomic so suggested embedding the post via the Custom HTML block. |
Quick summary
On some sites Twitter/X embeds don't work, when adding a new one I get "Sorry, this content could not be embedded."
Steps to reproduce
What you expected to happen
Site displays the tweet.
What actually happened
"Sorry, this content could not be embedded."
Impact
Some (< 50%)
Available workarounds?
Yes, difficult to implement
If the above answer is "Yes...", outline the workaround.
However this is only a partial workaround, as it doesn't fix previously posted Twitter/X embeds.
Platform (Simple and/or Atomic)
Atomic
Logs or notes
zd-8986491
The text was updated successfully, but these errors were encountered: