An other Huge issue in QGIS Server 2.18.17:
Le 01/03/2018 à 14:26, René-Luc Dhont a écrit :
Le 01/03/2018 à 12:52, Giovanni Manghi a écrit :
now that 2.18 is LTR I guess that many have also updated their QGIS
Server installation to this release. Problem is that I see a few
issues in 2.18 and would like to have gsome feedback from others.
*) slower: it seems this version is slower compared to 2.14, at least
for some specific request like WFS GetFeatures. See for example:
where in the same condition (same server, same postgis datasource of
around ~25000 polygons) 2.18 is about 30 seconds slower than 2.14.
This issue is simply due to the transformation of the geometry from
the layer CRS to the GeoJSON CRS standard: EPSG:4326
*) At some point in 2.18 development -in the print composer,
properties of a legend- the "none" value for the "map" option was
removed. This option (together with "auto update" unchecked) allowed
to do GetPrint requests where a legend always shown the same fixed
entries regardless of the layers being requested. Moreover now the
layers legend (from a GetPrint) frequently shows "?" instead of the
correct legend. Not sure if the two things are related.
It will be great to have the possibility to allow nullptr in the map
Nyall, do you have an idea how to enhance QgsComposerItemComboBox
Issue already exists: https://issues.qgis.org/issues/16899
*) Crashes on GetPrint: adding some type of elements in print
composers (like html text boxes) caused QGIS Server to crash when
doing a GetPrint *if* the *headless* server didn't had a fake xserver
installed. Now in 2.18 this happens even if QGIS Server is installed
on a Desktop OS, unless installing the fake x server. Not sure is
related but this now affects also Windows machines where a GetPrint
requests (of a layout with one of this problematic elements) make
always QGIS Server crash. This was not the case for 2.14.
The solution is probably to update the environment variable
QT_GRAPHICSSYSTEM to 'raster' has explain
https://issues.qgis.org/issues/15440 and in a lot of other project:
I'll test this solution.
QGIS-Developer mailing list
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer