meyerlor

Updating Lizmap did not change with 3.9 (so it's the same as going from 3.8.8 to 3.8.9 for example) and if you really want, you can use 3.9 without py-qgis-server...

This upgrade documentation is valid since 3.5: https://docs.lizmap.com/current/en/install/upgrade.html

A little workaround i use: rename the themes, as they are taken into account by alphabetical order. 1. Start 2. Your other theme 3. Next theme 4. etc

Uhm, will it be implemented in LWC as a setting admins can edit? Or do i need to set it on all my LWC servers manually?

in the .cfg of the project i find only two occurences of `export_enabled` : ``` "locateByLayer": {}, "attributeLayers": { "Flurst\u00fccke": { "layerId": "Flurst_cke_F_2ccf4491_d5d6_43fd_8391_538ffe5a888e", "primaryKey": "fid", "hiddenFields": "fid,Hauptnutzung,Aufnahmedatum,VertreterID,Vorg\u00e4ngerflurst\u00fccke,index1,Flurst\u00fcckskennzeichen,FLSTKZ,H\u00f6he,GeoidH\u00f6he,_x_etrs,_area,kennung", "export_enabled": true, "pivot":...

Just for the record:  This is the button which is there in LWC 3.8.3 and missing in 3.9.0

So i played a bit detective, iteratively upgrading an old 3.8.3 project - with the most recent 3.8.11 version, it is still working & the button is there. On 3.9.0-beta.2...

With the latest 3.9.2 this regression is still not adressed, and 3.8.12 is the version to stick with if that functionallity is crucial (which it is for some of my...

@rldhont i will send you an email with an url and the login data. This screenshot is from the project/LWC instance i'm sharing with you, under 3.8.12 (only K_Bauwerke is...

@rldhont thanks for your mail and giving insight into this issue - seems more then legit to be able to control more granular who can export data! What i don't...