Too many migration issues, many of which look overlapping or duplicate. It looks like a lot of them originated as one-off solutions without researching or relating to what issues are already there. It's a mess.
As maintainer with no deep knowledge about the migration plugin system details, i have no idea which of the issue is thorough, which only a bandaid, and which supplements or sabotages which other.
Adding all as child of this, and postponing all, unless someone(tm) sorts things out and provides a thorough reasoning what's reasonably next.
Show commandsStart 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:
changes, plain diff MR !53
Comments
Comment #2
geek-merlinComment #3
geek-merlinComment #4
geek-merlinComment #6
anybodyI did some cleanup in the children issues and closed clear duplicates.
As all left issues are very closely related and some of them even share the same code changes, as an experiment, I'll create an issue fork here, combining the changes in one, so we can compare the results before / after the changes more easily.
This will hopefully make it easier to decide where and how to proceed, currently that's indeed quite complex!
Comment #8
anybodyNow that #3294481: [PP-2] Update MigrationHelper and add hook_field_migration_field_widget_info() to add widget mappings. is out of scope, as it depends on two WIP core issues, we can remove that part and set that issue postponed [PP-2] to solve that separately!
Comment #9
anybody@geek-merlin: I think we can close this meta issue now:
So the issues are ready to be fixed or at least for further work. No more overlappings or duplicates!
I'll close the issue fork we used for testing the combination of all proposed patches, which worked as expected and helped to identify relation.
Comment #11
geek-merlinDid not look into details. Excellent cleanup work. Crediting and closing.