Twitter/Instagram embeds “breaking”

This is a PRIVATE forum for verified users only, to view all replies/answers, you must be logged in!

Status: not resolved
Viewing 10 reply threads
  • Author
    Posts
    • #18200

      rfischmann
      Member

      Hey guys,

      I’ve had this issue for quite a while, but haven’t yet figured out what’s wrong.

      If you go into this post [https://macmagazine.uol.com.br/post/2020/03/31/case-para-o-iphone-9-sugere-lancamento-antes-do-dia-5-de-abril/], for example, you’ll see there are one URL for Instagram and one for Twitter where they were supposed to show the full embeds for both.

      The thing is, when we published the post the embeds were working just fine. Also, if I hop into the post through WordPress’ editor, they also show up fine.

      However, it seems that after a few days these Twitter/Instagram embeds just “break” and, instead of fully loading, we only see their URL. It happens all the time.

      And BTW, I’ve never seen this issue occur with YouTube’s embeds. They always work.

      Any help/ideas? Cheers.

    • #18202

      Jacob
      Staff

      Hey there, You must be logged in to view this reply!

      Login | Register | Forgot Password?

    • #18204

      rfischmann
      Member

      I’ve tried that, Jacob. I’ve edited something in the post, but nothing changed on the front-end. On the back-end, they show up just fine.

      Is there any way to manually clear that oEmbed cache, to see if that’s the issue here?

    • #18206

      rfischmann
      Member

      So I did some digging and found out how to clear the oEmbed cache per post accessing my MySQL database. Sure enough, both on that example were set to {{unknown}}: https://d.pr/i/ptNvuM

      After deleting all _oembed lines from that post, both embeds are now loading up just fine.

      The questions now are: why is it breaking after a while? Why doesn’t WordPress try to regenerate those broken oEmbed caches? Is there any way to force WordPress to rebuild broken oEmbed caches?

    • #18207

      rfischmann
      Member

      I’ve found this very long post about it, don’t know if it’s helpful or not: https://seo-gold.com/understanding-wordpress-oembed-and-unknown-postmeta-entries/

    • #18208

      rfischmann
      Member

      Also found this ticket in WordPress Trac from years ago, exactly same issue: https://core.trac.wordpress.org/ticket/32553

    • #18211

      Jacob
      Staff

      Hey there, You must be logged in to view this reply!

      Login | Register | Forgot Password?

    • #18213

      rfischmann
      Member

      Hi Jacob, thanks for the link! So, let me see if I understood.

      If I follow “Example #1” from the link, every time any of our posts is loaded, the oEmbed cache will be regenerated. Correct? That doesn’t sound like a good idea, otherwise it doesn’t make sense to have a cache at all.

      Do you think we could add a check to the code so that, if the oEmbed cache contains {{unknown}}, then it should regenerate it? That would be more than enough to solve this issue, I believe.

    • #18217

      Jacob
      Staff

      Hey there, You must be logged in to view this reply!

      Login | Register | Forgot Password?

    • #18218

      rfischmann
      Member

      I don’t think that’s the case, Jacob, otherwise the embeds wouldn’t load inside WordPress’ editor (Gutenberg) either, and they always do.

      We’re hosted in Liquid Web — yes, on a cloud dedicated server.

    • #18430

      rfischmann
      Member

      This of course is still an issue for me. Can you help, Jacob?

Viewing 10 reply threads
  • You must be logged in to reply to this topic.

This is a PRIVATE forum for verified users only, to view all replies/answers, you must be logged in!

© Copyright 2020 by wpthms.com. All Rights Reserved.