Problem/Motivation

Config Entities - especially bundles ie node types/taxonomy vocabularies often have translations - both surface and deep (ie field config). Including them in the clone would be a large time saver in many multilingual situations.

Steps to reproduce

Clone a config entity with translations.

Proposed resolution

Clone the translations as well.

Remaining tasks

Write tests

User interface changes

Add checkbox to config entity clone forms.

Issue fork entity_clone-3183368

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

NickDickinsonWilde created an issue. See original summary.

NickDickinsonWilde opened merge request !3

NickDickinsonWilde’s picture

NickDickinsonWilde
He/Him/His
Primary language English
Location Victoria, BC (T'So-uke lands)
CreditAttribution: NickDickinsonWilde as a volunteer and at Taoti Creative commented
Status: Active » Needs work

Needs tests (and review ofc)

jrockowitz’s picture

jrockowitz CreditAttribution: jrockowitz as a volunteer and at The Big Blue House commented

@NickDickinsonWilde Your approach for cloning a config entity translation looks perfect. I am going to use it in the Webform module. Thanks

@see #3183926: Properly duplicate a webform's translations

NickDickinsonWilde’s picture

NickDickinsonWilde
He/Him/His
Primary language English
Location Victoria, BC (T'So-uke lands)
CreditAttribution: NickDickinsonWilde as a volunteer and at Taoti Creative commented
Status: Needs work » Needs review

Ready for testbot.
(btw, thanks for the comment Jacob, some of the tricky details were based on a comment of Berdir's a while back on stack overflow)