Clean up term form UI

updating tags.

Attached is a patch for this text. I was a little torn on weather to indicate that the inputs did not have any functionality by default, but after spending a while figuring this out myself, it seems like it might be an important piece of information.

Thanks, karschsp!

@bojhan although in general I agree with you, these are advanced features which are totally undocumented in the interface. Do you know what a synonym does? what effect it actually has on the vocabulary? I don't think these features are self explanatory.

I'm open to other ways to convey the meaning of these fields, but as is we're not doing that at all.

@bojhan What would you recommend for the help text on each of those fields?

Here are my suggestions for the text. The "relationship" information is based on the correct terms for semantic relationships in controlled vocabularies. See more at: http://www.slis.kent.edu/~mzeng/Z3919/4relationship.htm

1. Parents
Relationship: hierarchical. Items will exist below (or within) the parent(s) you select.

2. Related Terms
Relationship: associative. Items will exist alongside the ones you select.

3. Synonyms
Relationship: equivalent. Items entered will behave as if they were identical to one another. Enter one term per line.

I'm not convinced it makes sense to repeat the phrase, "X has/have no core functionality, but may be extended by other modules." I think there is a better place to put this information. What if Parents and Weight were grouped, and "Related Terms" and "Synonyms" were also grouped?

Adding tags.

And this patch renames "Advanced options" to "Relationships" as that is basically what it is.

Screenshots before and after the patch #13

before:

after:

Looks good, please fix the patch.

Before & after.

Yup, agreed - good terminology.

The last submitted patch failed testing.

back to rtbc

We'll leave it in here. Without it, the sentence reads very 'required'.

The term form is pretty broken still:

Related issue for the position of URL alias textfield: #678590: Path alias link is below submit button on taxonomy term add

All we need to fix is the location of the url alias? The rest seems to been fixed, the breadcrumb is a larger issue - not meant to be fixed here.

This form has Field API 'fields'. The order is defined by the admins on admin/structure/taxonomy/%tid/fields.

Reordering doesn't play nice when there are fixed-weight items in the middle of user-reorderable items.
So the consequence for other, non-Field elements in the form is that :

a) Either they declare themselves as 'reorderable' as well, using hook_field_extra_fields(). They just provide a default weight.
That's the case of 'Name' and 'Description' : see taxonomy_field_extra_fields(), and the result on this screenshot.

Should be done only if we see value in letting users tweak their position. Having too much stuff available for reordering only adds confusion for users.
I'm not sure this is the case for 'URL alias' and the 'Relations' fieldset.

b) Or they stick with a fixed position at the bottom of the form, with a reasonably high weight (100+) so that they stay out of the range of weights of the reorderable items
That's what the buttons container does.

Currently, 'url alias' has an implicit fixed weight of 0 (path_form_taxonomy_form_term_alter()), and 'Relations' has a fixed weight of 10. Both are wrong.

Won't fix it is then?