Closed (fixed)
Project:
Bulk Edit Terms
Version:
2.1.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Jul 2025 at 14:59 UTC
Updated:
1 Aug 2025 at 12:54 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
bkosborneComment #3
fjgarlin commentedThose are all great suggestions. All of them, except for the last one, seem pretty quick and straightforward.
I suggest doing all of them except the last one on this issue, and do the last one on a separate issue, so as not to block the quick and easy changes.
Comment #4
fjgarlin commentedOr if you still want to do it via one issue, then do it in two separate MRs. I'm happy either way.
Comment #6
bkosborneAgreed. I'll split that out into a separate issue. I may not even do it here. May be pretty easy with a form alter for our own use case.
Comment #7
bkosborneReady for review. Sorry, the changes look bigger than they are because I had to refactor how the form is constructed a bit. Now the code first gathers the list of all eligible term reference fields, then in a separate loop builds the form. This allowed me to collect the list of content types used by a field with the same name.
Comment #8
bkosborneeh, while I could do the change to select widget in a form alter, it's more complex that I'd like since we need to also load the term tree. Creating follow up to add it to the module...
Comment #9
bkosborneComment #10
fjgarlin commentedThe refactoring makes sense and looks good. Tests are also happy. RTBC.
Feel free to merge this yourself with your new admin powers 🙂
Comment #11
bkosborneThanks!