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.
Along with #731558: Use taxonomy_save_term() for all CRUD functionality, it would also greatly simplify many other efforts if taxonomy_manager just used taxonomy_form_term() for the forms instead of building its own.
Comment | File | Size | Author |
---|---|---|---|
#7 | taxonomy_manager-n731566-step1b.patch | 6.77 KB | DamienMcKenna |
#1 | taxonomy_manager-n731566-step1.patch | 6.77 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaHere's a patch against CVS. So far I've gotten the form itself to show up and work correctly (I think), the next step is handling the saving. Note: right now the save action just returns print_r($_POST) and exits, so it won't save anything.
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedDoes this end up breaking integration with term relation types module? http://drupal.org/project/term_relation_types
Comment #3
DamienMcKennaI'd never seen that one before.. I'll give it a look after getting this core functionality working first.
Comment #4
DamienMcKennaComment #5
mh86 CreditAttribution: mh86 commentedhow would the form look like? can you provide a screenshot?
Comment #6
DamienMcKennaIt would be the normal taxonomy term form.
Current limitations:
Comment #7
DamienMcKennaAn updated patch that passes tid and vid as hidden fields rather than values (which don't show on the form itself).
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous commentedDamien:
The reason I asked about term relation types is that it hooks into the taxonomy manager form (and custom modules of mine do as well) but it doesn't hook into the core taxonomy term form.
If this work unifies everything, wonderful. But if it breaks support for the other modules that hook into taxonomy manager's editor, I worry that it may not go far.
Comment #9
ivnish CreditAttribution: ivnish commented