Remove vocabulary description
beeradb - March 7, 2009 - 20:34
| Project: | Drupal |
| Version: | 8.x-dev |
| Component: | taxonomy.module |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | UBUserTesting2009, Usability |
Jump to:
Description
When creating a new vocabulary the form users are presented with is already overwhelming enough. Lets not make users enter 'description' which is used no where in core.
We'll have to think about an upgrade path for any modules which are using this, but my thoughts are that they can provide the field themselves.
#1
Any pointers to modules using this?
#2
#3
At least some contribs use it. Therefore I don't know if it's a really good idea to remove it. It's too specific to tell maintainers to provide a field themselves (adminis may end up with more than one description field). On the other hand it makes the interface quite strange-looking.
#4
Do you know what they're using it for?
One possibility is to remove the form and hook_schema, leave the column in the database in existing installs, then kill it in a later release. That way there's an easy migration path for the data.
More extreme version - make taxonomy vocabularies into a fieldable object, better do terms first though.
#5
Vocabulary Index uses it when browsing a vocabulary and AFAIK other Taxonomy browsers do the same. Nothing disastrous will happen if we decide to remove it, but I just thought we should discuss is before we do anything without proper thinking.
#6
Ok -- so with the following patch that has made it into core, what's next, catch?
#413192: Make taxonomy terms fieldable
Josh
#7
We could probably make taxonomy vocabularies fieldable but I don't know if that's desirable at all - we'd have to leave out half the field_attach_* calls because they'd never get called (that'd also make it a small patch though, which is good I suppose). I think this is lower priority than the terms as fields patch - since that removes a lot of the other cruft from this form hopefully.
#8
Just a thought, but with the field conversion on the way the help text rather than the description is obsolete, since it only applies to tagging widgets.
#9
Well, if you want to keep the Description field in there as it is, it should gain back the help text that was in D6: "Description of the vocabulary; can be used by modules." I wonder why that disappeared in D7....
(I was just writing about that field for my upcoming Peachpit book and got totally flummoxed. :-P )
#10