Having an interface to work with migrate is going to be awesome! This will lower the barrier of entry for people to use migrate. Everyone's going to be stoked.
Here's what we're looking at completing to get feeds_migrate even further off the ground. This list is by no means complete but a work in progress.
Thanks for all the help and support!
Changes needed in core and Migrate Plus in order to make further progress
We need some changes to happen in Drupal Core and Migrate Plus in order to make further progress on this project (though there is a possibility to implement workarounds, but we would prefer a good base to build on).
Changes in core and Migrate Plus are needed to:
- Fix PHP notices on several pages, so we can write tests that pass for these pages.
- Write form plugins for Migrate process plugins.
Fix PHP notices on pages
There are PHP notices when creating or editing migrations. This is because plugins in Migrate Plus don't account for the case that some configuration is not set yet. To fix that, Migrate Plus plugins should implement \Drupal\Component\Plugin\ConfigurableInterface. But before that can happen, Migrate plugin base classes should implement it first. But before that can be done, there should exist a uniform way to merge configuration in plugins first.
Further details on #3093407: Add functional test for creating/editing migrations
Create UI for each core process plugin
We need several metadata to be added to process plugins, like label and a description. This helps in displaying these nicely in the UI. We also would like config schema and config default values. These could help with creating a dynamic form and having a UI for each process plugin automatically. Note: for some process plugins we still may need to create specific forms because the UX for some might else not be great.
Further details on #3047264: [META] Build form plugins for process plugins in feeds migrate
Next steps
- Fix PHP warnings on pages:
- #2852463: Create a trait and base class to implement \Drupal\Component\Plugin\ConfigurableInterface
- #2937177: Migrate plugin base classes should implement ConfigurablePluginInterface
- Implement
defaultConfiguration()for migrate plugins in Migrate Plus (for MigrateSource plugin "url" and probably others) - #3093407: Add functional test for creating/editing migrations
- #3047264: [META] Build form plugins for process plugins in feeds migrate
- #3006045: Suggest unique selector path based on uploaded file
- #3022548: Changes are not being saved on the entity.
Future steps
These items are important but beyond our focus for the moment.
- #3011870: Should any Feeds migrate config be moved from Migrate tools to a Feeds migrate config entity?
- #3012965: Find a better way to read bundle for a migrations basic config form
- #3012966: Find the best way to read configuration from migrate plugins for migrate configuration UI
- #3012970: Should migration entities created by feeds_migrate be shown alongside migration entities in migrate_tools?
- #2958013: [META] port remaining feeds tamper plugins
- #2984386: Build working UI for csv import
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | Feeds-Migrate-issues.txt | 6.33 KB | megachriz |
Comments
Comment #2
jamesdixon commentedComment #3
jamesdixon commentedComment #4
jamesdixon commentedComment #5
jamesdixon commentedComment #6
jamesdixon commentedComment #7
irinaz commentedComment #8
jamesdixon commentedComment #9
jamesdixon commentedComment #10
megachrizIn the attached document I have written down some roadblocks that we are facing now. Issues related to this document are:
#3002360: Feeds migrate UI Basic settings part 1
#3011870: Should any Feeds migrate config be moved from Migrate tools to a Feeds migrate config entity?
Comment #11
jamesdixon commentedThanks @MegaChriz! I've created 4 issues from your list which include some direction from @heddn and added them to the roadmap:
Comment #12
jamesdixon commentedComment #13
jamesdixon commentedComment #14
jamesdixon commentedComment #15
jamesdixon commentedComment #16
jamesdixon commentedComment #17
jamesdixon commentedComment #18
jamesdixon commentedComment #19
jamesdixon commentedComment #20
jamesdixon commentedComment #21
jamesdixon commentedComment #22
jamesdixon commentedComment #23
jamesdixon commentedComment #24
jamesdixon commentedComment #25
irinaz commentedComment #26
irinaz commentedComment #27
damienmckennaAdding two core issues which were mentioned as blockers:
Comment #28
megachrizI've updated the roadmap to highlight what we need from Drupal Core and Migrate Plus in order to make progress. I added more details to #3093407: Add functional test for creating/editing migrations and #3047264: [META] Build form plugins for process plugins in feeds migrate too.
Comment #29
megachrizComment #30
chris burge commentedMigrate is being removed from core in D12 and will not be moving to contrib: #3371229: [Policy] Migrate Drupal and Migrate Drupal UI after Drupal 7 EOL.My badComment #31
heddnmigrate and migrate drupal are different. Migrate is not going away. The upgrade from previous drupals is going away. Ergo migrate drupal. But not Migrate itself.
Comment #32
irinaz commented@heddn, thanks for clarification. With new AI coding tools there is a chance that we can move forward with friendly UI for several reasons.