michael.aulia

It’s the Lazy Load Iframes settings. Go to your Media Settings, disable Lazy Load Iframes and purge the cache

Will have a look at this Kelly, thanks for the reply. I believe this is a PRO feature and not on the Free version?

Ah..yeah that was totally expected. Dang, would be fun doing this manually for hundreds of review posts ??

Thanks, looking forward to trying out your plugin!

So here are the funny things and in case someone here has the same problem:

Work Computer
– Works fine on Firefox, Chrome, Vivaldi. All browsers with extensions installed

Home Computer
– Works on Vivaldi
– Doesn’t work on Chrome (fresh install), Edge, Opera GX
The funny thing about Chrome at home…. if I use Chrome’s Private Window, it works…??

Not sure what’s happening here but if you have problems, try using Chrome Incognito window to login to your WordPress (or try a different computer??)

Don’t think it’s a plugin or theme issue, but again, I don’t know

Thanks! The weird thing is, I try again with the office computer the next day and it’s working fine. Last night at home, I already tried different browsers with the same results.

I’ll wait after work to test if it’s still causing problems at home computer – maybe a cache on the ISP side? Not sure

Ah, I see. Yeah I did some Googling around and it looks like it’s a bug though has happened for months without a fix. But thanks for the update!

For now we should disable Apple Pay until hopefully a fix one day. Thanks for your reply!

Hi Stuart,
Many thanks for your reply! I only had a chance to try it just now.

Looks like if I change the “Free Shipping” on the top, Apple Pay now grabs that correctly. HOWEVER!

It looks like Apple Pay will always auto-select the first/top shipping method no matter what you select. So for example if I have:
[-] Standard shipping
[-] Express shipping

When a customer selects Express shipping and use Apple Pay, the Apple Pay confirmation payment pop-up on the phone will always auto-select Standard shipping (whatever the first shipping option is)

It’s funny that this issue has been around since February 2018 but it hasn’t been looked at/fixed up til now?

Does everyone here disable Apple Pay too (which I’m doing at the moment) or have you guys found a workaround?

This works! Thanks much for the help!

I’ve actually already submitted a ticket before I posted here (Ticket #220150). Someone just replied (I assume it’s you?) I guess we’ll continue there via emails/ticketing system. Thanks!

Hi,

Sure, I’m happy to help out as much as I can. Let me know what you’d like me to do? I may not be able to leave the cache disabled for a long time though (in the past, I got Internal 500 error within the hour or two whenever my caching was not working and my old hosting suspended account :))

But if it’s only for a bit so you can get some debug log or testing things, I’m happy to help, just let me know!

The site, cravingtech.com, is live now with the workaround if you want to investigate the headers, etc

Ohh is it under Advanced->Check Advanced Cache->Include advance_cache.php? I unticked it and the plugin now works! Have also tested using the browser’s developer tools and see a cache hit header

From the description on the option, it doesn’t seem to be important (unless if I stupidly install another caching plugin), so I’m happy with the solution. Any possibility on why this option might fail on the server? (to see if I can fix it if it’s a permission issue of some sort)

Thanks for the prompt reply!

Hi Don,
That works like a treat, thanks for the quick and easy solution!

It’s cool, we all learn new things each day and you can’t possibly know and cover everything out there ?? Cheers

I’m using the plug-in too and here’s how you can fix it for now. Beware though that this workaround will be overwritten when there is an update to the plug-in in the future.

Edit this file under the plugins\ folder on your WordPress blog:
amazon-product-in-a-post-plugin\inc\amazon-product-in-a-post-get-product.php

Find every noshade=”noshade” occurences and remove the noshade=”noshade” part (keeping the <hr /> in tact. Save the file and re-test your AMP posts/pages to double check.

Working fine here on 2.7 RC1 @my blog

and thank goodness that you are apologizing. Donncha is a great guy and like others said, it’s free and he spends all day and night to give us this wonderful plug-in and here we are complaining! ??

Back to topic, err yeah it’s working fine here (but I’m still 0.8.4 though, not the latest one, which is 0.8.6)