Drupal 8 User Guide: 10.3. Configuring Content Translation

Configuring Content Translation
with Amber Matz In this tutorial,
we’ll walk through the process of configuring content translation. By the end of this tutorial,
you will make Custom block, Custom menu link
and Content entity types translatable and you'll understand
how to select specific subtypes and set which of the fields on each of these entities
can be translated. To follow along, you should understand the concepts of content
entities and fields, as well as user interface, content, and configuration translation
in a Drupal site. See the written version of this tutorial for links to the prerequisites. In the Manage administrative menu,
navigate to Configuration. Then, in the Regional
and Language section, select Content language and translation. Under Custom language settings,
check Content, Custom block, and
Custom menu link to make these entity types translatable. This causes 3 sets
of configuration options to appear, labeled with the headings Content, Custom block, and
Custom menu link. The second column contains
the available subtypes. These subtypes will have different
labels depending on the entity type. For example, Content type, Custom
block type, and Custom menu link. Let’s choose the subtypes we want
to translate for each entity type. Check Basic page for Content; Basic block for Custom block; and Custom menu link
for Custom menu link. Scroll back up and let’s start
with Basic page. When we originally checked
the translatable box for Basic page, this checkbox also was checked, Show language selector
on create and edit pages, and we’ll keep that checked. Next, we need to verify these fields to see which ones we actually
want to be translatable. Published we’ll keep checked.
Title is checked. Authored by, we’re going to uncheck. Authored on, we’ll also uncheck. Changed, which is the date
of last update, uncheck. Promoted to Front Page, which is whether the content will be
included in some content views, uncheck, as well as Sticky
at top of lists. URL alias, which, as you recall, is a nicer URL for the content,
we’ll keep checked. And Body, which is the main content
of the page, also checked. Now, scroll down to Custom block. For Basic block,
we’ll just uncheck Changed, as we did above and same
with Custom menu link. Uncheck Changed,
and now, Save configuration. A message will display that the settings were successfully updated. In this tutorial, we configured
the Custom block, Custom menu link, and Content entity types
to be translatable, and we selected which of the fields
on each subtype should be translated. See the written version
of this tutorial for links to resources that will expand
your understanding of this topic.

Leave a Reply

Your email address will not be published. Required fields are marked *