Regression! Hide Attributes in popup doesn't works in LWC 3.6.10 and 3.7.5 and Lizmap Plugin about lizmap-web-client HOT 13 CLOSED

Your screenshots are "Popup", not "Attribute table". It's two different tools. This is not the way to hide fields in a popup (depending of the kind of popup you use, CF documentation)

from lizmap-web-client.

@Antoviscomi i think that the popup is based on WMS and the attribute table is based on WFS from field options on QGIS Desktop

from lizmap-web-client.

Your screenshots are "Popup", not "Attribute table". It's two different tools.

@Gustry I have not checked this on LMWC 3.7.* but on previous versions if a field is unpublished from WMS capabilities (layer properties > fields > configuration > dot not expose via WMS) it surely does not show in the automatic popup in LMWC. If it does not work the same way in LMWC I would consider it really a regression, but as I said I haven't tested it in the latest version.

This is not the way to hide fields in a popup

What would be the right way then?

from lizmap-web-client.

@gioman Look at @Antoviscomi description ;-)

@Gustry I have not checked this on LMWC 3.7.* but on previous versions if a field is unpublished from WMS capabilities (layer properties > fields > configuration > dot not expose via WMS) it surely does not show in the automatic popup in LMWC.

This 100% correct, it's correct behavior.

The "Attribute table" tool in Lizmap is not linked to the popup tool.

• Popup → WMS service
• Attribute table → WFS service

In "Automatic" popup, fields are coming straight from QGIS Server. If fields are not exposed on QGIS server, then LWC (which is downstream) will not have fields as well.

I just tried, it works for me, with "automatic" popup and hiding fields from WMS service, with QGIS Desktop and server 3.34 :

field_tab_1 is missing from the popup.

QGIS Desktop : 3.36.0
QGIS Server : 3.36.0

@Antoviscomi Does it occurs since you have updated to QGIS Desktop and server 3.36 ?

You said 3.6.10 is impacted as well, but the number of backport on the 3.6 branch has been very low now, and QGIS 3.36 is very recent.

from lizmap-web-client.

When did you update to :

• QGIS server 3.36 ?
• QGIS desktop 3.36 ?
• LWC 3.6.10 ?
• LWC 3.7.5 ?

Was it working in between these upgrades ?

You can make the query straight to QGIS server to check if these fields are exposed from QGIS server ?

LWC is an overlay to QGIS Server. If QGIS server is hiding fields (which must happen if the flag is set, then LWC can't have data and can't display it) . If LWC can display these hidden fields from QGIS Server, it means these fields are not hidden from QGIS Server.

from lizmap-web-client.

@Gustry @gioman @josemvm after systemctl restart apache2 all works fine now in both versions

from lizmap-web-client.

@Gustry I use the Automatic popup that reads values from Attributes Table, as configured in Lizmap plugin, at least in all previous versions of LWC it seems to me (I remember so)

from lizmap-web-client.

@Gustry consider to reopen because

This is the fields configuration

from lizmap-web-client.

@Antoviscomi i think that the popup is based on WMS and the attribute table is based on WFS from field options on QGIS Desktop

In the above screenshot are the configurations where both WMS and WFS are checked to hide

from lizmap-web-client.

What would be the right way then?

Yes, It's the right way but, No @josemvm @gioman doesn't works anymore, I omitted the last screenshot for mistake in the initial bug topic

from lizmap-web-client.

@gioman I don't know is it related to 3.36 Qgis update (it's possible) but in previous configurations (as above descripted) the fields I checked to hide were really hidded now I'm not able to hide them anymore

from lizmap-web-client.

You said 3.6.10 is impacted as well, but the number of backport on the 3.6 branch has been very low now, and QGIS 3.36 is very recent.

@gioman yes, I confirm this impact for both 3.6.10 and 3.7.5 LWC versions, so I think you're right, there is something wrong on Qgis server 3.36 I suppose

from lizmap-web-client.

When did you update to :

• QGIS server 3.36 ?
• QGIS desktop 3.36 ?
• LWC 3.6.10 ?
• LWC 3.7.5 ?

Was it working in between these upgrades ?

You can make the query straight to QGIS server to check if these fields are exposed from QGIS server ?

LWC is an overlay to QGIS Server. If QGIS server is hiding fields (which must happen if the flag is set, then LWC can't have data and can't display it) . If LWC can display these hidden fields from QGIS Server, it means these fields are not hidden from QGIS Server.

@Gustry was only something wrong in session (apparently) because of after restart Qgis server all works as expected

from lizmap-web-client.