Filter Logic is not consistently using AND about atrocore HOT 2 CLOSED

Just an update on this as the guys have just been caught out again with this. This impacts any negative searches using the same field twice. An easier example to understand would be colour. If we add a positive filter where we add two colours, red and blue, using 'or' is needed. Select where colour is red or colour is blue. If we wanted to reverse that set, and use is not red or blue, the filter logic needs to be AND, so colour is not red AND colour is not blue. Using OR in this case, the red case will return all blues and the blue case will return all reds.

With the ability to use negative searches, the filter needs to allow selection of logic for all search criteria and not use default logic where a field is used twice.

from atrocore.

This is currently not an issue, it is a functional limitation. We will definitely address it someday in the future, but not in the nearest future. I was thinking about living the filter configuration like it is, which should generate a "query", which can be further edited by a more "advanced" user.

from atrocore.