[Raymond Dunegan]

Ok, I figged it out.

Get a google server key

make sure it is associated with your website in the google console.

ENABLE the javascript api as well as the geocode api, do this in the google console.

paste this into /wp-content/themes/yourtheme/header.php before the /head> tag
<script async defer src=”https://maps.googleapis.com/maps/api/js?key=YOURSERVERKEY&callback=initMap&#8221;
type=”text/javascript”></script>

REFRESH AND IT WORKS.

YOU CAN take a short cut by opening developer tools java console and click on the dev.google link at the error, scroll down and you can click on the link to get your snippet with your api, if logged in, just make sure itls the right one.

[Steven Zahm]

@ Brett

re: I’m no coding wizz so if its a simple update I’d be happy to test – it’ll be sometime before my site is live anyhow

Great! I just sent it. Let me know if you do not receive it.

[Steven Zahm]

@ Raymond

re: Are you saying that the map showing then throwing keyerror is a bug needing fixed?

No, this is definitely not a bug. Google is locking down their maps API. For years it was available to use without key. As of June 22 all new sites are required to use a key. By Oct 12 all old sites will require a key. I suspect this is step one in a longer term plan to start charging for access to this API. Time will tell.

I kind of suspected this day was coming after noticing this warning in the browser console which is why I started adding support for the browser and server keys. I had fully implemented the server key completely, just not the browser key. The beta I just sent has the browser key fully implemented so it should resolve this issue.

re: paste this into /wp-content/themes/yourtheme/header.php before the /head> tag…

I strongly recommend undoing this change.

I just sent you a beta copy of the next release of Connections which has fully implemented the browser and server keys for the Google Maps API.

You can set them on the Connections : Settings admin page under the Advanced tab. With the beta installed and the keys added, you should not longer receive the Google Maps error.

Let me know.

[ayomide]

can i get a copy of the code and instructions on how to implement it

[ayomide]

This reply has been marked as private.

[Raymond Dunegan]

Beta didn’t work without the head tag

• This reply was modified 6 years, 7 months ago by Raymond Dunegan.

[Steven Zahm]

@ Raymond

re: Beta didn’t work without the head tag

The reason seems to be that the Google Map API was inadvertently disabled. Perhap during your testing??? Navigate to the Connections : Settings admin page and click the Advanced tab. Scroll to the bottom and enable the Google Maps API option in the Compatibility section. After you do, remove the header tag.

[Steven Zahm]

@ ayomide

Sure thing. I’m send it now.

Here’s the link to the instructions on how to get a key.

https://developers.google.com/maps/documentation/javascript/get-api-key

When in the Google Console. You’ll have to enable the Maps JavaScript API and the Maps Geocoding API and maybe the Maps Geolocation API (not certain about the last yet).

Make sure to create both a server key and a browser key and enter both of the keys on the Connections : Settings admin page under the Advanced tab.

Here’s a little YouTube video I found that should help if you watch it. It’s for the Places API, but the process will be the same.

https://youtu.be/_SBdYW-E5kc

Hope that helps!

[Brett Stephenson]

Re:Great! I just sent it. Let me know if you do not receive it.

Hi Steve

nothing arrived – I checked spam box and not there either

I did get the other email you sent “RE forum – create searchable field” though

[Steven Zahm]

@ Brett

Sorry to hear you did not receive it perhaps I mistyped the email address or something… I just sent it again.

[Author]

Posts