[Bug]: Changes in the attribute form are not active in Lizmap input masks.

[guenterw]

What is the bug? (in English)

If you change values in the attribute form retrospectively, these changes will not be used for the input mask in Lizmap.
In the example of the alias, this is not critical, but if, for example, the value mapping is changed (or set up) retrospectively, this will confuse the values in the database.

Steps to reproduce the issue

Example: the alias of the field ‘wald’ is changed from ‘Wald Bezeichnung’ to ‘Wald’:

This is correctly taken into account in the input masks in QGIS:

In Lizmap, also in the pop-up:

But the old alias value is still in the Lizmap input mask:

The strange thing is that this string ‘Wald Bezeichnung’ (or parts of it) cannot be found in either the .qgs or the .cfg.
Then I deleted all caches. Browser cache, project cache (in the backend) and finally restarted the server. The name is still there.

As a workaround, I saved the layer as a layer definition file, deleted it in QGIS, closed the project, and then reinserted the qlr.
Disadvantage: for Lizmap, this is a new data set and the information in the plugin has to be re-entered.

Versions, safeguards, check summary etc

Versions :

• Lizmap Web Client : 3.9.2 - commit fd848d5 fd848d56b
• Lizmap plugin : 4.5.3
• QGIS Desktop : 3.40.10
• QGIS Server : 3.40.10
• Py-QGIS-Server : 1.9.6
• QGIS Server plugin atlasprint : 3.4.3
• QGIS Server plugin lizmap_server : 2.13.2
• QGIS Server plugin wfsOutputExtension : 1.8.3

List of Lizmap Web Client modules :

* altiProfil : 0.5.10 * altiProfilAdmin : 0.5.10

List of safeguards :

* Mode : normal
* Allow parent folder : yes
* Number of parent : 2 folder(s)
* Prevent other drive : no
* Prevent PG service : no
* Prevent PG Auth DB : no
* Force PG user&pass : no
* Prevent ECW : yes

Check Lizmap plugin

• I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.

Operating system

Ubuntu 24.04 (Server)

Browsers

Chrome

Browsers version

Version 140.0.7339.128

Relevant log output

[meyerlor]

I just ran into this behaviour last week (the unchangeable alias) last week, too. I thought it to be on my side, but it seems to be a regression.

[meyerlor]

Uhhm, this is frustriatingly broken. I'm trying for 2 hours now to get a boolean field (checkbox) working again - the attribute form shows the checkbox, but it completely ignores what is filled in, the value always stays NULL.

Nothing helped, not deleting and bringing back the layer (with a new name), not uploading the whole project under a different name, not adding a new field.. i'm out of my depth.

Edit: reverted to 3.9.0, here no problems...

Edit 2: sorry, with 3.9.0 the problem of the not reflected changes to the attribute form still exist - the reverting itself made the attribute form "update". So the dirty workaround for me is now, make a version downgrade, then upgrade and then just don't touch the attribute form anymore.

[mdouchin]

Could you please export the QML for the problematic layer (with no authentication data inside, but normally the QML only export the layer properties, not the datasource.)

[meyerlor]

Voila!

I tried to change the Alias of the field "Zeige_Fläche" from "Mit Fläche Beschriften" to "Beschrifte_Fläche"

Flächen_neu.qml.txt