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]: filter tool - multiple filters for the same layer but not combine them #5366

Open
1 task done
josemvm opened this issue Feb 5, 2025 · 1 comment
Open
1 task done
Labels

Comments

@josemvm
Copy link
Collaborator

josemvm commented Feb 5, 2025

What is the bug? (in English)

it's possible to define multiple filters for the same layer but not combine them, like filter1 AND filter2:

Image

Steps to reproduce the issue

try to define multiple filters for the same layer and pick some options

Versions, safeguards, check summary etc

Versions :

  • Lizmap Web Client : 3.8.4 - commit be354fc be354fcbc
  • Lizmap plugin : 4.4.6
  • QGIS Desktop : 3.34.14
  • QGIS Server : 3.34.14
  • Py-QGIS-Server : not used
  • QGIS Server plugin atlasprint : 3.4.1
  • QGIS Server plugin lizmap_server : 2.12.0
  • QGIS Server plugin wfsOutputExtension : 1.8.2
List of Lizmap Web Client modules :
* multiauth : 1.2.2
List of safeguards :
* Mode : normal
* Allow parent folder : no
* Prevent other drive : no
* Prevent PG service : no
* Prevent PG Auth DB : no
* Force PG user&pass : no
* Prevent ECW : no

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 22

Browsers

Firefox

Browsers version

134.0.2

Relevant log output

@josemvm josemvm added the bug label Feb 5, 2025
@sudhanshu112233shukla
Copy link

Hi, I'd like to work on this issue. I see that multiple filters for the same layer are not being combined correctly. Could you provide more details on the expected filtering behavior? Should the filters be combined using AND/OR logic, or is there another approach preferred? Also, any guidance on the relevant files or functions handling the filter logic would be appreciated. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants