[wp-trac] [WordPress Trac] #32553: Corrupted embeds

[WordPress Trac]

#32553: Corrupted embeds
-------------------------------+-----------------------
 Reporter:  pavelevap          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  reopened
 Priority:  normal             |   Milestone:
Component:  Embeds             |     Version:  4.1.5
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+-----------------------
Changes (by rfischmann):

 * status:  closed => reopened
 * resolution:  invalid =>


Comment:

 Sorry for reopening such an old ticket, but I've faced this issue for
 years and I believe it's the exact same behavior reported by @pavelevap.

 I simply gave up a couple of years ago and have been mostly using
 Twitter's (and also Instagram's) manual iFrame embeds, as they of course
 always work, but try to go back to the simpler/quicker oEmbed feature by
 pasting the URL to see if any recent WordPress update fixes it for good.
 Nope.

 Both Twitter and Instagram always work fine when I'm writing the post and
 publishing it for the first time. Then, I don't know why, after a few
 hours or days, their embeds break and we only see the URL in the post.
 When I go into the post's meta information on my MySQL database, I can see
 its embeds are all set to `{{unknown}}`. If I delete all `_oembed` lines
 from the post, the embeds start working again.

 Simply hoping into the broken post's editor in WordPress, changing
 something and re-saving it doesn't clear the oEmbed cache and they stay
 broken. Also, from inside the editor (Gutenberg), all embeds always show
 up fine — I believe they're not cached there.

 I never have any issues with YouTube's or Vimeo's embeds, only Twitter and
 Instagram.

 It doesn't make any sense at all for WordPress to cache a broken oEmbed
 request with `{{unknown}}`. If Twitter doesn't temporarily respond, as
 @swissspidy suggested, then the oEmbed shouldn't be updated (if it was
 already correct generated before) or cached at all, if broken. Or maybe
 the time for the next oEmbed caching clearance — which @helen mentioned
 above — should be very, very low when the remote's response is broken.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32553#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform