Fatal error when using the "Enqueue Content" button in Drupal 10

The simple change in the MR resolved the error for me.

Patch applied and Enqueue content is working as expected.

Removing the call to accessCheck(TRUE) will still result in an error for regular Drupal entities. It’s important to note that explicitly invoking accessCheck is necessary. Refer to this source: Access checking must be explicitly specified on content entity queries →

The error in the current code arises because the code checks for a non-empty $bundle_property_name before calling accessCheck. However, for Site Studio content components, $bundle_property_name is empty, causing our code to skip adding the access check and resulting in a fatal error. To resolve this, the correct approach is to ensure the access check is called before executing the query, regardless of the value of $property_bundle_name. Therefore, in addition to Martin’s changes, we should also include a call to accessCheck(TRUE). Please review the updated patch provided below. While potential test case failures are uncertain, this solution will function correctly for both component contents and standard Drupal entities.

Fixed in https://git.drupalcode.org/project/acquia_perz/-/commit/c0d6efa0c266bfbd... and released in latest stable release.

Automatically closed - issue fixed for 2 weeks with no activity.