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.Problem/Motivation
We are now displaying various sources of data:
- Environment check
- Custom installed and uninstalled projects with local scanning output (and optionally rector output)
- Contrib installed and uninstalled projects with local readiness, available update data and local scanning output (and optionally rector output)
We've introduced the local Drupal 9 readiness and remote Drupal 9 readiness as data points in #3150603: Display local and remote Drupal 9 readiness status (based on update and info.yml info). Now that more and more local projects are just ready and more and more remote releases are just ready, the local scanning is great but should not be the primary driving force of readiness. If a local version is Drupal 9 ready, there is not necessary anything to do with it anymore. If a remote version is ready, updating to it is the action to take, not doing anything locally (not even to check it).
We are currently displaying all the data and assuming people will make the "logical" decisions based on the data. But we can just go and tell them what is the logical decision we think based on the data.
Proposed resolution
Introduce an action oriented summary about tasks to do and then pages with explanations for each task at hand. We can move the overall overview / form to an advanced UI then. We need to keep the ability to take other decisions that we did not necessarily suggest, because circumstances may vary.
Initial mockup separating things people should do within this UI (analyze), outside of this UI (act) and things that we consider done (relax). There are some things we can analyze without the user doing anything, particularly local project readiness. But without updates information, we may send people into a rabbit hole they should not go into for example.
Detailed parts of all the things linked will need to be planned out as well. Feedback welcome.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | Screenshot_2020-08-14 Upgrade status example.png | 481.29 KB | Gábor Hojtsy |
| Screenshot 2020-06-22 at 15.45.35.png | 107.34 KB | Gábor Hojtsy |
Comments
Comment #2
Gábor HojtsyComment #3
Gábor HojtsyComment #4
Gábor HojtsyComment #5
xjmIn the screehshot at the top, "9 ready" makes it sound like 9 (function calls) or something are ready. Grammatically, there should be a hyphen: "9-ready".
But I think that's not the actual information the user wants. They want to know if one of these things is true:
"Drupal 9 update available: [link]"
"Drupal-9-compatible version already installed"
Making it an advanced UI seems sensible.
I don't understand the ote about "Remove 3 unused projects" thing though. I thought we'd already fixed it so the info parser didn't throw an exception based on the info files of unused projects in the codebase. What does that mean?
Comment #6
Gábor Hojtsy@xjm: the first screenshot is a work in progress on the 3.x branch, it will be even more columns in the final advanced version probably.
Re the remove unused modules that would be about not suggesting you go about updating your foo_extras project code locally to be Drupal 9 compatible when you actually never installed any part of foo_extras. We would suggest you get rid of it instead.
Comment #7
Gábor HojtsyWith the last child issue at #3165287: Integrate environment checks overall result in summary landing, I think this is pretty much complete. Plan to post a blog post about this on Monday to gather more feedback. Test are still not at all passing, and I'll work on those once we settle on whether this UI is good for the 3.x branch :)
Comment #8
Kristen PolAdding related issue as some feedback was added here: #3165529: Various feedback on 8.x-3.x
Comment #9
Gábor HojtsyThis is now all in the 3.x alphas. Most of Kristen's feedback was also resolved, so going to close this.