INTEREST JOURNAL DRUPAL & WEB

Drupal Guide in Detail: 10.3 Adding a Translation to Existing Content

About 400 words 2 min read

Japanese ↗
On this page

Detailed guide. An unofficial adaptation of User Guide 10.3. Source updated April 14, 2025; reviewed November 6, 2026. No running-Drupal procedure test has been performed.

Official source ↗ · Previous: 10.2 Configuring Translatable Types and Fields · Chapter 10 overview · Next: 10.4 Translating Views and Other Configuration

Goal and prerequisites

Translate the existing Home item into Spanish. It needs at least two languages, Content Translation and a translatable type and fields configured in 10.2 . This creates a translation attached to the item, not an unrelated new page.

Adapted procedure

Find Home at /admin/content, choose Translate from its operations, and add Spanish. Use Página principal for the title. Translate the sample welcome, April–September Sunday hours and market location into Spanish; they are fictional learning data. Add the pagina-principal alias and save this translation.

The source omits a leading slash in its alias example. Follow the installed form’s validation, using /pagina-principal if required.

Our checks: language and URLs

The source removes a leading es URL prefix to return the administration UI to English. Behavior depends on language negotiation. Prefer an available language switcher; do not remove every es segment, which could change source or target identifiers in the route. Verify publication, original/translation linkage, aliases and homepage switching. Check the effect of edits to shared fields too.

Optional-extension security notes

308 ↗ concerns Allowed Languages permitting creation in a disallowed language by someone who can create content in at least one language; the advisory names 2.0.3 as fixed.

310 ↗ concerns WordsOnline Connector SQL injection through TMGMT, requiring login and Create translation jobs permission. It names 2.0.6 as fixed; 1.0.x is unaffected.

These are historical fix references; check official current releases. Neither extension is implied by core’s manual translation exercise.

Sources, credits and changes

Source: Drupal User Guide 10.3 ↗ . Contributors and source links listed in its Attributions: Boris Doesborg ↗ . Refer to the source for writing, editing and adaptation roles, and to the guide-wide credits ↗ .

Copyright remains with the individual contributors; the official copyright page ↗ states © 2015–2025. Changes include reorganized explanations and procedures, our preparation and verification examples, troubleshooting notes, source-interpretation qualifications and release references. Original screenshots and videos are not reproduced. This adapted text is shared under CC BY-SA 2.0 . It is not an official edition or endorsement. This notice does not license unrelated articles or the site design.

Previous: 10.2 Configuring Translatable Types and Fields · Chapter 10 overview · Next: 10.4 Translating Views and Other Configuration

Chapter 9 details · Chapter 11 · All chapters · Search official information

Back to chapter contents ↗