Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Profile still uses the old permission code, which moved to Commerce, then moved to Entity API, and got many bug fixes along the way.
We need to rip the current code out, start using the Entity API one.
Should fix issues like #2815273: Edit permission has no effect.
Comment | File | Size | Author |
---|---|---|---|
#13 | start_using_the_entity-2844908-13.patch | 24.09 KB | mglaman |
#6 | start_using_the_entity-2844908-6.patch | 24.52 KB | mglaman |
Comments
Comment #2
mglamanLinking related issues. First step is to get test failures that reprelicate reported issues. Then implement code and see that it passes.
Comment #3
mglamanComment #4
mglamanWorked on this during train ride. Proposed change record once I work out the last few issues: https://www.drupal.org/node/2866124
Comment #5
mglamanRefactoring this caused #2854336: Private fields are visible to any user with view access to the profile to fail.
Comment #6
mglamanHere is first patch. It uncovered issues that we have in the queue. Instead of fixing here I commented those items out with @todo
Comment #10
mglamanContributing others, because thanks for finding the other bugs :)
Comment #11
mglamanComment #13
mglamanFixed the kernel test
Comment #15
mglamanOkay! Huge step forward, now for the other follow ups.