I’m seeing the same on back-end and front-end. The browser is showing a 403 Forbidden error on the requests to maps.googleapis.com. This seems to be due to protections related to Cross-Origin Resource Sharing (CORS).
This is my understanding – I might be wrong…
When we send a page to the browser, we tell the browser if this page includes cross-origin data. That is, as it builds the page, should the browser expect to see requests Only coming back to our server, the origin? That would include common assets like .js and .css files. Or should the browser expect requests that go out to other pages to as well. This would typically be the required in a site that renders ads and the page Must pull in content from sources other than the origin.
I believe our servers need to authorize access from our pages to specific external resources. I have tried to do this on my server and in my WP installation, but I’m new to CORS details and am not sure about how this needs to be done.
I hope this extra info helps David.
If I understand this correctly, I’ll do some research to see if I can help resolve the issue.
This was not a CORS issue. We need to Enable the Google “Maps Static API” in our Google Cloud Services.
To verify, view the page source and copy the URI for the googleapi.com into your browser address bar. You will either get a message that you need to enable billing on the Google Maps Project, or it may tell you the specific API has not been enabled.
The cost to use this specific Static API is $2/1000 requests. Non-enterprise accounts get $200/month of free credit (or more, depends on your country). So if you have nothing else hitting your Google account, you can get 100,000 free static maps per month with this plugin.
Other services have similar pricing. For example, converting between address and coordinates requires the Geocoding API at $5/1k requests.
I believe this resolves the issue for both of us.
Take-aways from this :
– Like any other for-fee component, be sure you are using this plugin in a way that the revenue exceeds expense.
– Consider putting map usage like this behind a membership wall, only exposing to logged-in users, etc.
– Configure your Google account with quotas to avoid run-away costs.
Well, in this case, I see the solution as better documentation. Made a note of that citing this. But it isn’t a bug per se, so noting this as resolved.
https://github.com/dshanske/simple-location/issues/225
<div class=”sloc-display p-location h-adr”>
