Latest update not working

One of the two updates in the new version is disabling Iframely if the scope isn’t a single page/post (don’t ask us why WordPress haven’t updated the changelog).

Can it be that your posts are out of post scope?

In PHP terms, get_the_ID() should return a value as otherwise WP doesn’t store embeds in cache and it overloads our servers.

Also, WP team closed couple tasks in 4.6.1, one of which was re how they detect if URL needs to be run through embed logic. I believe they now only process links inside <p> paragraphs. Can you try that if you’ve updated WP as well? I see your new post doesn’t have <p></p> around <a…>

I’m not entirely sure I understand but I created the posts in the same manner that I have before the Iframely update. I installed a plugin to show me the post ID in the admin and it is assigning it an ID so I’m not sure what you mean if they are out of the post scope?

OK, then Iframely should work if WP embeds work. Try it with the <p> perhaps?

Ok I tried with the paragraph and it still didn’t work. I reinstalled version 0.2.0 and updated the non working post and it works correctly now.

Can you try us figure out what exactly doesn’t work for you? Can you pull 0.3.0 and remove just this change set and see if it starts working for you?

Ok I updated to 0.3.0 and removed that section of the code. I created this new post : https://www.rebeccascomics.com/index.php/2016/09/11/alien-nebula-watercolor-and-ink/ and it appears to be working correctly. Let me know if there is anything else I can test for you. Thanks!

Thanks! It means wp doesn’t see its post ID yet. Let us think what could be going wrong here and back to you with suggestions. In the meantime, I see you have one of the Google Analytics plugins – if you could let us know which one it is, we’d try it with that plugin too.

I’m using Google Analytics by MonsterInsights https://www.monsterinsights.com/pricing/#utm_source=wordpress&utm_medium=plugin&utm_campaign=wpgaplugin&utm_content=v504
Let me know if I can provide any other information. Thanks, James

We ended up rolling back postID logic in v0.3.1. Ping us if the issue still persists. Thank you for helping us debug it earlier this week!