Steven Zahm@ Erik
This is not really an issue with Connections… Google now requires an API key in order to access it Maps API. They’ve been transitioning to this requirement over the past year or so.
Here’s a link to a tutorial on how to create the required API keys:
Hope this helps!
ps. I am presently working on adding a multi-service provider backend for Connections. The goal will to allow you as an end user to choose your maps provider. I plan on adding support for Google Maps, Bing Maps, Open Street Maps and Yandex Maps. Since all services require an API key and will charge for usage I figure it’ll be a good idea to allow you as a user to decide which provider you would like to use.
The first update to include these backend changes should land by the end of the week. You as an end user should not notice any functional difference … that will come in future updates.
This will also require updates to the templates. This should be a relatively minor update. Basically if no API key exists for any of the providers, no map will be displayed.