Currently "view own unpublished content" access is only checked and grants access a user to its own content when `->access('view')` is called on an already loaded node object by node id or via loadMultiple().
However, when node ids are collected by an entity query or database query with node_access tag in place, unpublished contents by the current user are not returned.
E.g.:
$result = \Drupal::entityQuery('node')
->accessCheck(TRUE)
->execute();
This leads to interesting and long term problematic workarounds both in Core and in contrib space:
\Drupal\node\Plugin\views\filter\Status Views filter should not exist, but it does and therefore
🐛
The content overview Views view filters out unpublished content
Active
also exists\Drupal\node\Plugin\EntityReferenceSelection\NodeSelection entity reference selection plugin should grant access to (own) unpublished content without additional workarounds, see
🐛
User can't reference unpublished content even when they have access to it
Needs work
Active
11.0 🔥
Enhances developer experience.
When Node ids are collected via an entity query or database query with node_access tag in place, unpublished contents by the (current) user are not returned.
Could you help me replicate this? I'm finding precisely the opposite in 🐛 QueryInterface::accessCheck does nothing Active