Boolean field filtering does not work when no values are set

Created on 22 March 2017, over 7 years ago
Updated 10 February 2023, almost 2 years ago

Posthumously we have been required to add a boolean "hide from front end" field to our article content type as a number of articles need to be hidden from view yet still available to search engines. We have subsequently found that due to the field not having been set any combination of filtering on this field results in no articles being shown rather than just the ones which have been specifically ticked.

My thinking is that if someone was to choose "Is not equal to True" then this should only hide the fields which have been ticked whereas it is also hiding the articles which have yet to have this field set.

This to me looks to be a bug, so hoping someone can help with this?

πŸ› Bug report
Status

Closed: duplicate

Version

8.9 ⚰️

Component
ViewsΒ  β†’

Last updated about 5 hours ago

Created by

πŸ‡¬πŸ‡§United Kingdom leovw

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024