We had a meeting with Gordon Luckett to discuss this issue and he provided insight into what's causing it and a workaround solution. The Fusion template relies on OpenLayers v2 and with Google Maps API v3.50, something has changed that prevents it from working with OpenLayers v2, resulting in Fusion errors.
As a workaround solution, if you remove both the GoogleScript tag, from the XML, and live Google base maps in Maestro, the Fusion errors no longer occur. You can replace the live Google base maps with the tiled versions, which allows continuity for the end user. It was also suggested to consider pivoting to using the React viewer instead of Fusion, which is something I hope to look into in the future. Hope this helps, David On Tue, Jan 24, 2023 at 3:41 PM David Bowen <dbowen...@gmail.com> wrote: > Hello Kyle, > > We're encountering the same issue as you; if we change the version to > 3.51, MapGuide throws the Fusion Error, but works fine with version 3.49. > We're currently running MapGuide 3.1.1, on Apache, consuming Google's > basemaps, geocoder and street view. > > <GoogleScript>https://maps.google.com/maps/api/js?key=KEYHERE&v=3.49 > </GoogleScript> > > I've been working to add CSPs to the response headers for the pages that > utilize the Google resources but haven't had any luck. I'm not seeing a CSP > error in the console log at any point before or after making modifications > so I'm not sure if the CSPs are being added correctly. > > I'm interested to see if anyone else has encountered this and if they have > figured out a solution. > > David > > On Tue, Jan 24, 2023 at 1:25 PM Kyle Parker <kpar...@aesi-consulting.com> > wrote: > >> Hello all mapguide-users, >> >> We are running MapGuide v3.1.1.9378 and have run into an issue using >> Google Maps API to bring in Google base maps. It looks like an issue with a >> deprecated call in the Maps API with the latest version. We have found that >> if you use the previous version of 3.49 in your Layout's GoogleScript >> instead of the current 3.51, the error no longer shows up. Version 3.49 >> will no longer be available after May 2023. >> >> <GoogleScript>//maps.google.com/maps/api/js?key=KEYHERE&v=3.49 >> &sensor=true</GoogleScript> >> >> >> The base map appears to work fine after dismissing the pop-up. >> >> >> Our webserver is running IIS, and we have added *.google.com to the >> Content Security Policy HTTP response header, but it had no effect. We >> would like to stick with MG v3.1.1 for now if possible. >> >> I realize this is not a Google Maps help forum, however I was wondering >> if anyone else has run into this issue, and if you have found a way to >> either fix the erroneous 'width' call or prevent the error message from >> displaying. Thank you very much for your time and any comment you can >> provide. Thanks! >> >> Kyle Parker >> GDMS >> >> Confidentiality Notice: The information contained in this message and any >> attachments may contain confidential or proprietary material and is >> intended solely for the use of the person or entity to which it is >> addressed. Any unauthorized review, use, disclosure or distribution of this >> communication is strictly prohibited. If you have received this >> communication in error, please immediately notify the sender by reply >> e-mail and destroy all copies of this communication and any attachments. >> _______________________________________________ >> mapguide-users mailing list >> mapguide-users@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/mapguide-users >> >
_______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
