Couldn't reproduce it. Need LSA or help reproducing it :)

Thanks

For encrypted attributes, filtergin requires encrypting values for the query.
Only did for single choice and multiple choice.

PR: https://github.com/LimeSurvey/LimeSurvey/pull/2635

For the other attribute types or forms of comparison, it is very difficult (if imposible) to query encrypted values.
Maybe, if an attribute is encrypted and is not single choice or multiple choice, we don't allow filtering?

Same will happen when browsing responses.

For the other attribute types or forms of comparison, it is very difficult (if imposible) to query encrypted values.

Why ? We don't use compare ? A link to the search ?

Maybe, if an attribute is encrypted and is not single choice or multiple choice, we don't allow filtering?

yes , need this option if previous one is not set.

For the other attribute types or forms of comparison, it is very difficult (if imposible) to query encrypted values.

Why ? We don't use compare ? A link to the search ?

For open text, If you need to query with wildcards it may not be possible. You may need to query by exact match... even spaces could bother in the query.
For numbers, if you need to query greater or lower than, porbably is not possible.

@ollehar what shall we do here?

For open text, If you need to query with wildcards it may not be possible. You may need to query by exact match... even spaces could bother in the query.

Oh, yes … i'm silly

For numbers, if you need to query greater or lower than, porbably is not possible.

Same, i'm silly … you can remove the probably

For encrypted attributes, filtergin requires encrypting values for the query.
Only did for single choice and multiple choice.

Tickets created for other type of questions.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=33987

Fixed in Release 5.4.9+221101