Patch to add tabbed user interface and other enhancements
| Project: | Taxonomy Node |
| Version: | 5.x-1.5 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Jump to:
Taxonomy node is going to save my butt on a current project, but I found the interface a bit cumbersome for ordinary users.
I've added a tabbed interface option which switches between the term edit form "basic" and the node edit form "advanced". The tabs can be toggled on or off at /admin/content/taxonomy/taxonomy_node. Tabs are currently off by default. When enabled, I've also removed the instruction messages. I've also removed the disabled vocabulary form elements on the node page since they didn't do anything. The vocabulary is still submitted using the 'value' type element.
Separate from the tabs UI, I've also added the ability to update the Term Name with the node form using the title field.
If you're open to other UI enhancements, I'll probably be working heavily with this module for the next few months.
Thanks!
Chris.
| Attachment | Size |
|---|---|
| taxo_node_tabs.patch | 8.71 KB |
#1
I'll review this suggestions and any other you might send.
About this issue I have only one comment. The purpose of of the disabled vocabulary field is to show the node/term's hierarchy. If you have a hierarchy vocabulary, the hierarchy is maintained on the nodes and I'd like the idea to have that hierarchy displayed. Editing the term name from the node title might be useful but I wanted to keep the module simple enough and have everything updated from one place, but I'll look into that.
It helps for reviewing patches if you keep only the modifications needed, rather than also removing code that you might find not useful or needed but we can discuss removal of things on separate issues.
I am more than willing to receive any contributions to the module so feel free to post them all.
Thanks a lot!
a.=
#2
#3
Ok, sounds good. I see your points. The disabled fields are the only thing I removed, and we can discuss those separately.
I need to use this module, but the interface doesn't work for our level of users. They have never seen Drupal before and are quite non-technical. How would you feel about adding an option to display the hierarchy or not? This would be useful when your vocabulary doesn't allow a hierarchy. The options could be per vocab too - The tab option is currently global, but doesn't need to be.
If I can achieve these things in a way that's agreeable to you, I can avoid creating an add-on module that form_alters the UI and may break upgrades in the future.
Let me know if you want to see any other changes. I'd be happy to make them and submit a new patch.
#4
Subscribing, greetings, Martijn
#5
I agree with this poster. I, too, have patched the code to remove the vocabulary select box, but in the 6.x-1.0-beta3 version. Users are not going to understand why the box is there when:
A) Nothing is selected, even though technically the node *is* associated with a taxonomy term. This is probably a bug that should be filed as a separate issue (edit: see Nodes associated with taxonomy terms are not tagged with the term).
B) The box doesn't allow them to select anything, and in most browsers, the disabled state doesn't look much different than the enabled state (still looks white, with a scrollbar).
I would much prefer a label (using the "markup" Form API element type) to show the associated term hierarchy, as users can just ignore it if they don't understand it. Form fields make the user think they have to supply something.