tanias

Hi @wpmudev-support8, just using LiteSpeed, not Cloudflare.

Conditions are as follows:

• Only these countries: USA
• Source of arrival: A search engine
• Visitor’s device: Desktop only
• Only these posts: post 1, post 2, post 3

Link to screenshot can be found here: https://drive.google.com/file/d/1zcEivKwXPbI-JzVFen9tH-_ssGAtmQ20/view?usp=sharing

Thanks.

Hi @wpmudevsupport14,

Thanks for your quick response.

Our server-level cache is LiteSpeed, and we’re using the LiteSpeed plugin on WordPress, with QUIC.cloud CDN enabled.

I’ve further tested the popup, making some adjustments per the recommendations provided by LiteSpeed here:?Exclude a plugin from LS Cache.

• I added wordpress-popup to Tuning > JS Excludes and Tuning – CSS > CSS Excludes, however this didn’t fix the issue.
• I then disabled Load CSS Asynchronously – this seemed to fix the issue for Chrome but not Safari. Popups were still showing on Safari.
• Likewise (and I think this is only on Safari), the Visitor’s Country condition seems to work only for the last post in the ‘Only these posts’ list.

Considering the above, I tried setting separate visibility rules for each post in the one popup. This didn’t work either.

Also, I noticed when I separated the visibility rules that the input field for Visitor’s Country (under the first visibility rule) changed to a different format.

Because of this, I thought maybe the popup isn’t picking up the Visitor’s Country properly. So I created separate popups for the posts to see what happens. Country visibility seems to be working for Chrome. But I’m not sure at this stage re Safari – I still need to test whether the LiteSpeed Load CSS Asynchronously option is causing popups not to work properly on this browser.

FYI, while testing these separate popups, both popups appeared on one of the posts that was listed in the original popup, although I removed it from that popup and added it to the second one. This is even though I had purged the LiteSpeed cache via the WordPress plugin and waited a while before publishing the popups again.

I’m thinking this may be due to not waiting long enough when the cache is purged via the WordPress plugin? And/or not also purging the cache via QUIC.cloud, specifically CSS, JS and possibly Other Static Assets?

Your insights would be greatly appreciated.

Thanks for your quick reply Adam. I’m well – I hope you’re also well.

You’re absolutely right. It wasn’t the Hustle plugin but a CSS optimisation setting. I’ve now resolved the issue. And am happy to say that we can keep using the Hustle plugin.

Thank you again for your help.