Problem/Motivation
The Taxonomy module by default provides a Description field for taxonomy terms. Its label and help text cannot be changed in the UI. The field can be placed (and disabled) on the Manage form display page, but it cannot be removed.
In use cases where for example the description should only be a shorter plain text field, or where a different label or a different help text is required, the site builder needs to add their own text field in addition and then hide the Description field from the form and the display.
For other entities (for the default Article content type), a default Body field is provided but can be removed on the Manage fields page.
Proposed resolution
Expose the Description field on the Manage fields page, similar to the Body field of a content type.
Remaining tasks
User interface changes
This is a UI change.
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#6 | 2751013-6.patch | 6.03 KB | marvin_B8 |
Comments
Comment #2
pashupathi nath gajawada CreditAttribution: pashupathi nath gajawada as a volunteer and at Melity commentedI am looking into this issue.
Comment #4
ifrikpashupathi nath gajawada, I unassigned you, so somebody else can pick up the issue.
Comment #5
marvin_B8 CreditAttribution: marvin_B8 as a volunteer and at comm-press commentedComment #6
marvin_B8 CreditAttribution: marvin_B8 as a volunteer and at comm-press commentedi'm not sure why it’s implemented as a entity basefield and not as a normal field.
Maybe it exist some reason for that, but i don’t know.
The code is only a example implementation.
Comment #8
marvin_B8 CreditAttribution: marvin_B8 as a volunteer and at comm-press commentedComment #9
marvin_B8 CreditAttribution: marvin_B8 as a volunteer and at comm-press commentedComment #10
ifrikThanks marvin_BB for putting the usability tag back again after removing it. In general tags should not be removed because they are used for more then just displaying them one the single issue page.
The "usability" tag for example is used to display open issues on http://drupalux.org - and of course we want people to find UX issues after the a specific sprint as well.
Comment #11
dawehnerI doubt we can really do that. Doens't this changes the underlying table structure? It used to be a base field and no longer is.
Comment #13
Berdir#569434: Remove taxonomy term description field; provide description field for forum taxonomy is an old existing issue that wanted to do this but we didn't manage for 8.x and I'm not sure how to do this for 9.x now as we can't break BC.
Closing as duplicate.
Comment #14
mpp CreditAttribution: mpp as a volunteer and at AmeXio for District09 commented