Re: [mapguide-users] New builds of Fusion to support new Bing Maps
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 mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] New builds of Fusion to support new Bing Maps
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 new fusion code which kept throwing errors but different ones than described I think. This turned out to be caused by having layers or folders in the map that were set to not show in the legend. Anyway, somewhere along the line the original error has disappeared. I hope somehow this helps you. On Tue., Nov. 6, 2018, 8:35 p.m. 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 > 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
Re: [mapguide-users] New builds of Fusion to support new Bing Maps
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 mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] New builds of Fusion to support new Bing Maps
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 currently using a Bing layer as we are in the process of getting our API key (enterprise). I don't know if these errors will disappear when Bing maps are added but it shouldn't throw an error without them. Ideas? -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html ___ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
[mapguide-users] New builds of Fusion to support new Bing Maps
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 the current iteration of Bing Maps and the changes backported, however no accessible release of Fusion has been made that has these changes incorporated. So I've decided to put out some new builds of Fusion that has these changes (and many months of fixes and minor enhancements). You can download these builds for your respective version of MGOS below: 2.6: http://download.osgeo.org/mapguide/fusion/fusion-2.6.2.zip 3.0: http://download.osgeo.org/mapguide/fusion/fusion-3.0.1.zip 3.1: http://download.osgeo.org/mapguide/fusion/fusion-3.1.1.zip To install, unzip the contents to the www directory of your MGOS install. Rename or remove the existing fusion directory before unzipping. You can also check out the respective SVN changelogs to see what else has changed: 2.6: https://trac.osgeo.org/fusion/log/branches/fusion-mg26 3.0: https://trac.osgeo.org/fusion/log/branches/fusion-mg30 3.1: https://trac.osgeo.org/fusion/log/branches/fusion-mg31 If you want to continue to use Bing Maps in Fusion, you will now have to apply for a new API key in the bing maps portal https://www.bingmapsportal.com With this key, put it into the top-level extension property named BingMapKey in your Application Definition document and point it to your respective template in this build to use the current version of Bing Maps. If you use the hybrid base layer type, you will have to change the type to AerialsWithLabels. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/New-builds-of-Fusion-to-support-new-Bing-Maps-tp5326055.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
