This is to address the issues some of you may already have seen appear with your Google maps, and specifically Map 2 stack.
The powers that be have been changing their api’s again. This time it’s Google with their Google Maps.
Yesterday they changed that, and access to the maps now requires a per domain user api key.
Before we all panic. There is a temporary exception in place.
Google have made it so until the end of the year, and website that has previously ran a Google map using the version 3 api (Map 2 stack does), will be granted access to the maps without a key.
So all your existing deployments of the map will continue to function as normal in the interim.
They will however not display as normal within RW preview, as RW preview for all intents and purposes is seen by Google as a new domain.
They will still work as expected when you re-publish any pages containing a map in the interim though.
So with the immediate panic out of the way, what are we going to do about it.
Well, from our end it’s pretty straightforward. We will be issuing an update to the stack, that will include one extra input field in the settings, for you to add your own Google maps api key for the domain.
The extra work has been placed with you guys I am afraid.
You will need to log into Google to obtain an api key for any new website you want to deploy a map in.
EDIT: UPDATE NOW ISSUED
I have created a step by step to get your map API keys on the Map 2 stacks demo page inside the FAQ section : https://www.doobox.co.uk/stacks_store/demos/map2.html