Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This issue was originally created as a META to focus on improving the migrate UI but became side tracked after I posted a patch to implement some suggestions by yoroy. Work continued on that patch, and yoroy's call for a review (#13) of the UI was not done. Let's go back and review the UI and get agreement on the work to be done, creating child issues as needed.
That means that the patch here is postponed until there is agreement on that work and move it to a child issue.
Next Steps
Add up to date screen shotsReview the screensMake child issues- Agree on changes listed:
- #2905222: Migrate UI: Initial Screen UX improvements
- #2905227: Migrate UI: Improve 'Review Upgrade' page UX
# Screenshots (9/24/2017 after source module patch)
Original Issue Summary
Screencast showing migrate workflows: https://drive.google.com/file/d/0B6xsrc5BVkagMjdrTHZ3R2o0YXM/view
Review & note further user interface refinements here…
| Comment | File | Size | Author |
|---|---|---|---|
| #42 | screen_6.png | 22.81 KB | heddn |
| #42 | screen_5.png | 12.74 KB | heddn |
| #42 | screen_4.png | 89.14 KB | heddn |
| #42 | screen_3.png | 222.01 KB | heddn |
| #42 | screen_2.png | 59.07 KB | heddn |
Comments
Comment #2
yoroy commentedComment #3
yoroy commentedUpgrade an existing Drupal site (source site) by importing it into a new and empty Drupal 8 install (target site). See the upgrading handbook for more detailed information.
1. Back up the database for this target site. The import process will remove all existing configuration.
2. Make sure that the host for this target site can access the database for the source site.
3. If the source site has private files that need to be imported, a copy of the files directory must be accessible on the host this target site is on.
4. Enable all modules on this target site that are enabled on the source site. For example, if you have used the book module on the source site then you must enable the book module on this target site for that data to be available on this site.
5. Put this target site into maintenance mode.
Importing can take a long time. It is better to import from local copy of the source site instead of directly importing from the live site.
---
Above is already a bit of rewrite.
Comment #4
xjmWe should also fix this:
https://www.drupal.org/files/issues/Are%20you%20sure%3F%20%7C%20Hojtsy.h...
Are you sure? ARE YOU SURE?? ;)
Comment #5
quietone commentedPatch with yoroy's suggestions in #3. I don't get the two 'are you sure' messages, so no fix for #4. It is already fixed?
Comment #6
quietone commentedComment #8
xjm@quietone, well "Are you sure?" is also not a helpful title. :) So hopefully we can improve the string based on feedback from@yoroy or others. But @Gábor Hojtsy took that screenshot today I think.
Comment #9
quietone commented@xjm, yes, I wasn't looking at 'Are you sure' post a migration.
This patch should just fix the earlier error.
Comment #10
quietone commentedComment #12
heykarthikwithuComment #13
yoroy commentedYeah, there's more than what I wrote in #3. The patches are appreciated, but would be good to first do a review of all the screens.
The screenshots I took are from Gabors screencast from a couple of weeks ago: #2281691: User interface for migration-based upgrades so may not be the most up to date version of the UI. If the UI has changed in the mean time we first need new screenshots :)
Comment #14
heykarthikwithusure :)
Comment #15
gábor hojtsyCurrent screenshots. Note that you don't actually need any D6 site. I shot these on simplytest.me. It will prefill your D8 DB credentials (feature of simplytest.me) and not find any upgrade of course matching Drupal 8 as source. All the screens are screenshottable anyway.
Note that there are two are-you-sures, one when you are about to perform an upgrade and one when you are about to roll back. The double are you sure screenshot was made with Bartik. It may be that Bartik and Seven display questions differently but its more likely minor string changes were made, so now it says "Upgrade analysis report" instead of the second are you sure, which I am not sure makes sense in that context either...
Comment #17
xjmSince the Migrate UI is alpha-experimental and new as of 8.1.x, this and other issues for it can be committed during the 8.1.x beta.
Comment #18
mikeryanNote I've closed a bunch of old upgrade UX issues in the migrate_upgrade queue and linked them here - there may be some past discussions over there which are still relevant.
Comment #19
yoroy commentedThank you @mikeryan.
Comment #20
yoroy commentedComment #21
xjmComment #22
quietone commentedThis patch removes the text 'upgrade analysis report' and changes 'Are you sure' to 'Are you sure you want to perform the upgrade'.
Since incremental migrations have been removed, there is no second 'Are you sure?'.
Comment #23
quietone commentedIt helps to upload the patch.
Comment #25
quietone commentedForgot to update the test. Not sure about the other errors, they seem to be unrelated.
Comment #29
mikeryanComment #30
yogeshmpawarI have rerolled the patch for 8.2.x version.
Comment #31
manuel garcia commentedComment #32
heddnCan we update the IS with next steps and what this meta task plans to accomplish?
Comment #33
heddnI don't think this is a meta task, but we still need next actionable steps.
Comment #34
mikeryanLet's get an IS update before proceeding.
Comment #35
quietone commentedComment #36
ifrikI might have lost the overview of the scope of this issue, so appologies if this should be somewhere else.
Currently - in 8.3 - there seems to be only one "Are you sure?" page.. The user gets to that after clicking a button "Review upgrade" so a consistent page title would simply be "Upgrade review".
Comment #38
mikeryanComment #40
heddnReviewed in migrate weekly meeting. We *need* an IS update.
Comment #41
quietone commentedAll right, time to sort this one out.
Comment #42
heddnReviewed this with @jjpoole today. We've updated the IS and added screenshots. Next step is to review the updated screenshots, any earlier feedback and open up child issues.
Comment #43
webchickThis would be a great thing to take to the weekly usability meeting in #ux on drupal.slack.com. It happens every Tuesday at 2pm Pacific time (https://time.is/compare/vancouver for your timezone). It's a meeting dedicated to getting design/usability feedback on core patches.
Comment #44
heddnComment #45
webchickI believe this is the only issue stopping Migrate UI from being marked stable, so tentatively tagging as a Migrate critical. Sorry if this is not the right approach.
Comment #46
yoroy commentedI feel bad about this issue because my review was all over the place and I never did the breakdown into separate, actionable issues. That is indeed what to do now.
Comment #47
heddn@yoroy and others, I did a walk through of these pages in #42 with a UX designer I work with at Acro Media. As a result, we considered that #2905222: Migrate UI: Initial Screen UX improvements and #2905227: Migrate UI: Improve 'Review Upgrade' page UX should be opened as follow-ups. If you agree/disagree, feel free to add comments in those child issues. I've also updated the IS to reflect those two tasks as the actionable next steps.
Comment #48
jjpoole commentedYes, the process as a whole is pretty solid and straightforward. Mostly it just need some clear language (text, labels, buttons, etc). Those two child issues should get us to a good position.
Comment #49
heddnThe children of this are now officially the blockers for marking this module beta and eventually stable: #2905491: Mark Migrate Drupal UI as stable
Comment #50
heddnThe children of this issue are blockers to #2905491: Mark Migrate Drupal UI as stable
Comment #51
xjmThe individual children of this issue should be marked as critical, but the plan for tracking them can be major. Per @heddn we have all the actionable steps split out into issues now.
Comment #52
quietone commentedUnassigning myself.
Comment #54
heddnAll children issue except for #2853708: Make a status report page for Migrate UI with links to incremental migrations/rollbacks/etc. are closed. I'm going to mark this as fixed as this is no longer an active meta. Thanks everyone for their fine work on UX improvements.