Problem/Motivation

Currently, the plan is that the UI for upgrades to Drupal 8 from Drupal 6/7 will be initially developed in contrib, to be pulled into core when "ready" (a decision will be made before RC whether it will be made available in 8.0.0). This UI is under development as migrate_upgrade, and at Drupalcon Austin Bojhan and webchick sat down with me to review the current state of that effort. From that session came a punchlist of suggested changes to the UI as it is now. I'll be adding those issues in the sandbox as children of this meta issue - the meta is here in core for visibility, since this work will eventually end up in core. Note that many of these will be Novice issues, for those looking to get started contributing.

For historical background - previous discussion on the UI leading to its current implementation - see #2200379: Upgrade UI.

How to find upgrade page

Appearance/layout of upgrade page

Workflow

Feedback

Comments

mikeryan’s picture

mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

For context, attached are screenshots of the interface as reviewed with Bojhan and webchick - all the current child issues are relative to this version of the UI.

mikeryan’s picture

Issue summary:View changes
mikeryan’s picture

Issue summary:View changes

That's it, all the known child issues at this time have been added.

mikeryan’s picture

So, out of all these child issues, the biggest one is #2282021: Consolidate upgrade process to one form/one click. I'm thinking of simplifying it even further, narrowing the scope of the migrate_upgrade functionality to just a one-click full configuration-and-content import (or maybe allowing a configuration import and subsequent content import). Please weigh in at #2282021: Consolidate upgrade process to one form/one click.

Thanks.

benjy’s picture

Would be nice to have an update on this issue of the current state of the UI, big outstanding issues etc.

mikeryan’s picture

Issue summary:View changes

Added context issue.

mikeryan’s picture

Sorry I missed that question - basically, the UI has been working to the extent the underlying framework has for several months, with occasional chasing-HEAD breakage. I haven't tried it for a few weeks so it might well be broken at the moment, but catching up with recent core changes should take care of that. The open issues aren't really major - either cleanup/improving reuse, or providing more/better feedback - the biggest thing I think is the context issue. Should the migration readiness assessment being discussed be integrated with this upgrade form, or separate? Should it be in contrib - in migrate_plus, or perhaps coder_upgrade?

benjy’s picture

Also, after talking with webchick I thought i'd do an initial review, i forked migrate_upgrade into a sandbox and i've done some general clean-up here: https://www.drupal.org/sandbox/benjy/2448261

@mikeryan, not sure if you want me to post it into one big patch in the migrate upgrade issue queue or if you want me to break it up. The diff is here: http://privatepaste.com/458f93e589

Also, I can confirm, all is working with HEAD as of the last day or two.

mikeryan’s picture

I would like to see it broken up, I see a few different things going on there it'd be easier to review separately:

  1. Database driver setup refactoring.
  2. Version detection changes.
  3. Batch results logging.
  4. Miscellaneous rearrangement and simple coding standard stuff (e.g., use of $this->t()).

On a quick once-over I have some comments/questions, but it'll be easier to discuss in more specific issues.

Thanks!

benjy’s picture

Sorry, I should have mentioned there is an overview on the sandbox overview page.

iantresman’s picture

Just to add my support for a user interface (UI). Most people running Drupal sites are not programmer/developers, and without a UI, will find migration very difficult, if not impossible.

I envisage an option to specify a Drupal 6/7 mySql hostname, username and password, and the migration system to investigate what may be migrated, followed by an option to select data to migrate.

I believe the node import module provides a UI to import/migrate from CSV files.