New builds of Fusion to support new Bing Maps
(too old to reply)
Jackie Ng
2017-06-29 16:00:21 UTC
Raw Message
Hi All,

On June 30th 2017, Microsoft will pull the plug on the v6/v7 Bing Maps
controls and APIs


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

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


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

- 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.
2018-02-07 13:37:45 UTC
Raw Message
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

I don't know if these errors will disappear when Bing maps are added but it
shouldn't throw an error without them.


Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html