Thanks all - this has been merged into the latest version of the module.
Thanks all - this has been merged into the latest version of the module.
Thanks all - this is fixed in 3.0.0-beta2
Thanks all - this is fixed in 3.0.0-beta2
Thanks all - this is fixed in 3.0.0-beta2
Fixed in 3.0.0-beta2
Fixed in 3.0.0-beta2
Uploading a more complete fix using core/once
Uploading patch.
Thanks @texas-bronius - I would recommend not using the patch in #3 because it would open the site up to potential access/security issues.
Check out the patches here that apply accessCheck(TRUE): https://www.drupal.org/project/redhen/issues/3402288#comment-15344955 🐛 Entity queries must explicitly set whether the query should be access checked or not RTBC
Marking this as a duplicate. Anyone following this issue should check out the patches here: https://www.drupal.org/project/redhen/issues/3402288#comment-15344955 🐛 Entity queries must explicitly set whether the query should be access checked or not RTBC
Both patches in #3 work for me too.
Patch attached.
N.B. This is likely not a perfect solution to this bug, but it works for me, and hopefully highlights the underlying problem to someone who can land a more proper patch!
Reroll of #25 against Drupal 10.2.x
Sorry for the spam, y'all - giving this re-roll one last try for a working patch.
Hmm, that one was still giving me Could not apply patch! Skipping - trying another re-roll.
Updated patch for D10 compatibility
Re-uploading #2 with fixed whitespace formatting
This patch fixes the bug.
It looks like the extra pull_where_clause code was removed in https://git.drupalcode.org/project/salesforce/-/commit/d041e14e5e00c020e... so the patch in #12 was accidentally removing it again. Here's another reroll that leaves pull_where_clause alone