Hi Lisa, Google slipped in something in their Maps API that broke how it is used in OpenLayers. There are fixes for this in the upstream github repo that I'm porting back to 2.6-trunk branches of Fusion.
https://trac.osgeo.org/fusion/ticket/639 As for API key requirements, I don't know much about this. If a key or client ID is required, you should be able to tack on the ?key=YOUR_API_KEY or ?client=YOUR_GME_CLIENT_ID to the end of the maps API URL in the GoogleScript section of the ApplicationDefinition document. If this is a common requirement, I can add fields in the Fusion editor to set these values and update the GoogleScript URL accordingly. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/MGOS-3-0-and-Google-Maps-Layer-Issue-Not-Loading-tp5261648p5261698.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
