Lizmap Web Client 3.6.14 - 2024-07-04 This branch has reached its end of life, for “normal” bugfix. Only bugfix related to security is done now.
QGIS 3.34.9 will be released later this week by the QGIS community. We advice you to upgrade, as some bugfix were done, for server side as well recently.
@gustry I’ve just installed it and seems to works well, I just found an issue in layer order on map, with pgrouting module results (that I reported in the pgrouting-module’s github repository), and I also noticed that wps module it’s not configurable in 3.8-rc3 because of requires maximum version <= 3.7.x, I’ll test it more extensively as time goes by
@wagner-it the grouped and sub-grouped work fine for me on 3.8rc-3 on a project created on 3.36.2 QGIS Server version, as you can see in the follow screencast, @gustry there was a QGIS sub-version issues concerning Groups managment (if I rember right) so I suggest you to try to upgrade QGIS version and test the groups with a new project version.
@Antoviscomi Thanks for the feedback.
I think we are talking about different things. In Lizmap the activation/deactivation works fine.
I mean the attention to the activated layergroups based on the QGIS themes.
Example: I have a group Water in QGIS, this is saved as not activated via the QGIS map theme. Below this there is a grouped layergroup Pipes. This is saved in the QGIS project as active in the theme. However, it is not displayed because the group above it is deactivated.
In Lizmap, the activated grouped layergroup is incorrectly displayed as active below the deactivated group. See screenshots in Issue 4652 (link above)
No, @wagner-it because of PAI_2011 is the supergroup, that was unactive in QGIS, the sub-group Rischio_Frana, and the Layer ‘psec_cetraro’, was active in QGIS but no more in LWC, so there isn’t an exact match between what the user sets and what LWC returns