Clean up the taxonomy term and vocabulary interfaces
chx - October 6, 2006 - 06:40
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | taxonomy.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | chx |
| Status: | closed |
Description
I am saying this is a usability bug. Look at your term edit screen before and after :)
Also removed some very dead-looking code. If you want to change a form, then you use hook_form_alter. The code removed did not pass the term, so what gives?
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| taxonomy_term_form_cleanup.patch | 3.03 KB | Ignored | None | None |
#1
And, a screenshot.
#2
Let's make it easier for advanced taxonomy modules to make the Advanced Options open by adding a variable, without adding a UI for it.
#3
Notes: I think synonyms should have a note saying that it is only used if some module utilizes it. I think description should say that the description is only used for administrative purposes unless some add-on module utlizes it.
I also think cleaning up the vocabulary page similar to this approach is more important; it's the first page someone sees, and those options are opaque.
#4
Definite improvement.
The closely related vocabulary form would benefit even more from a similar overhaul.
#5
I agree with merlin's comments. Implement them and this gets committed. :)
#6
Can I request a very simple and friendly usability enhancement to this page: the cursor should default to the 'Term' field, so you can enter a whole series of terms without having to reach for the mouse each time. This is something that is a major PITA when you have a long list of terms to enter.
I would be happy to figure this out (jquery or plain js?) and add it to the patch if there is interest - it should only be a couple of lines.
#7
I would like to see this moving so please add JS in a separate issue. Also, vocabulary edit is a separate one.
#8
reviewed and works great.
#9
- 'Advanced Options' should be 'Advanced options'.
- The relation stuff is not showing up here (making the form not quite 'advanced').
#10
Marking as Code needs work based on Dries' comments.
#11
Doesn't look like this will get into 5 - so moving it to 6.
#12
Now that taxonomy_manager is here, makes sense to bump this to 7.x.
#13
There is already an advanced fieldset on the term form, and the interface is much simplified.
Marking 'fixed'.
Robin
#14
Automatically closed -- issue fixed for two weeks with no activity.