Remove vocabulary description

It would also be nice if there was a way to restrict the characters used in terms, especially for free tagging terms created by users. I would like to restrict tags to alphanumeric characters because they are used by Views to generate URLs.

+1, need this too.

This went in for taxonomy descriptions in another issue, but none of us in that issue could think of a use case for vocabulary descriptions. It's possible such a change could still go in for D7, if it was clearly explained why vocabularies need this.

The text is shown below the taxonomy title and if this text contains words you'd like to emphasize with bold, italic, underline you need to be able to enter HTML.

No, it's not, that's the term description, which already has a format in HEAD.

I have no idea what the vocabulary description is used for, apart from that it's displayed in the vocabulary edit form, perhaps the admin/content/taxonomy listing table, and that still doesn't have a format.

Sorry, then forget it... D6 doesn't have a format for term descriptions... and I haven't taken a look to this field in D7, yet. If you say it has a format, I'm fine. Not sure if the others in here meant the description of "terms" - but said "taxonomy"!?

I'm almost done with a site I;m working on and now I realised that I need the ability to have a description body field (for a term) that a user can add html copy. The description on the term page seemed to be what I needed but I need to add html too. So I need to enable a wysiwyg. But this term description field doesn't have input format.

How to have html support for term description? or is there another approach that I don't know?

I need this also :( Hga77, or anyone else, have you come across a solution?

Hey madtown,

I tried everything I could. Then I realised that I'm waisting time. There is even a module that tries to add a body text field per taxonomy...But it just didn't work the way I wanted. At the end I re-did all my work using cck instead of taxonomy. A whole day it took me but it was well worth it at the end.

Don't use taxonomy unless you know you need to and you know the pros/cons versus using cck...Look at your use case and choose the the correct one! Don't do what I did...I had to strip out ALL taxonomy and re-build with cck! Worked out great at the end.

However I remember that using CCK, whenever I needed to group cck items (aka Terms, when using taxonomy) and display them inline from views, it wasn't very straightforward (Taxonomy+views lets you do that). So what I did was use javascript to re-shuffle those and make inline and so on, whenever I'm displaying them from views. Maybe latest views lets you do this, dunno...

The term description in Drupal 7 already has a text format. It's just the vocabulary description, which is rarely used anywhere, which doesn't.

Um. I've just searched through Taxonomy module. The vocabulary description is not used anywhere. (?) Why does it exist in the first place then?

See #8. I believe some contrib modules use it, I don't think that's enough of a reason to keep it in.

Issues like this are perfect to re-purpose, since the whole reasoning is contained. I wonder whether it may even still be possible for D7?

Duplicate of #394576: Remove vocabulary description, kinda sorta, though that issue proposed removing it for usability reasons. The vocabulary description is a field now, and it does have display settings... not that there is a menu path to display a vocabulary. However, I'm sure there's contrib and views that use it.

Edit: I marked #394576: Remove vocabulary description as a duplicate of this issue.

See also #1192070: Remove / Don't add a default "Description" field to Terms.

I started an issue yesterday looking to move term and vocabulary description to a varchar(255) rather than a text field to improve database performance #1422618: Make taxonomy description a field. If we just remove the descriptions and replace them with a fieldAPI body field then this should solve both issues, right?

"The vocabulary description is a field now, and it does have display settings..."

Which issue is this being worked on? The latest checkout today has description as a hard wired textfield, the taxonomy_vocabulary entity is marked as not fieldable. I'm assuming you are referring to the term description?

1. The vocabulary description is not a field. Neither in HEAD, nor do I know of any effort to do so. Only #569434: Remove taxonomy term description field; provide description field for forum taxonomy exists.
2. Converting the description into a field would mean a field on a bundle. Because this is not clear enough: A field on a bundle. Not a field on an entity of a certain bundle. We don't have that anywhere in Drupal yet.
3. #1552396: Convert vocabularies into configuration is about to convert vocabularies into configuration. There's no facility yet that would allow fields to be attached to configuration, and I don't even want to think about that at this point...
4. Therefore, I'd still recommend to drop the description property from vocabularies altogether, without replacement.

Nice followup. I definitely will not open a feature request for a "Fieldable vocabulary" then, even if this is strangely lacking and a super trivial task! :)

It's stored in a config file now node type also has a description field I don't think it makes sense to remove it.