Visitor’s Country not working

Hi @tanias,

I hope you are keeping well and thank you for reaching out to us.

Since the website URL where we can replicate the issue wasn’t provided, I couldn’t investigate the problem further. We’ve observed similar issues reported when the website domain is proxied using Cloudflare. Could you confirm if your website uses Cloudflare?

Additionally, could you please share an export of the form so that we can examine the issue more closely?

We look forward to hearing back from you and help you resolve the issue as soon as possible.

Kind Regards,
Nebu John

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.

Hi @tanias

To be honest, I’m not much familiar with QUIC.cloud options (even though I am using LiteSpeed – but without it) but you may be right about it – basically, any cache at any level may interfere with such things.

But I’m also wondering about two other things:

1. if rules are correctly set; this may sound a bit “lame” but it’s quite easy to set rules that are a bit “contradictory” or “conflicting”, I’ve seen it too many times to rule it out already.

Would you mind exporting the popup (the one that originally didn’t work) and sharing it with us? Or at least sharing screenshots of its visiblity rules as they are set?

2. and what about CloudFlare that my colleague asked about? Are you using CloudFlare for this site at all?

Kind regards,
Adam

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 @tanias,

Thanks for sharing a screenshot regarding this. I gave a quick test in my system and I could only get the popup loading with USA region.

This behavior suggests a possible conflict, potentially related to cache settings as you have indicated.

Do you have a staging site? To further diagnose the issue, if you have a staging site available, could you kindly test the functionality with the cache disabled and observe the behaviour? This would help determine if the cache setting is influencing the issue at hand.

Furthermore, if the problem persists even after disabling the cache, I recommend deactivating all plugins except for Hustle to check if the issue might be related to a plugin conflict. This step is crucial for isolating the cause of the observed behavior.

The above steps will help in ruling out what might be causing such behaviour.

Please do let us know how that goes, so that we can check further if needed.

Looking forward to your response.

Kind Regards,

Nithin

Hi @tanias,

Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to open a new thread if you have new queries.

Kind Regards
Nithin