Lizmap Web Client 3.8 was released

We are pleased to announce the release of Lizmap Web Client 3.8.

You can find the full changelog on the GitHub release. :slightly_smiling_face:

The visual changelog will come later in September, (after the QGIS User conference in Slovakia next week, let’s meet there if you are there !).

Quick overview :

  • Ask a single tile for all layers. This is a major option in this version. It might greatly change the rendering behavior, requesting a single tile to QGIS Server, instead of one per layer toggled in the project. Thanks to Faunalia for these contributions. :+1:
  • Improve snapping functionalities, to be able to choose the layer from Lizmap Web Client directly
  • The HTML content on the landing page can be different according to if the user is connected or not.
  • For HTML and Javascript developers, more WEB components are available, like lizmap-features-table see PR description or JavaScript API.

353739777-a60ba8f6-972c-44e2-975a-fcf30cb0e9d0

To benefit of all features, you need the latest plugin version, which was just released now, version 4.3.22. This latest version allows you to have multiple user&groups in the field for attribute filtering.

For your information, the Lizmap Web Client version 3.6 is now EOL (End Of Life). Only critical security bug-fixes will be applied to this branch.

Please test and give some feedbacks :rocket:

Regards,
:lizard:

3 Likes

For your information, we have released version 3.8.2 today :wink:

It’s fixing bugs which have been reported. In the administration panel, there is now a table showing the list of LWC modules installed on the instance, or links to provide some helps about QGIS Server plugins.

It has also a better handling of additional user JavaScript scripts. There is now a button to reload the map without broken JS.

Happy testing

1 Like

We have now added the visual changelog for 3.8 :+1:

We clearly encourage you to migrate to 3.8, it makes 3.7 better according to some feedback we got. (when we zoom for instance, due to the migration to OpenLayers 10)

It makes now the 3.6 release retired, it means there won’t be any updates on the release. Except if there is a very critical issue on this release.