Recently updated to WordPress 4.9.9 or 5.0.1 and your CSV file imports for Store Locator Plus® stopped working? You can thank yet another “WordPress security feature” — also known as “backwards compatibility break”. This “update” came with absolutely no warning to plugin developers.
This does not affect our MySLP SaaS users thanks to our fully managed software stack, so they can rest easy and continue to import locations.
The basic configuration of Google API Keys tells you to turn off ALL restrictions on the first API key you setup with Google. Turns out a lot of people have issues with configuring the keys properly and getting them put in the right place.
To make matters more complicated, some lower-end web hosting companies don’t understand security and in turn shut off critical web services that do nothing to improve security; Like disabling all communication between the web server and Google. That breaks things like the ability to Geocode locations in Store Locator Plus®.
This article is here to tell our WordPress plugin users how to properly secure their Google API keys for web hosts are configured properly.
Thankfully our MySLP SaaS service users don’t have to deal with this nonsense, a benefit of having us manage the locator software for them. MySLP users login to their MySLP account, manage locations and map settings, and when they are ready copy the “generate Embed” code and past it into any page, post, or widget on their WordPress site — no plugins needed.
If you are using My Store Locator Plus® pat yourself on the back and take an extra 5 at coffee break today. You don’t need to read this article.