- First commit to issue fork.
- last update
about 1 year ago Composer require failure - last update
about 1 year ago Composer require failure - 🇧🇪Belgium tijsdeboeck Antwerp 🇧🇪 🇪🇺 🌎
The previous MR version only stored the translated 'name' base field. Added support for custom fields in translations.
- Status changed to Needs review
about 1 year ago 1:01pm 27 August 2023 - last update
about 1 year ago Composer require failure - last update
about 1 year ago 5 pass, 1 fail - 🇫🇷France tostinni
Is there any reason to having added this line in
importTaxonomiesForce()
@@ -697,6 +726,7 @@ class TaxonomiesController extends ControllerBase { $entity_properties = [ 'vid' => $vid, + 'tid' => $taxonomy['tid'], 'langcode' => $taxonomy['langcode'], 'name' => $taxonomy['name'], 'description' => [
Because it will break when importing taxonomies in a site where newer terms have been created.
As this patch currently only works with force, I recommend to use it with #3271724: Force import for taxonomy deletes all terms regardless if they're managed by structure sync →
- First commit to issue fork.