PHP Fatal Error | Drupal\Core\Entity\Query\QueryException: Entity queries must explicitly set whether the query should be access checked or not

Issue fixed.

keshav.k → made their first commit to this issue’s fork.

Reviewed and tested patch.
It is working good. Created MR for easy merge

The MR seems to be merged, but the status was not changed to fixed, so just updating the status.

Changing the status back to RTBC, so maintainers can give credit.

+1 RTBC

jp_sc → changed the visibility of the branch 3362224-php-fatal-error to hidden.

jp_sc → changed the visibility of the branch 3362224-php-fatal-error to active.

Same issue seems to appear in recently_read_cron() in recently_read.module.

I have found another Drupal 10 compatibility issue with the code which results in a PHP error during testing.

I have issued another merge request to resolve the issue. I have tested and can confirm this resolves the PHP fatal error when running cron.

I have added my fix to a new issue and created a merge request here: https://www.drupal.org/project/recently_read/issues/3407065#comment-1535... 🐛 PHP Fatal Error | Cron execution Entity queries must explicitly set whether the query should be access checked or not Needs review

Hello,

When using this module on Drupal 10, it throws a QueryException because entity queries in both recently_read.module and RecentlyReadService.php do not explicitly define whether to check for access permissions.

This patch adds ->accessCheck(TRUE) to all affected entity queries:

• recently_read_cron() in recently_read.module
• getRecords() method in RecentlyReadService.php

This is required since Drupal 9.4+, and mandatory in Drupal 10.
This patch takes up the old patch and adds the fix to it for the getRecords() method

✅ The patch is tested and works with Composer patching.

Thanks for maintaining the module!

Best regards,