Problem/Motivation

There's no explicit description/motivation shared why we we ignore certain paths by default for readiness checks.
The text about "no update available at this time" could be improved so there are fewer questions.

Proposed resolution

Improve the wording and workflow for these things

Remaining tasks

User interface changes

Updated UI:

When an updated version isn't available

When a security update is available.

API changes

Data model changes

Release notes snippet

Comments

heddn created an issue. See original summary.

heddn’s picture

Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new154.35 KB
new58.17 KB
new36.05 KB
new2.4 KB
heddn’s picture

StatusFileSize
new2.64 KB

Here's a 7.x backport patch.

mherchel’s picture

Status: Needs review » Needs work

Looks much better! IMHO, I would change the word "handicapped" to "limited".

I would also bold the word "not" in "Database updates are not run after an update. When I installed this module, I kind of skimmed over this, and didn't realize this fact.

Thanks so much :)

heddn’s picture

Status: Needs work » Needs review
StatusFileSize
new1.53 KB
new3 KB
heddn’s picture

StatusFileSize
new4.28 KB
new1017 bytes

  • heddn committed def6907 on 8.x-1.x
    Issue #3093072 by heddn: Improve UX of settings page
    
heddn’s picture

Version: 8.x-1.x-dev » 7.x-1.x-dev

Fixed/pushed to 8.x. Next up, 7.x.

heddn’s picture

StatusFileSize
new3.16 KB
mherchel’s picture

🎉 Thanks!

  • heddn committed 6112d7b on 7.x-1.x
    Issue #3093072 by heddn, mherchel: Improve UX of settings page
    
heddn’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.