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.
Problem/Motivation
After #2165725: Introduce hook_entity_operation() was committed, the field instance config entity operations turned out to be out of order.
Proposed resolution
Fix this by making field instance config entities re-use the EntityListBuilder functionality, instead of overriding it by using its own custom operations.
Remaining tasks
None.
User interface changes
None.
API changes
None.
Comment | File | Size | Author |
---|---|---|---|
#6 | interdiff.txt | 7.05 KB | tim.plunkett |
#6 | field_ui-2235347-6.patch | 9.63 KB | tim.plunkett |
Comments
Comment #1
tim.plunkettHere's the fix. Not sure if we should fix the access controller here or not.
Comment #2
dawehnerseems legit
Comment #4
tim.plunkettHeh, base_path strikes again!
Comment #6
tim.plunkettHere it is with resolving the @todo about access.
Assuming the base_path fix was correct, I think this is done.
Comment #7
tstoecklerShouldn't the corresponding class be reomved as well, if this is no longer needed?
This looks good. I don't know if a 'view' operation even makes sense in this case, but maybe it makes sense to exclude that here? Not sure.
Comment #8
tim.plunkettIt's not removed, just moved to the right place (since it's field_ui, not field)
I'm not sure what it means to "view" a field... But its true that Views, DateFormats, FilterFormats, etc. all special case 'view' and return TRUE.
Comment #9
jibranI think patch is ok with nice clean up so #7 is ans in #8 so setting it to RTBC.
And this.
Oh I like it.
Comment #10
XanoI was thinking the operations are now out of order because the new situation also sorts them by label, but that is not the case.
Any way, I updated the issue summary, as this issue does a whole lot more than just fix the order.
Comment #11
alexpottCommitted e51789c and pushed to 8.x. Thanks!
Comment #13
tim.plunkett