Tom has posted a patch and windows binaries which fix the problems with Firefox 3 and Mapguide. http://trac.osgeo.org/mapguide/ticket/378
I had done some of the digging for issue and I found that the only difference was that Firefox 3 appends "; charset=UTF-8 to the Content-Type http header.
FF3: Content-Type: application/x-www-form-urlencoded; charset=UTF-8
FF2: Content-Type: application/x-www-form-urlencoded
I have tested this on XP with the binaries Tom posted and it worked :)
To test the patch on linux, download the patch into your MgDev/Oem MgDev/Web/src source directory.
wget http://trac.osgeo.org/mapguide/attachment/ticket/378/FF3Fix.patch?format=raw
mv FF3Fix.patch\?format\=raw FF3Fix.patch
Apply the patch using patch -p 0 < FF3Fix.patch
You then need to rebuild the Oem stuff using ./build_oem.sh in the MgDev directory.
You then need to run make install ( you need to run the make install for the server as it enables the Mapguide support in Apache conf) otherwise, you will get the ELF binary of mapagent.fcgi returned.
Remember to either backup and restore serverconfig.ini or recreate any alias mappings as serverconfig.ini will be recreated.
In addition, don't forget to install the new fusion 1.0.6 release
The basic viewer is working for me on both XP and Linux now with FF 3 but there seems to be an issue with fusion.. hmmmm..
Fusion is working in IE & Mapguide Studio but something seems to be failing with Firefox
Steve Dang has also checked in some fixes on the trunk for Rasters, whilst primarily targeted at the Autodesk.Raster provider, it's meant to improve the GDAL stability as well.
http://trac.osgeo.org/mapguide/ticket/556
http://trac.osgeo.org/mapguide/ticket/610
Once there has been some more testing, I think there's a good case for a 2.0.2 point release as there are some good fixes in the tree since 2.0.1
Update: The fusion problem has magiscally disappeared and the patch should be applied to MgDev/Web/src not MgDev/Oem
3 comments:
Should the linux patch file be downloaded to "MgDev/Web/src" instead? That's what seemed to work for me.
Thanks for all the tips, they are very helpful! -SD
firefox 3 bug exists in 1.2.x also. Will there be a patch available for 1.2.x? Thanks
The patch should work fine with 1.20, you are going to need to compile your own version tho....
For the effort involved, your much better off upgrading to Mapguide 2.0.1, it's much more stable
Post a Comment