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.Postponed on #2936365: Migrate UI - allow modules to declare the state of their migrations
Problem/Motivation
This is a follow up to #2922701: Migrate UI - refer to modules and add help text which itself is a followup to #2914974: Migrate UI - handle sources that do not need an upgrade to work on improvements to the UI text. It started from a migrate meeting where it was decided to have 3 categories of module status on the page as well as improvements to the help text.
The Migrate UI 'Upgrade analysis report' lists modules is two categories, those with an available upgrade path and those that are missing an upgrade path. A module with one migration will be listed as having an available upgrade path even if the module really needs more than one migration. Because of that the use may expect a module to upgrade when in fact it won't. And contrib needs a way to inform migrate of its migration status. Using hooks or events was discussed but no decision was made.
Proposed resolution
Create a third category, Incomplete, to identify modules where some of the necessary migrations are working. And use the warning icons for these modules.
Do this in a way, so that contrib modules could override this status if they provide a migration path. This is being done in #2936365: Migrate UI - allow modules to declare the state of their migrations
Remaining tasks
Write a patch, review, commit
User interface changes
Yes, to the Migrate Drupal UI.
API changes
N/A
Data model changes
N/A
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2928147-3.patch | 7.98 KB | quietone |
Comments
Comment #2
quietone CreditAttribution: quietone at Acro Commerce commentedComment #3
quietone CreditAttribution: quietone at Acro Commerce commentedHere is a start. It still needs tests but is lacking a way to add modules to the new 'incompleteUpgradePaths' list. It works find locally if I add modules to that array in MigrateUpgradeForm. Setting to NR so see if this breaks anything.
Comment #5
quietone CreditAttribution: quietone at Acro Commerce commentedTagging and update IS to show that an issue exists for one of the propopals.
Comment #6
quietone CreditAttribution: quietone at Acro Commerce commentedDiscussed in migrate meeting. This will be simpler to test when #2932652: Migrate UI - handle extensions that can't be automatically upgraded is resolved.
Postponing
Comment #7
masipila CreditAttribution: masipila as a volunteer commentedChanged the issue this is postponed on.
Comment #9
quietone CreditAttribution: quietone at Acro Commerce commentedThe work being done in #2936365: Migrate UI - allow modules to declare the state of their migrations has moved away from having three sections in the Review Page. So, closing this as outdated.