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.

1 Like

Hello there…I’m still using LWC 3.8.2, but last day I received the mail about the official release of the 3.9 version and with the annotation that the py-qgis-server from this version on is mandatory instead of optional…i used Docker to start the first tests before upgrading, but I’m stuck in the part that the LWC recognizes my py-qgis-server (http://:8080/ows)

At server info I get this:

Modules

No module installed

QGIS Server

QGIS Server is correctly installed and returns the expected response for OGC requests.

We cannot get the details about your QGIS Server installation (version, plugins, etc.).

You must check that the following steps are done :

  1. QGIS Server is above or equal to 3.28
  2. The Lizmap QGIS server plugin is installed on the server with a version above or equal to 2.10.1
  3. The URL to reach QGIS server is correct in your administration panel
  4. The URL to reach the Lizmap API on QGIS Server is correct in your administration panel, if you use Py-QGIS-Server
  5. Your Lizmap Web Client logs does not contain any warnings about reaching QGIS server
  6. The environment variable about the Lizmap server plugin described in the documentation link below is correctly set in your configuration
  7. Your QGIS server logs does not contain any warnings about the Lizmap server plugin (at QGIS server startup and when loading this webpage). You might need to increase debug level.

On the container:
root@8c0c88e43ab2:/# qgis-plugin-manager list
QGIS_PLUGINPATH set to /usr/lib/qgis/plugins
QGIS version : 3.40.7
List all plugins in the directory set by environment variable : /usr/lib/qgis/plugins


| Folder :arrow_down: | Name | Version | Flags | QGIS min | QGIS max | Author | Folder rights | Action :warning: |

|atlasprint |atlasprint |3.4.3 |Server |3.28 | |3Liz |root : 0o755 | |
|lizmap_server|Lizmap server|2.13.1 |Server |3.28 |3.99 |3Liz |root : 0o755 | |

I think I’m missing the path for the projects, but I have the same settings as in my QGIS server running on Ubuntu 24.04:

Can anyone give me a hint?

You can check the documentation :

In your post :

The URL to reach the Lizmap API on QGIS Server is correct in your administration panel, if you use Py-QGIS-Server

With Py-QGIS-Server, the Lizmap plugin API URL must be provided. (We can indeed improved this part now in 3.9). Did you follow the checklist ?

You haven’t tell us which docker images you are using for QGIS Server.

Hi there.

I’m using a custom image based on Ubuntu 24.04 that uses the .zip file (https://github.com/3liz/lizmap-web-client/releases/download/3.8.11/lizmap-web-client-3.8.11.zip)from Github, I have several customizations like dfs mounts and corporate proxys configurations. I then deploy this image into containers to 3 docker hosts balanced by a nginx server. The docker containers can run an internal qgis-server as a failsafe, in case my qgis-server running also on a separate Ubuntu server 24.04 for some reason fails or is on scheduled maintenance. On this qgis-server I replicate the mounting points of the containers, so that the project paths are the same.

On this separate qgis-server, I installed the qgis-plugin-manager and installed the plugins (Lizmap server, atlasprint and wfsOutputExtension , and everything runs ok.

I think I might have a problem with this point:

  1. The URL to reach the Lizmap API on QGIS Server is correct in your administration panel, if you use Py-QGIS-Server
    Being my server running on 10.1.1.130:8080, should the URL be http://10.1.1.130:8080/ows ? What more can I troubleshoot?

Kind regards,
NMS

Sorry, I meant the QGIS Server image.

Being my server running on 10.1.1.130:8080, should the URL be http://10.1.1.130:8080/ows ? What more can I troubleshoot?

No, it’s a different URL than the one for QGIS OGC services. Look at the tooltip if I’m correct.

In the documentation, look at lizmap_api and lizmapPluginAPIURL

I’m trying to start from scratch:

From this page: GitHub - 3liz/py-qgis-server: QGIS embbeded WMS/WFS/WCS asynchronous scalable http server

I start a docker container running the command:

docker run -p 8080:8080
-v /mnt/repo:/mnt/repo
-e QGSRV_SERVER_WORKERS=2
-e QGSRV_LOGGING_LEVEL=DEBUG
-e QGSRV_CACHE_ROOTDIR=/mnt/repo
-e QGSRV_CACHE_SIZE=10
-e QGIS_SERVER_PARALLEL_RENDERING=true
-e SERVER_PLUGINPATH=/usr/lib/qgis/plugins
-e QGIS_SERVER_LIZMAP_REVEAL_SETTINGS=TRUE
3liz/qgis-map-server:3.40

Most of documentation runs the qgis server on port 7200, this one runs on port 8080…inside de cli of the container I see the qgisserver is installed, but not the qgis-plugin-manager…I then install the qgis-plugin-manager and install the ā€˜Lizmap server’, atlasprint and wfsOutputExtension…

From the CLI of the container, when I run
curl http://localhost:8080/ows/

I get this (that is correct, no further parameters passed)

<?xml version="1.0" encoding="UTF-8"?>

Project file error. For OWS services: please provide a SERVICE and a MAP parameter pointing to a valid QGIS project file

But when I run
curl http://localhost:8080/lizmap/ , I get this

{ā€œerrorā€: {ā€œmessageā€: ā€œInvalid resource path.ā€}, ā€œhttpcodeā€: 404, ā€œstatusā€: ā€œerrorā€}

What am I missing???

Kind regards,
NMS

What is your configuration file ?

[api.enabled]
lizmap_api=yes

Or via environment variable API_ENABLED_LIZMAP ? Configuration Settings — py-qgis-server 1.8 documentation

Please check this page : Py-QGIS-Server

That the problem…running the container from the command, what configuration file is being used? Or do I have to create one? Isn’t the container ready to use? Or do I need to configure it first?

No, the configuration file related to your instance and it’s possible to use 3liz/qgis-map-server:3.40 without Lizmap. QGIS Server can be used alone, without Lizmap.

Either use environment variables, or create the configuration file and mount it into the container.

https://docs.3liz.org/py-qgis-server/intro.html#cmdoption-c