hanopcan

Hi Kris, Thanks for the reply!

As I mentioned you won’t see the issue as I have disabled the iframe lazyloading. But in case it helps here’s a page with some embedded links on for you to look at: https://www.thegreenwebfoundation.org/fellowships/gabriela-eslava-bejarano/

As I mentioned in my initial post, I had exactly the same problem when debugging the issue using a default theme with no plugins activated. I’m also the second person to report this. To save going back and forth on this, are you be able to confirm if you can replicate this issue yourself on any standard WP install? Thanks!

• This reply was modified 1 year, 4 months ago by hanopcan.

Ok noted. This is the last post I will make in this topic in case seeing this issue resolved is interested to anyone else: https://www.ads-software.com/support/topic/lazyload-in-iframe-prevents-the-links-working/

Hi support,

Hope this is ok etiquette, as I see this has been marked as resolved, but I have exactly the same behaviour on my own website. Actually I’ve had this happening for quite a while. But today is the first day I’ve looked into the problem and realised it’s to do with Smush.

If the Smush plugin is activated, I have the LazyLoad for iframes option checked, then the links on an embedded post no longer work. They are there, but clicking on them does nothing.

I also tested this with a default theme (I tried TwentyTwentyThree), with no other plugins enabled and got the same issue.

So I know the fix is to turn off the lazy loading, which I’ve done on my own site, but this feels like a potential bug rather than the expected behaviour?

Is anyone at support able to replicate the same issue?

Thanks! – Hannah

Thanks for the transparency, and also the great work on this plugin Eddy. The WordPress community massively appreciates your efforts ??

Thanks for the suggestion Kenneth. But no it’s not plugins. I should have been clear about that in my post above as I’ve tried this on a vanilla install with absolutely no plugins and still the same problem. I’m pretty sure it’s something coming from core, specifically the inline CSS I mentioned.