Problem/Motivation

If I add a boolean field to a nodetype with previously existing nodes that havent't been saved since I had added the new boolean, I expect that the boolean value ist not 1 (TRUE) .
In fact there is absolutely no fields value at all on these nodes as long as the nodes are not updated.

I consider this as a bug that the views filter "field_boolean" ist not 1 (TRUE) is not working. In other words I expect these nodes to be listet in the view with this filter but they aren't listet as long as they are not updated again.

Steps to reproduce

~1. Save some nodes.
~2. Build a view with a list of these nodes and make sure that the nodes are listet in the view.
~3. add a new 'field_boolean' to the nodetype
~4. add the filter 'field_boolean' is not 1 (TRUE) to this view
~5. Experience that the nodes aren't listet anymore in this view
~6. update the nodes
~7. Experience that the nodes are listet now in this view

Proposed resolution

I don't know if this is a field system bug or a views bug but it is strange. If anyone has a more appropriate title for this issue, please let me know …

Comments

marco.b created an issue. See original summary.

marco.b’s picture

Issue summary: View changes

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.1.10 (June 4, 2021) and Drupal 9.2.10 (November 24, 2021) were the last bugfix releases of those minor version series. Drupal 9 bug reports should be targeted for the 9.3.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

marco.b’s picture

Issue summary: View changes
cilefen’s picture

Status: Active » Postponed (maintainer needs more info)
Related issues: +#2862828: Boolean field filtering does not work when no values are set

This looks like a duplicate.

marco.b’s picture

Yes, that's right, it is indeed a duplicate. So I close it here.

marco.b’s picture