content type

Content Types, Users, and Other Entities

In all probability, your app will add a few new fields to existing data models or create some new entities.

Create a Namespace

All machine names should be namespaced with the title of your app. For example, all Panopoly News fields, content types and views have "panopoly_news" applied to them.

Enabling entity translation for a content type

With Entity Translation enabled for "Node", you can set the translation mode (Entity Translation or Content Translation) for each Content Type. To enable translation mode for a particular content type, you need to edit the content type and click on the 'Publishing options' tab and choose under Multilingual support:

• "Enabled, with translation" for Content Translation
• "Enabled, with field translation" for Entity Translation

Note that the i18n submodules "Field Translation", "Multilingual Content" and "Multilingual Select" do NOT need to be enabled to use Entity Translation properly, and SHOULD NOT be enabled to use Entity Translation properly with an upgrade path to multilingual websites in Drupal 8.

How to enable translation for particular fields

Once entity translation has been enabled, you can make individual fields for the content type translatable by first editing the field and then going to the 'Field Settings' tab, checking the Users may translate this field checkbox, and saving the settings.

Translation of titles

By default in Drupal 7, titles are not fields. Titles of nodes can be converted to fields using the Title module as follows:

Starting with Drupal 7 the concept of entities arose. Entities are used to store and display data, which could be a node, a user, a taxonomy term or something custom developed. Entities have a list of helper functions that can ease development and it is possible to add fields to entities via the UI, like we know it for nodes.

In Drupal, a Content Type is a pre-defined collection of data types (Fields) which relate to each other by an informational context. In this sense, "context" means "parts that should be considered as a correlated whole." Content Types are how site editors can input original content on a Drupal site; while Views, for example, is one way you can serve up content to your end users.

The Blog module (a core module in Drupal 7 and earlier) allows authorized users to maintain a blog. Blogs are a series of posts that are time stamped and are typically viewed by date as you would view a journal. Blog entries can be made public or private to the site members, depending on which roles have access to view content.

Note that the Blog module is not needed for a "single-user" blog (a site that only has one individual blogging). For that use case, it's simpler to create a custom content type. The Blog module is usually used when there is a need for a number of blogs, written by different users, running on one site. For more information on creating a single-user blog, see this Single User Blog recipe.

The Blog module was removed from Drupal 8 core but it can still be installed and enabled as a contributed module.