- 🇳🇿New Zealand quietone
Seems more suitable to the 'database update system' component.
The report at the end of the drupal database update process is very confusing.
It asks users to look to see if there are any errors reported on the page, and assume the update was successful if there are not. The could make a user nervous (for real site), even when the there are no failures listed below or nothing logged.
Originally reported by @tsvenson on #2341575-42: [meta] Provide a beta to beta/rc upgrade path →
Detect whether any errors occurred during the update process and show one of two different messages.
The amount of text on this screen will be reduced and easier to understand.
None
None
Needs work
9.5
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
The change alters the user interface, so before and after screenshots should be added to document the UI change. Make sure to capture the relevant region only. Use a tool such as Aviary on Windows or Skitch on Mac OS X.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Seems more suitable to the 'database update system' component.