<div dir="ltr">Hello Kyle,<br><br>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.<br><br><GoogleScript><a href="https://maps.google.com/maps/api/js?key=KEYHERE&v=3.49">https://maps.google.com/maps/api/js?key=KEYHERE&v=3.49</a></GoogleScript><br><br><div>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.</div><div><br></div><div>I'm interested to see if anyone else has encountered this and if they have figured out a solution.<br></div><br>David</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 24, 2023 at 1:25 PM Kyle Parker <<a href="mailto:kparker@aesi-consulting.com">kparker@aesi-consulting.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="font:10pt Segoe UI"><div id="m_7639216721019973240GroupWiseSection_1674582371000_kparker@aesi-consulting.com_F7A59F5002B60000BE671F001F009300_"><div>Hello all mapguide-users,</div><div><br></div><div>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. </div><div><br></div><div><GoogleScript>//<a href="http://maps.google.com/maps/api/js?key=KEYHERE&" target="_blank">maps.google.com/maps/api/js?key=KEYHERE&</a>;<font style="background-color:rgb(255,255,0)">v=3.49</font>&sensor=true</GoogleScript></div><div><br></div><div><br></div><div>The base map appears to work fine after dismissing the pop-up. </div><div><br></div><div><img alt="" src="cid:185e57f6bad71be20ae1" hspace="0" border="0" align="bottom"></div><div><br></div><div>Our webserver is running IIS, and we have added *.<a href="http://google.com" target="_blank">google.com</a> 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.</div><div><br></div><div>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! </div><div><br></div><div>Kyle Parker</div><div>GDMS<br></div><br><span style="font-size:10pt;display:inline-block">
<p>
<font size="2" face="Arial">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.</font>
</p>
</span></div></div>
_______________________________________________<br>
mapguide-users mailing list<br>
<a href="mailto:mapguide-users@lists.osgeo.org" target="_blank">mapguide-users@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapguide-users" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapguide-users</a><br>
</blockquote></div>