Problem/Motivation
I'm pretty sure that in #3328351: Explicit access checks on content entity queries, we went a bit to far. We need to back out the accessCheck on the membership loader. Patch attached. Not sure how to add test coverage for this, but it should be added.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 3328924.patch | 596 bytes | heddn |
Comments
Comment #2
heddnComment #3
mindaugasd commentedAdding some errors with access checks on D10. Sorry if unrelated, but just in case these mean anything to you. I get these errors in various many places.
Comment #4
kristiaanvandeneyndeHmm dammit, just combed over all changes manually again to double-check and will tag new release.
Re #3: please open a separate issue.
Comment #7
kristiaanvandeneyndeAlready committing and releasing fix, but leaving issue open for adding test coverage.
Comment #8
kristiaanvandeneyndeComment #9
sweetchuckThe issue and the error messages mentioned in comment #3 are still exists in
drupal/core: 11.3.2
drupal/group: 3.3.5
Comment #10
sweetchuckIn case somebody lands here, because of searching for a solution for error messages in comment #3.
The problem is that
groupandentity_clonemodules aren't friends.drupal/core: 11.3.2
drupal/group: 3.3.5
drupal/entity_clone: 2.1.0-beta1
/admin/config/system/entity-clone/clonable-entities/group/1/content