Simplify text describing updates in the site status report

Created on 29 October 2017, about 7 years ago
Updated 12 September 2023, about 1 year ago

Problem/Motivation

This is a follow-up to #2545520: The same link "available updates" links to two different pages in the same paragraph when there is a problem checking available updates . The following changes were considered out of scope for that issue, especially since changing the text would break existing translations.

See the screenshots for various cases listed in Comment #122 on that issue. Also see Comment #124 .

1. When there is a problem checking for updates (to Drupal core or to contributed modules and themes) the status report includes this text from _update_message_text():

There was a problem checking [available updates] for Drupal.

or

There was a problem checking [available updates] for your modules or themes.

(with the link going to /admin/reports/updates).

We considered using the same text in both cases, removing " for Drupal" or " for your modules or themes".

Proposed resolution

(a) Status Report:

(b) Status Report - no update manager access:

(c) Updates available email:

Remaining tasks

Review how this will affect the Status report and the e-mail generated by update_mail().
Use the simpler text for both cases.
Add before/after screenshots to the issue summary

User interface changes

Before

Status report
TBA
email
TBA
.

After

Status report
TBA
email
TBA

API changes

None.

Data model changes

None.

📌 Task
Status

Needs work

Version

11.0 🔥

Component
Update 

Last updated about 4 hours ago

  • Maintained by
  • 🇺🇸United States @tedbow
  • 🇺🇸United States @dww
Created by

🇺🇸United States benjifisher Boston area

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Novice

    It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

  • Needs usability review

    Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024