Wordpress LScache Plugin: Geolocation plugin conflict
Last Updated on: Wed, 15 Apr 2026 00:00:02 hi, after some experimentation I discovered the cause of a problem I was having when using a plugin called WP Conversion Boost PPCKit and the geolocation service provided by ipinfodb.com a problem that Id never encountered before ? Not logged in, the geolocation returned Ann Arbor (Michigan) ? Incorrect! Logged in, the geolocation returned returned my current location ? Correct! it was only after I realized that one of the hosting companys servers (A2 Hosting) was located in Ann Arbor that the lightbulb went off over my head? Caching! turned off LiteSpeed Cache and all was well but as Id rather keep using it, Ive got to ask ? has anything changed in the plugin? are there any backend settings that address this particular situation? i.e.- the situation being that geolocation only works when one is logged into the site would prefer to avoid messing with htaccess if at all possible thanks UPDATE: After turning the LiteSpeed Cache plugin onn/off a few times the geolocation is (for now?) correct. Now the question is ? was it this plugin or caching in general? why did happen? why did it start? can I exclude the one page it happened on from being cached? The Truth is out there? Hi, when you use LiteSpeed Cache with GeoLocation , you will need to follow this guide to tell server that you want to serve differently over different country otherwise it will just save whoever-comes-first like US user visited first, then it generates US page and serve for all , if UK user visited first, then it generates UK page and serve for all ?etc Best regards, Hi, Im going to mark this topic Resolved , due to lack of activity. If you still need help, please feel free to re-open it. When re-open it, please also change the topic status to not solved Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference