Lizmap Web Client 3.8 RC 2 and latest monthly bugfixes

Hi,

Because of summer holidays coming, we have released our monthly bugfixes versions a little bit earlier in the month :slight_smile:

  • Lizmap Web Client 3.8.0.rc.2 - 2024-07-08 Without any critical bug report, the 3.8.0 release will before end of July.
  • Lizmap Web Client 3.7.9 - 2024-07-04
  • 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.

For translations, you can check the completion for your language on docs.3liz.org, and help on Transifex for Lizmap and Jelix library used in the backend. :world_map:

1 Like

Because of summer holiday, we have decided to postpone a little bit the release of 3.8.0.

But we have released a 3.8.0-rc.3 version in the meantime.

Please check the full changelog

We really would like to thanks you if you can test this version.

1 Like

I installed the RC3 version. At the moment all is working well. Any issues to check?

@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

1 Like

@gustry I noticed another anomalous behaviour related to loading of wps results on 3.8-rc3 that I’ve reported on the Github module’s repository.

1 Like

I have installed 3.8.0-rc.3 with the current QGIS version 3.34.9. Examples can be found here
https://cx21-8.webgis.biz/index.php

Grouped layergroups are not displayed correctly in subgroups as active/deactive according to the QGIS themes. Issue is written (https://github.com/3liz/lizmap-web-client/issues/4652)
And Google StreetView via JS does not work. I had already created an issue for this:
https://github.com/3liz/lizmap-javascript-scripts/issues/81

Otherwise it looks very good!

1 Like

@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.

sclzrc3

@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)

1 Like

Yes @wagner-it I confirm the Issue, I misunderstood the behaviour in previous reply

QGIS Setting

Schermata del 2024-07-25 11-12-23

LWC 3.8-rc3

Schermata del 2024-07-25 11-12-59

LWC 3.7.9

Schermata del 2024-07-25 11-14-57

1 Like

@Antoviscomi although in your screenshot “LWC 3.8-rc3” the PAI_2011 layergroup should actually be activated by mistake - right?

1 Like

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

true @Antoviscomi Until recently, this behavior also existed in general for the grouped layergroups. Now it only affects the subgroups.

1 Like