Source string (Built-in English)
What is a comment type?
Translated string (German)
Source string (Built-in English)
Comments are divided into <em>comment types</em>, which are the entity sub-types for the comment entity type. Each comment type has its own fields and its own form and display settings; each type can be used to comment on a single entity type. You can set up different comment types for different commenting purposes on your web site; for example, you might set up a comment type for recipes that has fields "How did it taste?" and "Did the instructions work?", and another comment type for blog entries that has only a generic comment body field.
Translated string (German)
Source string (Built-in English)
What is moderation?
Translated string (German)
Source string (Built-in English)
<em>Moderation</em> is a workflow where comments posted by some users on your site are verified before being published, to prevent spam and other bad behavior. The core software provides basic moderation functionality: you can configure permissions so that new comments posted by some user roles start as unpublished until a user with a different role reviews and publishes them. Contributed modules provide additional moderation and spam-reduction functionality, such as requiring untrusted users pass a CAPTCHA test before submitting comments and letting community members flag comments as possible spam. See @users_overview_topic for more about users, permissions, and roles.
Translated string (German)
Source string (Built-in English)
Overview of managing comments
Translated string (German)
Source string (Built-in English)
The core Comment module provides the following functionality:
Translated string (German)
Source string (Built-in English)
Posting comments
Translated string (German)
Source string (Built-in English)
Creating comment types; the core Field UI module allows you to attach fields to comment types and attach comment reference fields to other entities so that people can comment on them.
Translated string (German)
Source string (Built-in English)
Configuring commenting
Translated string (German)
Source string (Built-in English)
Moderating comments as discussed above
Translated string (German)
Source string (Built-in English)
See the related topics listed below for specific tasks.
Translated string (German)
Source string (Built-in English)
Moderating comments
Translated string (German)
Source string (Built-in English)
Configuring comments
Translated string (German)
Source string (Built-in English)
Creating a comment type
Translated string (German)
Source string (Built-in English)
Disabling comments
Translated string (German)
Source string (Built-in English)
Adding a field to an entity sub-type
Translated string (German)
Source string (Built-in English)
Configuring field display for an entity sub-type
Translated string (German)
Source string (Built-in English)
Configuring the edit form for an entity sub-type
Translated string (German)
Source string (Built-in English)
What is taxonomy?
Translated string (German)
Source string (Built-in English)
<em>Taxonomy</em> is used to classify website content. One common example of taxonomy is the tags used to classify or categorize posts in a blog website; a cooking website could use an ingredients taxonomy to classify recipes. Individual taxonomy items are known as <em>terms</em> (the blog tags or recipe ingredients in these examples); and a set of terms is known as a <em>vocabulary</em> (the set of all blog post tags, or the set of all recipe ingredients in these examples). Technically, taxonomy terms are an entity type and the entity subtypes are the vocabularies; see @content_structure_topic for more on content entities. Like other entities, taxonomy terms can have fields attached; for instance, you could set up an image field to contain an icon for each term.
Translated string (German)
Source string (Built-in English)
An individual vocabulary can organize its terms in a hierarchy, or it could be flat. For example, blog tags normally have a flat structure, while a recipe ingredients vocabulary could be hierarchical (for example, tomatoes could be a sub-term of vegetables, and under tomatoes, you could have green and red tomatoes).
Translated string (German)
Source string (Built-in English)
Taxonomy terms are normally attached as reference fields to other content entities, which is how you can use them to classify content. When you set up a taxonomy reference field, you can let users enter terms in two ways:
Translated string (German)
Source string (Built-in English)
Free tagging
Translated string (German)
Source string (Built-in English)
New terms can be created right on the content editing form.
Translated string (German)
Source string (Built-in English)
Fixed list of terms
Translated string (German)
Source string (Built-in English)
The list of terms is curated and managed outside the content editing form, and users can only select from the existing list when editing content.
Translated string (German)
Source string (Built-in English)
Taxonomy reference fields can be added to any entity, such as user accounts, content blocks, or regular content items. If you use them to classify regular content items, your site will automatically be set up with taxonomy listing pages for each term; each of these pages lists all of the content items that are classified with that term.
Translated string (German)
Source string (Built-in English)
Overview of managing taxonomy
Translated string (German)
Source string (Built-in English)
The core Taxonomy module allows you to create and edit taxonomy vocabularies and taxonomy terms. The core Field UI module provides a user interface for adding fields to entities, including the taxonomy reference field, and configuring field editing and display. See the related topics listed below for specific tasks.
Translated string (German)
Source string (Built-in English)
Concept: Taxonomy (Drupal User Guide)
Translated string (German)