Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
The source plugin for d6_taxonomy_term_localized_migration gets all the terms but does not filter out the ones not using a localized vocabulary.
This was discovered while working on #3082211: Migrate UI upgrade tests should provide the complete log because, for unknown reasons, Upgrade6Test produces a different number of error messages locally vs drupalci.
Steps to reproduce
Proposed resolution
Add a condition to the query to only get translations of type 'term'.
Remaining tasks
Patch
Review
Commit
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#4 | 3193189-4.patch | 3.52 KB | quietone |
#3 | 3193189-3.patch | 21.79 KB | quietone |
#3 | interdiff-2-3.txt | 3.05 KB | quietone |
#2 | 3193189-2.patch | 18.52 KB | quietone |
Comments
Comment #2
quietone CreditAttribution: quietone as a volunteer commentedAnd the patch. This was included in a patch in the related issue, #31 and all tests pass.
Comment #3
quietone CreditAttribution: quietone as a volunteer commentedThe source plugin test should be updated as well.
Comment #4
quietone CreditAttribution: quietone as a volunteer commentedThe first thing I did was compare with the Drupal7 version - but I missed the difference. It is just one line in the query method that was missing,
$query->condition('i18n.type', 'term');
This is a better solution.
Comment #5
quietone CreditAttribution: quietone as a volunteer commentedComment #6
quietone CreditAttribution: quietone as a volunteer commentedMore accurate title
Comment #7
quietone CreditAttribution: quietone as a volunteer commentedComment #8
jibranI can confirm that the fix is the same as
d7/TermLocalizedTranslation.php
so RTBC.Comment #11
quietone CreditAttribution: quietone as a volunteer commentedTests are passing on 9.3.x, restoring RTBC.
Comment #14
catchCommitted/pushed to 9.3.x and cherry-picked to 9.2.x, thanks!
Doesn't apply to 9.1.x, but there's a short window to get bugfixes into 9.1.x anyway, so just marking fixed.