-
Posts
-
Hi,
I have multiple Enfold websites using a new Google API key.
I have set up billing correctly, as one of the sites that showed the developer notice is now working fine.
However, another site is still showing the developer notice.
I have checked (and double checked) the URL defined in the API is correct.
Enfold validates the API correctly.
I have purged the server cache, disabled plugins, and reset the performance settings in Enfold.I contacted Google and their reply is: “Upon checking the site, I can see that you the API key did not make it through. I understand that you’ve already setup the billing account, API key and also added it to your theme. But it looks like there’s an issue with your theme which caused the failure to add the API key to your map (or you accidentally missed a step while adding it).
In normal implementation of API key in Google Maps, we just add the API key directly in the HTML script tag, just like what you can see in this documentation: https://developers.google.com/maps/documentation/javascript/get-api-key#step-2-add-the-api-key-to-your-application
However, your it looks like your theme/plugin has a non-programmer-friendly user interface where you enter your API key, which is then supposed to add the key to the script tag. But if it failed to add the API key, you will get the degraded map (the darkened map with watermarks).”
Please can you take a look at the site: Details below in private. The site with the problem is one of my oldest Enfold sites.
Hey Heathcliffe,
How can a site have the same API key? 1 API key should go to 1 domain, can u test that please?
Best regards,
BasilisHi @Basilis
This is the way the API key works. You create a key and then add restricted domains.
This is how I have always done it and it’s always worked fine.
This is the way Google has designed the API key to work. Otherwise, I would have many API keys to manage and (with the billing) I would also have to set individual quotas so I can keep under the free credit limits.
If I don’t set restricted domains, then the key can be open to abuse.Google says the website is using the key-less script tag: https://maps.google.com/maps/api/js?ver=4.4.31
and it should be updated to include the API key parameter by adding `key=YOUR_API_KEY” to the script.Not sure if this helps?
Hi,
I fixed it. You use the events calendar plugin which also loads the google map api. You need to set the api key for for the events calendar plugin too, otherwise it “blocks” the Enfold api. I added the url to the events calendar api settings page to the private content field.
Best regards,
PeterMany thanks for this. It was driving me nuts, completely nuts.
Have you contacted TEC to get them to fix the issue?H.
- You must be logged in to reply to this topic.