api keys added, map is gray

Same issue here, api and geocoding keys are present. map grey.

Is this plugin abandoned ? please Ian help!!

I wouldn’t say it’s abandoned, but it’s not a high priority for me right now either.

I took a look at your site the other day, but couldn’t see any clues as to what the problem might be. The plugin still works for me on other sites.

Google did recently start requiring API key restrictions (or at least complaining when they’re not present). If that were the problem, then it should have shown an error message in the browser console, though, which I didn’t see on your site.

If you want to try it, you can add restrict your API key to the “geocoding” and “maps javascript” APIs:

https://developers.google.com/maps/api-key-best-practices#restrict_apikey

It can take up 5 minutes for the changes to take effect.

If that doesn’t work, you could try temporarily disabling all your plugins to see if that fixes it, and temporarily switch to one of the default themes.

Hello thank you Ian for your reply.
– I tried from beginning restricting keys with urls, and in these two pages
https://siampl.it/agenti/ (category map with multiple placemarks)
https://siampl.it/contatti/ (single placemark)
maps were gray, and I could see for two days a RefererNotAllowedMapError. I wrote to [email protected] and they say ” The given application & Api key is not blocked from our side”, then after a while the error disappeared from console but maps were still gray.
– I tried then removing restriction and in contact page the map for once appeared, then after refresh the map shown with watermark with a reassuring in console “You have exceeded your request quota for this API.”, that’s makes sense, since I have not enabled billing yet.
But in Agents page the map was still gray, so I think it may be an issue related to category more than api key usage. Hope I gave you some hints.
Thank you for your help! ??
ps: of course restriction is a problem but is secondary and it’s google fault, not of your plugin.

• This reply was modified 5 years, 9 months ago by marcie73.
• This reply was modified 5 years, 9 months ago by marcie73.

Hello, I found something interesting, in Setting > Basic Google Maps Plecemarks the standard map had center map “Roma”, that always worked. I also tried “Rome” or “New York”, but nothing. I put latitude and longitude (41.9097306,12.2558141) and this worked and fixed the issue of gray map.
In contact map I also latitude and longitude because could not accept address.

So it might be an issue related to geolocation values.
Thank you!

Thanks Marcie

I was having exactly the same problem but putting in latitude and longitude fixed it.

Thanks from me too, Marcie. That explains why some of my maps didn’t work, while others did. I was using the default Map Center Address as a location for some maps, but overriding the center address for other maps.

The issue had been on my “look at” list, but I just checked the settings page and found an error there saying that geolocation had failed. Simply re-saving (no changes made) the settings resolved the issue, but now having the latitude and longitude I replace the location name with them and saved again. The non-working maps sprang back to life :-). I have a lot of different maps on my site, so now I’ll go through and make sure that all center addresses are in latitude and longitude format.

Proposed solution:
I had the same problem and was able to analyze and fix it the following way:
1) Open the page where you have embedded the map.
2) Open the Java-Script-Console in your browser (how to: https://developers.google.com/web/tools/chrome-devtools/console/javascript)
In the tab “console” Google provides you with a very clear error-message which problem it detected. That can be e.g. “referal not allowed” or “payment data missing” or others. Very nice: The Google-Error Message provides you with a clear url-link to a help page how to fix your specific problem. ??
-> In my case, everything was configured ok, just no payment data provided.(Which you would likely not assume necessary if quota are not reached. But Google requires it anyway…