If you have recently ported a WordPress site from another server or from a staging site to a production site and the address lookup in Store Locator Plus is failing — you may have an incomplete port. There are a few simple ways to tell that the WordPress configuration is incorrect. This video for our WordPress folks will help you determine if your “ported configuration” is the culprit.
Thankfully our MySLP users never have to deal with this sort of issue — but for our WordPress users that may have an incorrectly ported site, watch this:
Google does not openly advertise the fact that they have different location data for different users. However there is good anecdotal evidence an hearsay that Google Maps API returning inaccurate results may be by design.
The evidence is most prevalent in the geocoding of locations. The latitude and longitude Google assigns to different addresses is not “set in stone”. It is an interesting anomaly given the fact that places on earth should not move with regard to their latitude & longitude outside of plate tectonics.
The team at Store Locator Plus® has long held a theory that Google intentionally subverts accurate location data; quite likely to gain competitive advantage for their own products and services.
WordPress 4.9.9 as well as 5.0.1 and ALL the “security patch releases” back to 3.7 now have a new CSV file management bug. Any CSV file that is uploaded is rejected by WordPress due to a security violation.
The Quick Fix
Add this to your wp-config.php file:
Yes, this will effectively disable all those cool new “security features” in the latest release of WordPress but it also will get your CSV imports working again. Just remember to take this out when WordPress 4.9.10 (or 5.0.2) comes out — assuming they deem this new “security feature” a bug and patch it accordingly.