Closed (fixed)
Project:
(Obsolete) configuration translation for Drupal 8
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Anonymous (not verified)
Created:
20 May 2013 at 14:33 UTC
Updated:
15 Feb 2026 at 08:06 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedWhile this meeting, I am investigating this problem.
Comment #2
gábor hojtsyHere is a short summary:
Drupal best practices:
1. Your config should be stored with the config .yml system in core
2. You should write configuration schemas for your config (docs: https://drupal.org/node/1905070, module to test/inspect: https://drupal.org/project/config_inspector)
3. Make sure your config file has langcode: en (or another langcode as appropriate) at all times; put up a language selector for users if the config can change language (see core has for views, vocabularies, etc).
Config translation UI enablement
4. If (1), (2) and (3) are true, you can use hook_config_translation_group_info() (see docs in https://drupal.org/project/config_translation) to map config keys to paths (or config entities, if you have those)
5. If the config you are dealing with is a config entity and you also have a listing page for your entities, add a translate operation to the list if the config_entity module is turned on (this will hopefully be automated later as well)
This will magically expose a translation tab on your config settings page (or config entity editing page), which lists languages and lets people submit translations (and go back edit original config values).
Any questions? :)
Comment #3
Anonymous (not verified) commentedThank you. Sorry for my late reply. I have been trying to reproduce it.
Comment #4
gábor hojtsy