Seems there is a number of new people having issues with the Store Locator Plus® address lookup feature due to a failed REST API request. With Store Locator Plus 5 all address lookups are routed back through the WordPress site via the REST API in order to protect Google API keys.
If your site is running WordPress from a subdirectory you may run into issues if your web server is not configured to properly handle REST API routing. Especially if the site is using “pretty permalinks”, any Permalink setting under WordPress Settings | Permalinks other than “plain”.
The problem is that most of the Codex articles on the subject of doing a “WordPress in it’s own directory” installs came out well before the REST API existed. Most, dare we say ALL, have not been updated since and completely ignore the corner case of a WordPress subdirectory install with Permalinks enabled.
Thankfully our MySLP users don’t have to deal with this sort of thing; but if you are using the self-managed WordPress plugins, read on.
You’ve found the telltale sign that your restricted browser API key has been set in the Store Locator Plus geocoding key field. Coming soon with the WordPress Store Locator Plus 5.0.4 release is a new message that will show in your map results telling you what error codes Google is sending back.
There are a couple of correct ways to setup your Google API keys for Store Locator Plus
If you are in North America you may be asking where is Toronto, Ontario. Depending whom you ask, the answer can be slightly different. It turns out that asking Google Maps Canada yields a different answer than if you pose the same question via Google Maps API.
We’ve touched on this disparity in a prior post about Google Maps returning inaccurate results. Today we’ll discuss a specific example for Toronto, Ontario.
And if you are wondering — our vote is that Toronto, Ontario is at