πŸ‡ΊπŸ‡ΈUnited States @wxactly

Account created on 12 March 2015, over 9 years ago
#

Recent comments

πŸ‡ΊπŸ‡ΈUnited States wxactly

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

πŸ‡ΊπŸ‡ΈUnited States wxactly

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

πŸ‡ΊπŸ‡ΈUnited States wxactly

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!

πŸ‡ΊπŸ‡ΈUnited States wxactly

Reroll of #25 against Drupal 10.2.x

πŸ‡ΊπŸ‡ΈUnited States wxactly

Sorry for the spam, y'all - giving this re-roll one last try for a working patch.

πŸ‡ΊπŸ‡ΈUnited States wxactly

Hmm, that one was still giving me Could not apply patch! Skipping - trying another re-roll.

πŸ‡ΊπŸ‡ΈUnited States wxactly

Updated patch for D10 compatibility

πŸ‡ΊπŸ‡ΈUnited States wxactly

Re-uploading #2 with fixed whitespace formatting

πŸ‡ΊπŸ‡ΈUnited States wxactly

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

Production build 0.69.0 2024