Re: [mapguide-users] New builds of Fusion to support new Bing Maps

2018-11-13 Thread GordonL
Thanks, it is still reporting those errors, but the real issue was a SSL setting in the browser (TLS 3) that was causing the issue. -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html ___ mapguide-users mailing list

Re: [mapguide-users] New builds of Fusion to support new Bing Maps

2018-11-08 Thread Mike Herel
Hi Gordon, I am not seeing these errors any more but I don't remember what fixed it. I wasn't clear in my explanation but I think the error was Bing related. Since that time we have gotten an API key. That may have fixed it. Also, it could be related to another issue we found. I put back the

Re: [mapguide-users] New builds of Fusion to support new Bing Maps

2018-11-06 Thread GordonL
Did you still get these errors? I am getting them in Chrome right now. I think there must be a IIS setting change or a Chrome update.. -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html ___ mapguide-users mailing list

Re: [mapguide-users] New builds of Fusion to support new Bing Maps

2018-02-07 Thread MHerel
I have installed MGOS 3.1 and have applied the new Fusion code but I get 2 errors on the page load. fusionSF.js:1696 Refused to set unsafe header "Content-length" FusionSF.js:1697 Refused to set unsafe header "Connection" I do not get these errors with the original Fusion code. I am not

[mapguide-users] New builds of Fusion to support new Bing Maps

2017-06-29 Thread Jackie Ng
Hi All, On June 30th 2017, Microsoft will pull the plug on the v6/v7 Bing Maps controls and APIs https://blogs.bing.com/maps/June-2016/Bing-Maps-V8-Web-Control-Released When Microsoft pulls the plug, this will break Bing Maps support currently in Fusion. Fusion has already been updated to use