I’m sure everyone is aware of the changes to Google maps starting on June 11th which mean embedded keyless maps and map APIs without billing details added to the Google maps platform will no longer display properly after June the 11th.
I’ve signed up for a new API key, added billing details and restricted the key to only work on certain domains.
I’ve added my new key to several sites built in Freeway Pro 5.5 and although the maps are working OK for now I’m getting 2 or 4 javascript API errors related to the map control showing up in the developer tools in Safari and in the console in Chrome.
I’ve added my new API to all my sites and all maps are currently working as expected. I have the same problem with sites I’ve built in Adobe Muse where their standard maps widget has no input field for an API key. They have promised a fix which is a surprise as they killed off Muse a while back.
The errors mention upgrading my application from V2 to V3 but given that Freeway is a way off from a new version coming out, I wondered if my maps will still work after June the 11th and if anyone else knows a workaround for now?
Thanks for the heads up on this. Yet something else to keep up on. I wonder if google is heading for a 100% paid model for maps?
–
David Owen
Creative Design | Print Production | Web Design & Strategy | Domains & Web Hosting
On 5 Jun 2018, at 22:04, Louis email@hidden wrote:
Hi,
I’m sure everyone is aware of the changes to Google maps starting on June 11th which mean embedded keyless maps and map APIs without billing details added to the Google maps platform will no longer display properly after June the 11th.
I’ve signed up for a new API key, added billing details and restricted the key to only work on certain domains.
I’ve added my new key to several sites built in Freeway Pro 5.5 and although the maps are working OK for now I’m getting 2 or 4 javascript API errors related to the map control showing up in the developer tools in Safari and in the console in Chrome.
I’ve added my new API to all my sites and all maps are currently working as expected. I have the same problem with sites I’ve built in Adobe Muse where their standard maps widget has no input field for an API key. They have promised a fix which is a surprise as they killed off Muse a while back.
The errors mention upgrading my application from V2 to V3 but given that Freeway is a way off from a new version coming out, I wondered if my maps will still work after June the 11th and if anyone else knows a workaround for now?
I’m sure everyone is aware of the changes to Google maps starting on June 11th which mean embedded keyless maps and map APIs without billing details added to the Google maps platform will no longer display properly after June the 11th.
I’ve signed up for a new API key, added billing details and restricted the key to only work on certain domains.
I’ve added my new key to several sites built in Freeway Pro 5.5 and although the maps are working OK for now I’m getting 2 or 4 javascript API errors related to the map control showing up in the developer tools in Safari and in the console in Chrome.
I’ve added my new API to all my sites and all maps are currently working as expected. I have the same problem with sites I’ve built in Adobe Muse where their standard maps widget has no input field for an API key. They have promised a fix which is a surprise as they killed off Muse a while back.
The errors mention upgrading my application from V2 to V3 but given that Freeway is a way off from a new version coming out, I wondered if my maps will still work after June the 11th and if anyone else knows a workaround for now?
