In order to develop a migration path for translated content, we need some actual, y'know, translated content in Migrate Drupal's database fixtures. :) This should be its own patch because enabling the relevant modules adds a great deal of data to the fixtures, and I don't want to mix that up with patches that contain actual migration logic.

Tagging for RC target triage because this only affects Migrate Drupal -- and only its tests at that.

Comments

phenaproxima created an issue. See original summary.

phenaproxima’s picture

Status: Active » Needs review
StatusFileSize
new753.86 KB

Here we go. This patch changes the fixtures thusly:

Drupal 6

  • Enabled the Content Translation and Locale modules
  • Installed the French language
  • Set the default language to English
  • Enabled translation for the Article node type
  • Ran drush updb

Drupal 7

  • Ran drush updb
  • Installed Icelandic language
  • Set the default language to English
  • Enabled translation for the Blog entry node type
neclimdul’s picture

eep, that's a bit disruptive for the couple migrate patches in the queue changing the fixture. But yeah, this is something we should probably do.

phenaproxima’s picture

They can go first. These changes are easy to re-roll.

Status: Needs review » Needs work

The last submitted patch, 2: 2594263-2.patch, failed testing.

gábor hojtsy’s picture

My understanding is this is broken out of and apparently somewhat an extension of #2225775: Migrate Drupal 6 core node translation to Drupal 8.

phenaproxima’s picture

Status: Needs work » Needs review
StatusFileSize
new762.45 KB

So it looks like running database updates changed values which the tests were depending on, and that's why all those failures happened. I have changed the tests (and, in one case, a migration) accordingly.

A couple of tests for the Drupal 7 Aggregator migration path were majorly changed, since aggregator feeds are very dynamic by nature and can change any time the fixtures are updated normally.

I had to change a migration test or two in the Comment module, because the fixture updates altered certain comment-related variables.

phenaproxima’s picture

Issue tags: -sprint
StatusFileSize
new771.49 KB

@Kazanir pointed out that one of the modified assertions MigrateCommentVariableInstanceTest was sketchy -- it was asserting something that should not have been changed in the Drupal 6 database fixture. Fixed that. Here's to not re-rolling this monster again.

Kazanir’s picture

Status: Needs review » Reviewed & tested by the community

Looks good now :thumbsup:

The last submitted patch, 2: 2594263-2.patch, failed testing.

webchick’s picture

Status: Reviewed & tested by the community » Fixed
Issue tags: -rc target triage +rc eligible

Ok, went through this patch, apart from the dump file exports (though I did scan them and yikes, Locale is a monster ;)). Some nice bug fixes in here, as well as i18n coverage for test data, yay!

This code is all confined to Migrate stuff, which is an experimental module, which I believe makes it RC eligible. It's also just test stuff, so doubly-eligible. Tagging.

Committed and pushed to 8.0.x. Thanks!

  • webchick committed ad81d25 on 8.0.x
    Issue #2594263 by phenaproxima, neclimdul, Gábor Hojtsy, Kazanir: Add...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.