Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Checkbox not in all Layer categories #4272

Closed
1 task done
AdiTane opened this issue Mar 6, 2024 · 3 comments
Closed
1 task done

[Bug]: Checkbox not in all Layer categories #4272

AdiTane opened this issue Mar 6, 2024 · 3 comments

Comments

@AdiTane
Copy link

AdiTane commented Mar 6, 2024

What is the bug? (in English)

After updating to Lizmap 3.7.5 I notice that the checkbox is not displayed in all the categories of the layers. It seems that only categories with less than 10 features have the checkbox. This happens in all browsers

Steps to reproduce the issue

  1. Upgrade from 3.6.8 to 3.7.5

Versions, safeguards, check summary etc

Versions :

  • Lizmap Web Client : 3.7.5
  • Lizmap plugin : 4.2.4
  • QGIS Desktop : 3.22.16
  • QGIS Server : 3.22.16
  • Py-QGIS-Server : not used
  • QGIS Server plugin atlasprint : 3.3.2
  • QGIS Server plugin lizmap_server : 2.8.4
  • QGIS Server plugin wfsOutputExtension : 1.8.0
List of safeguards :
  • Mode : safe
  • Allow parent folder : no
  • Prevent other drive : yes
  • Prevent PG service : yes
  • Prevent PG Auth DB : yes
  • Force PG user&pass : yes
  • 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 20.04.6 LTS

Browsers

Chrome

Browsers version

Chrome Version 121.0.6167.185

Relevant log output

No response

@AdiTane AdiTane added the bug label Mar 6, 2024
@Gustry
Copy link
Member

Gustry commented Mar 6, 2024

Duplicate of #4026 ?

@Gustry Gustry added the feedback label Mar 6, 2024
@AdiTane
Copy link
Author

AdiTane commented Mar 6, 2024

Duplicate of #4026 ?

You are correct but I wanted to point out since this happened also with the latest release of 3.7

@Gustry
Copy link
Member

Gustry commented Mar 6, 2024

I think you should provide your feedback and context there, so it can be centralized. Thanks

@Gustry Gustry closed this as not planned Won't fix, can't repro, duplicate, stale Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants