Bug report #10625
addDrawingOrder changed in 2.4 breaks LayerDrawingOrder logic
Status: | Closed | ||
---|---|---|---|
Priority: | Severe/Regression | ||
Assignee: | Marco Hugentobler | ||
Category: | QGIS Server | ||
Affected QGIS version: | 2.2.0 | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 19028 |
Description
I'm investingating why QWC is giving me problems with QGIS Server 2.4.
I've spot a difference between QGIS 2.2 and the master code which seems to cause problems during the GetProjectSettings response parsing.
In previous versions of QGIS Server addDrawingOrder worked for project layers [1] while for embedded layers we had addDrawingOrderEmbeddedGroup [2].
Now we have only addDrawingOrder which seems to work only for embedded projects.
The result is that, without emdedded layers, the <LayerDrawingOrder> element will always be empty.
This seems to cause some problems on the QWC side. In fact now QWC works only with GetCapabilities, while it worked both with GetCapabilities and GetProjectSettings before.
[1] https://github.com/qgis/QGIS/blob/release-2_2/src/mapserver/qgsprojectparser.cpp#L3644
[2] https://github.com/qgis/QGIS/blob/release-2_2/src/mapserver/qgsprojectparser.cpp#L4067
[3] https://github.com/qgis/QGIS/blob/master/src/mapserver/qgswmsprojectparser.cpp#L674
History
#1 Updated by Giovanni Allegri over 10 years ago
I suggest this pull request https://github.com/qgis/QGIS/pull/1462
#2 Updated by Marco Hugentobler over 10 years ago
- Status changed from Open to Closed
Fixed in changeset c05e342ab1fc09a1f9f09cf76840862dc3e038cf.