Follow-up to #2225775: Migrate Drupal 6 core node translation to Drupal 8

Problem/Motivation

Entities that are translated need an auxiliary migration to be pulled into D8. Entities with revisions also need an auxiliary migration. These migrations are extremely similar to the base migration, with basically the same source/process/destination, and just a few changes. Currently each of them requires a nearly-identical migration template YML file.

Eg: d6_node__page will also have migrations d6_node_revision__page and d6_node_translation__page.

Proposed resolution

  • Automatically create node translation migrations, based on the node migrations.
  • Automatically create node revision migrations, based on the node migrations.
  • Find a way to do this that can be easily applied to other entity types as well, so we don't need to redo this work for terms, users, etc.

There should be no changes to API, UI, or data model.

Comments

vasi created an issue. See original summary.

vasi’s picture

Status: Reviewed & tested by the community » Active
mikeryan’s picture

Status: Active » Postponed
mikeryan’s picture

Status: Postponed » Active

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

mikeryan’s picture

Priority: Major » Normal

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Gábor Hojtsy’s picture

Issue tags: -sprint

Definitely not being worked on, so removing from sprint.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

masipila’s picture

Re-parenting so that all multilingual migrations can be found from the same meta. Moved original parent to related issues.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Issue tags: +DrupalSouth 2019

With the master node migration that is being proposed in #2746541: Migrate D6 and D7 node revision translations to D8 the need for the _translation and _revision migrations can eventually be removed and this will no longer be needed.

Wim Leers’s picture

#15: Oh, wow! So the "revision" and "translation" migrations will simply disappear?

(When using drush migrate commands, they will not be listed anymore?)

quietone’s picture

Now that #2746541: Migrate D6 and D7 node revision translations to D8 is committed I think this is now a won't fix.

Any objections?

quietone’s picture

Status: Active » Needs review

Meant to set this to NR for #17.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

mikelutz’s picture

Status: Needs review » Closed (outdated)

Closing as outdated. This doesn't apply anymore.