Problem/Motivation

This is a follow-up to #2914974: Migrate UI - handle sources that do not need an upgrade.

There are modules such as Views where there will most probably never be an automatic upgrade. If we use Views as an example, the site builder needs to configure the desired views manually in D8 after the upgrade has been executed. Currently we don't have any way how a module could provide a link for further information on how to handle the upgrade when automatic upgrade is not possible.

Proposed resolution

  • Let's leave these kinds of modules in the 'upgrade path not visible' list in the Migrate Drupal UI pre-upgrade report but indicate explicitly that 'Automatic upgrade not possible'.
  • We need to have a mechanism how any core / contrib module can explicitly opt-in to this category. This is being done in #2936365: Migrate UI - allow modules to declare the state of their migrations
  • When a module opts-in to this category, it MUST provide an URL which provides further information on manual options or alternative approaches.

Remaining tasks

Evaluate if this is worth doing. Views is at the moment the only core module. It has been mentioned in multiple parts in the docs that the views need to be manually created.

User interface changes

Yes, see proposed resolution.

API changes

Additional mechanism needed how modules can opt-in to this category.

Data model changes

None.

Comments

masipila created an issue. See original summary.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
CreditAttribution: alexpott at Thunder commented

I think that we have to use the module's .info.yml file. That's where we store metadata about a module. Unless we have some way to determine this automagically.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Issue tags: +Migrate UI

Adding tag.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Title: Migrate UI - handle sources that can't be automatically upgraded » Migrate UI - handle extensions that can't be automatically upgraded

discussed in migrate meeting. let's make the title accurate.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Issue summary: View changes
Related issues: +#2936365: Migrate UI - allow modules to declare the state of their migrations
masipila’s picture

masipila CreditAttribution: masipila as a volunteer commented

Hmm, I'm trying to figure out the relations of the related issues that we have around this topic. I believe that this issue (#2932652) will not be needed and we can manage this as follows:

#2936365: Migrate UI - allow modules to declare the state of their migrations will introduce a capability to say that the upgrade status is 'complete', 'incomplete' or 'n/a' in module's .info.yml file.
#2928147: Migrate UI - add 'incomplete' migration status will add the Migrate Drupal UI handling for listing the 'incomplete' status.

Hence: Do we need this issue at all?

Cheers,
Markus

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented

@masipila, I agree. Let's keep the discussion in one place .

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Status: Active » Closed (duplicate)

This situation is addressed in #2936365: Migrate UI - allow modules to declare the state of their migrations, where it is one of the cases covered. Closing as a duplicate since that seems the best fit.