As a solution for the issue described in The Content overview page filters out unpublished nodes when a node access module is enabled, the behavior of the "Published status or admin user" Views filter has been modified. Now, the filter becomes inactive when a node access module is enabled.
This change ensures that the node access module takes over the responsibility for access control, managing access to both published and unpublished nodes. This is necessary because the node access module is designed to handle all aspects of access control, making the additional filtering redundant and potentially conflicting.
Site builders can now see in the filter's configuration UI whether the "Published status or admin user" filter is active or inactive. If the filter is inactive, the UI will also display a list of node access modules that are enabled on the site and have caused the filter to become inactive.
The filter is active because there is no node access module is enabled on the site:
The filter is inactive because one or more node access modules are enabled on the site:
