Thanks Tecca
Thanks for bringing this to our notice. The JSON being blocked is the 3rd party service we use to get the visitor location.
We have inbuilt redundancy in the script to ensure that if one service fails, we have a backup – so while you see the warning, we hope that the link is still redirecting to the right URL based on visitor location since the secondary location service should kick in.
In your test, with the https protocol, did you notice that the URL was not redirected correctly? If yes, will love to see an example.
Having said that, we agree – the script should not be throwing a warning even though it does not impact the functionality. We will address this issue in subsequent release. Thanks for bringing it up!
Thread Starter
Tecca
(@tecca)
Great, thanks for the reply! You’re right, the plugin works regardless, so there’s no issues there.
I’ve marked this as resolved, thank you for your time.
Thanks Tecca.. appreciate the confirmation.
Regards,
R
PS: if you can, please consider writing a review so that others can discover this plugin. Helps us keep motivated! 🙂