Problem/Motivation

In #2281691-148: User interface for migration-based upgrades I noted:

+++ b/core/modules/migrate_drupal_ui/migrate_drupal_ui.install
@@ -0,0 +1,16 @@
+function migrate_drupal_ui_install() {
+  $url = Url::fromUri('base:upgrade')->toString();
+  drupal_set_message(t('The Drupal Upgrade module has been enabled. Proceed to the <a href=":url">upgrade form</a>.', [':url' => $url]));
+}

So this is the only place a user is given the link to go to migrate their site. There is nowhere in the admin ui apart from the configure link on the modules page - and configure is a pretty weird label for this. I guess we should have a followup to have a think about where to put a link in the UI to the page.

This also created the odd situation of telling a user twice a module has been installed if the install form has to enable dependencies...

Proposed resolution

Add a section / link to the admin UI somewhere.

Remaining tasks

tbd

User interface changes

tbd

API changes

None

Data model changes

None

Comments

alexpott created an issue. See original summary.

alexpott’s picture

Issue summary: View changes
FileSize
40.1 KB

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

yoroy’s picture

The link ended up in a message because we were assuming the clean slate Drupal 8 setup and migrate being the one first thing you'd be doing with it. It *is* clumsy to have that link shown together with other messages.

My initial suggestion would be to show the link in the 'Development' section on the Configuration page:

Just a first stab at the wording:

Site upgrade
Import the database and files of an existing site.

We need to get clarity around using upgrade/migrate/import: #2678638: [META] Usability refinements for Migrate UI

quietone’s picture

yoroy’s picture

Issue tags: +ux-workflow
Bojhan’s picture

Shouldn't this be triggered from a reports page? Instead of /config?

yoroy’s picture

Discussed this a bit with @Bojhan. First thing that stands out is that the message is not persistent. It probably should be because this is something you want to do as the very first thing for that new site your migrating into.

I think I agree with a place in Reports somewhere. We thought this workflow comparable to the one in update.php: a wizard outside of the "admin" space.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.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’s picture

Let's gather UX issues in one META.

maxocub’s picture

Status: Active » Closed (duplicate)

This is a duplicate of #2701795: Provide menu links for Drupal Upgrade UI pages (or the other way around) but there's a patch being worked on in this other issue, so let's move the discussion there.