Our Google Maps functionality has mysteriously broken. Our map displays now show "This page can't load Google Maps correctly." over the map.
We didn't change anything. It just stopped working and I first noticed it yesterday. It was working perfectly before.
I've gone into our Google account and updated the credit card on file with the billing and that did not solve it. I've tried a bunch of things found on various webpages that talk about this error, but nothing has worked.
When I checked the API key in our Toolset Settings area, it was different from what was showing on the Google account. So I have no idea how it was working fine before. I changed the API key to the correct one and saved it in Toolset settings and it still doesn't work.
I added a restriction to limit access to Website as follows:
hidden link
I saw that on another support page (not Toolset support) that suggested to do that but it didn't work either. I'm losing my mind on this. It was working fine before and I changed nothing that I know of to break it. I have no idea why this is happening or how to get it working again. Any assistance will be greatly appreciated.
Warning
The script element that loads the API has no API key. Please make sure you include a valid API key as a key parameter. You can generate a new API key in the Cloud Console.
To get an API key, click the button below to get started.
Get Started
If you are loading Maps JavaScript API from the deprecated v2 path, you will get the NoApiKeys warning, even if you specified the key parameter. Please check the v2 to v3 upgrade guide and migrate your application to Maps JavaScript API v3.
I tried adding a 2nd key with no restrictions and that didn't work, so I eliminated that. But now when I test the first key in Toolset | Settings, I'm seeing this:
REQUEST_DENIED - API keys with referer restrictions cannot be used with this API.
So now I'm removing the restrictions from the first key.
Testing again and it now says:
Google API seems to be configured properly.
But it still hasn't stopped the original error.
I've tried deleting the site cache and browser cache. No effect.
Hello. Thank you for contacting the Toolset support.
Can you please share admin access details and let me check whats going wrong with your setup.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
This is the live site, but you can change the map configuration as needed because it isn't working. Let me know if you need access to the Google Console as well. I'm guessing the problem likely lies there. The account we're using there is only for this mapping, so it is likely I'd be able to get approval to give you access there if needed.
OK, I'm seeing that I forgot to add the API key to the settings for that plugin. I've done that now and it is working. I have no idea why that key being missing from that plugin would impact the display of the map using Toolset Maps, but obviously there was an issue there. Thanks for the find. I'm glad it turned out to be easier than figuring out something wrong on the Google admin side.
Wow, this also solved a long-standing problem I had previously given up on. We had a ticket for that here:
That problem has been fixed now as well. If you can, add the following post to the end of that other ticket. I tried to add it but it said the topic was closed. If anyone else encounters that specific problem, looking for other mapping plugins will likely solve that for them as well. Here's what I tried to add to that ticket:
---------------------------------------------------------------------------------------------
It turns out the problem here was we have another Google Maps plugin installed on our site and I hadn't entered the API key in the settings for that plugin. We hadn't gotten to testing the functionality provided by this plugin yet.
We encountered another problem in the following support ticket:
Minesh determined that the other plugin was the problem and my fix to provide the API key there also fixed this problem that I had long since given up on solving. I didn't think that the other plugin would cause a problem with the use of your plugin and frankly, the existence of that plugin on our site was an "Out of sight out of mind" thing until Minesh found it. I installed it as a part of an effort to find all good mapping options for mapping routes, but I haven't tested everything with it yet. I should have disabled the plugin, but just neglected to do so. Anyway that's the fix in case anyone else encounters this problem.
Also note that this API key has been missing the whole time from that plugin's settings. I have no idea why it just now became a problem for Toolset Maps to display the maps. It's been working all this time that way and just now changed.
