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

Created on 30 June 2023, 12 months ago

Problem/Motivation

Following a deprecation → as of Drupal 9.2, Drupal 10 enforces that entity queries must specify an accessCheck, throwing an exception otherwise. In the module's current state (along with the automated patch provided in #3296961 📌 Automated Drupal 10 compatibility fixes RTBC that makes it otherwise D10-compatible), digests fail to send because the entity queries in the module don't include them.

Steps to reproduce

Use the module on a Drupal 10 site. Run a cron job that triggers digest_cron(). An error will appear in the logs, and the digest will have failed to send.

Proposed resolution

Add accessCheck()s to any entity queries throughout the module.

Patch forthcoming.

🐛 Bug report

Status

Needs review

Version

1.0

Component

Code

Created by

🇺🇸United States KurtTrowbridge

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @KurtTrowbridge
Open in Jenkins → Open on Drupal.org →
Core: 10.0.7 + Environment: PHP 7.3 & MySQL 8
last update 12 months ago
Composer error. Unable to continue.
@kurttrowbridge opened merge request.
Status changed to Needs review 12 months ago2:57am 30 June 2023
Comment 12 months ago →
🇺🇸United States KurtTrowbridge

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024