As covered in the release notes, the CentOS build of MapGuide has a change in the xerces library used by any part of MapGuide that works with XML content.
The xerces library for the CentOS build is now built with the iconv transcoder instead of the default GNU iconv transcoder. This was done to avoid cryptic "could not load a transcoding service" errors that were occuring on mgserver startup in my developement and clean-install CentOS VMs.
The Ubuntu build still uses xerces built against the default GNU iconv transcoder and does not throw this xerces error.
I do not know what side-effects there are as a result of this change of transcoders. If you encounter any issues with your CentOS install of 2.6 beta 1 in the areas of:
* XML content processing
* Interactions with resources containing non-english content
* Resource Service APIs
* Site/Session repositories
I noticed an issue with Fusion and HttpTiles using AIMS 2015.
It doesn't work anymore, I just get a blank map without any tiles.
The problem also occurs with MapGuide Open Source 2.6 Beta 1.
Meanwhile I found out that the cause of the problem are changes in OpenLayers.js (MapGuide.js).
The problem doesn't occur, if I use the original OpenLayers.js (Version 2.13.1) from openlayers.org.
What are the differences?
In OpenLayers.js which comes with AIMS 2015 / MapGuide Open Source 2.6 Beta 1 the function calculateGridLayout
as part of OpenLayers/Layer/Grid.js is overwritten in section MapGuide.js.
The Fusion that comes with MGOS 2.6 Beta 1 uses OpenLayers 2.13.1. However, we also keep track of any custom modifications to any files in the OL source.
MapGuide.js was one of them and it turned out that we no longer have to keep a modified copy for our own OpenLayers.js. Basically, it's already been fixed due to this ticket: http://trac.osgeo.org/fusion/ticket/614
Thanks for the info Jackie.
I wasn't aware of the changes and improvements you made since publishing MapGuide Open Source 2.6 Beta 1.
Yesterday I checked the newest files on Fusion trunk and updated this buggy version of Fusion which comes with AIMS 2015 (sorry Autodesk...).
Looks very good until now (e. g. no more php error messages with selection.php) and from an administration standpoint,
the upgrades to Apache 2.4 and PHP 5.5 and the TraceKit integration (which is not a part of AIMS) are really great improvements.
An issue that still exist (in our environment):
We have several maps with two base layer groups (e. g. the first base layer is a a town map the second one an aerial photo).
The first base layer group is set to visible (=initially visible in map), the second one to invisible.
After opening the map, both base layer groups are visible and the second one (aerial photo) overlaps the first one (town map).
The legend tree looks ok, the first base layer group has been turned on, the second one has been turned off.
In a former version of Fusion (I don't know the exact version) this issue has been patched.
The patch has been applied to MapGuide.js with following lines of code at the end of function initLoadMapResponse: