Entity queries must explicitly set whether the query should be access checked or not

Fixes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies. Also, 10.2 is in security mode now.

That line of code has been in Drupal since #2785449: It's too easy to write entity queries with access checks that must not have them → . What changed? Which query is this, and from which module?

Also, accessCheck is a property, not a function.

In Drupal core 10.3.10, I encountered the same error. I’ve created the following patch, which resolved the issue successfully:

In Drupal core 10.3.10, I encountered the same error. I’ve created the following patch, which resolved the issue successfully:

Correcting what I wrote in #4: yes there is an accessCheck function QueryBase in addition to the property. However, it is protected so directly referencing it in Query should work.

@vijayshiva134 We would need a stack trace from you to better understand what happened.