Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
From entity.views.inc:
// @todo: Support an entity info description key or such?
Also, there are needs for a multiple label, e.g. I think feeds already invents something like that. We should do it with the entity.module and push it for d8.
Comment | File | Size | Author |
---|---|---|---|
#7 | 1216258-entity-descriptions.patch | 6.33 KB | klausi |
#5 | 1216258-entity-descriptions.patch | 3.79 KB | klausi |
#2 | entity_label_plural.patch | 2.86 KB | fago |
Comments
Comment #1
fagoadding tag
Comment #2
fagoPatch adding those keys for d7 attached.
Comment #3
bojanz CreditAttribution: bojanz commentedI like both the patch and the idea.
Comment #4
fagook, so I guess we should provide that values for all core-entities then.
Comment #5
klausioh boy, this could become a real bike shedding issue. I find it hard to come up with proper core entity descriptions. But at least I tried ;-)
Not sure the descriptions are in the right place though.
Comment #6
fagosounds good to me.
Views has:
Users who have created accounts on your site.
we should move this under the existing if clauses in _entity_info_add_metadata_callbacks() + improve that function name to fit.
We are still missing plural labels for the other entity types?
help has:
"To classify content, you define vocabularies that contain related terms, and then assign the vocabularies to content types."
So what about:
"Vocabularies contain related taxonomy terms, which are used for classifying content."
Views has: "Taxonomy terms are attached to nodes."
ouch.
Taxonomy module has that help sentence:
Taxonomy is for categorizing content. Terms are grouped into vocabularies. For example, a vocabulary called "Fruit" would contain the terms "Apple" and "Banana".
So maybe, "Taxonomy terms are used for categorizing content."
Comment #7
klausiOh, I thought we don't need the plural forms for regular words, but of course they are needed for translations.
Fixed all your remarks.
Comment #8
klausiComment #9
fagoThanks, patch looks good. We just spotted in inconsistency inside core:
Classify or categorize? I'd vote for the former.
Comment #10
klausiexplaining things in other words might not be an inconsistency. Anyway, I don't care about that minor detail.
Comment #11
fagoIt's minor, still users might be confused by different wordings in different places in the UI (see node, content, post ..). So I've chosen "classifying" and committed it.
Thanks!