When I go to admin/structure/taxonomy/2/add to add a term to vocabulary #2, the URL alias field is below the submit button on the screen. It shouldn't be. See screen shot.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 678590-path-term-field-weight.patch | 3.8 KB | damien tournoud |
| #3 | 678590-path-term-field-weight-D7.patch | 3.82 KB | dave reid |
| #2 | 678590_01.patch | 3.43 KB | asimmonds |
| #1 | 678590.patch | 2.39 KB | asimmonds |
| termadd.png | 14.39 KB | jhodgdon |
Comments
Comment #1
asimmonds commentedThis is the result of removal of the identification fieldset in #664022: Remove Identification fieldset from term add
Trying to fix this appears to be harder than it looks, if we still want the path textfield to show just under the term description textarea.
Patch attached attempts to adjust the #weight of the path alias textfield by using a #after_build callback on the form.
I'm not entirely happy with this, too much of a hack IMO, may be it's easier to do if this and the term's 'advanced options' were in a vertical tabs arrangement similar to /node/add. Ideas?
Comment #2
asimmonds commentedLets try something simpler, instead of a #after_build, just manually apply weights to the form elements.
Comment #3
dave reidBetter one that uses our $form['actions'] structure to contain the form's buttons.
Comment #4
damien tournoud commentedSame patch, without the broken #access in 'delete'.
Comment #5
dave reidYes, that's much better. Thanks Damien. :)
Comment #6
dries commentedCommitted to CVS HEAD. Thanks.
Comment #7
yched commented#499192: Fix display and forms for "Fieldable terms" does the job of exposing the non-Field elements in the taxo term form.
The weights 0 and 10 assigned by the patch committed here will clash with Fields with user-assigned order. As with any form that includes Fields (and the 'reorderable' behavior that comes with those), we cannot stick hardcoded form elements at fixed weights in the middle of user-reorderable fields.
So either:
a) we make those elements ('relations' fieldset and 'URL alias' input) reorderable on the 'Manage fields' page by exposing them in hook_field_extra_fields().
b) we don't make we assign them heavy weights so that they automatically stick at the bottom of the form, just above the submit button. Less cruft for the user to take care of on 'Manage Fields' page. That's what we did for the Vertical Tabs at the bottom of node forms.
Thoughts ? - We can include the changes in #499192: Fix display and forms for "Fieldable terms" , but raising the topic here.
Comment #8
dave reidOooh. +1000 for having path.module implement hook_field_extra_fields().
I opened #687994: Add hook_field_extra_fields() implementation to path module for this so I'll go ahead and mark this as fixed.
Comment #9
yched commentedAgreed for the 'URL alias' input.
This leaves the question of the 'relationships' fieldset. Reorderable, or always at the bottom of the form ?