Multilingual tour for content translation settings

Created on 12 June 2013, over 11 years ago
Updated 19 May 2024, 7 months ago

Follow up for πŸ“Œ META: Write a multipage multilingual tour Postponed .

Problem/Motivation

Multilingual configuration is spread throughout the site. It would be useful to have a tour to help users know how to configure the site for multilingual. There should be individual tours for certain multilingual features and these can be linked together to make a multipage tour later via πŸ“Œ META: Write a multipage multilingual tour Postponed .

Proposed resolution

Write individual tours for the content translation settings only.

Remaining tasks

Create tour yml files for the content translation settings tour:

    • Not without stepping on other tours
  • Content language settings page (admin/config/regional/content-language)
    • Enable entities (Content)
    • Choose content types
    • Choose fields for translation
    • Configure default language per content type
    • Configure language selector per content type

User interface changes

New tours

API changes

None

Technical pointers when creating tour tips

See: https://drupal.org/node/1921152#tour-tips-tech-note for tech notes on making tour tips.

Related issues

🌱 META: Start providing tour tips for other core modules. Postponed
#1942576: Tour tips to be able to link to other pages and start tour's automatically. β†’
πŸ“Œ META: Write a multipage multilingual tour Postponed

πŸ“Œ Task
Status

Fixed

Version

2.0

Component
TourΒ  β†’

Last updated 5 days ago

Created by

πŸ‡ΊπŸ‡ΈUnited States Kristen Pol Santa Cruz, CA, USA

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Novice

    It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024