Twitter oEmbed error after WP 6.4 update
-
Hi there, after updating to WordPress 6.4 I have a problem while embedding tweets.
Both on Block and Classic Editor, the tweet is no longer rendered as it should when the link is pasted into the editor. The Classic Editor does not give specific errors, while on the Block Editor the error “This content can’t be embedded” is shown. Looking at the requests, I get a 404 error at the oEmbed proxy endpoint. It never happened before the update, so I don’t know what goes wrong. If I try to open that link, I get a 401 error that says that I am not allowed to make such a request from the browser, which should be correct. Existing embeds are not affected and I can still embed the old way, but with oEmbed everything is much quicker.
If you need other info, please let me know! Thank you.
-
@threadi Sure. I don’t do anything special, I just paste a tweet link in the Twitter block and it returns an error. Normally I would be able to see the tweet in the editor, but this is not the case because of that 404 error to the oEmbed path. And by the way, if I embed a tweet in the editor and it returns an error, the tweet can’t be seen as expected in the frontend.
You can find screenshots here. (The error is in Italian, but it can be translated as “This content can’t be embedded”.)
- The topic ‘Twitter oEmbed error after WP 6.4 update’ is closed to new replies.