Improve update.php language on modules page

Created on 30 May 2009, about 16 years ago
Updated 24 July 2025, 11 days ago

Problem/Motivation

A non-Drupal user notes concerning language regarding module updates:

On the Home >> Administer >> Site building page, there's a real need for the present subjunctive.

It now says "It is important that update.php is run every time a module is updated to a newer version." That means "The following fact is important: update.php is run [ambiguous passive-tense statement] every time..."

If you want to say "You had better run it", change the "is" to a "be". Or just rephrase the whole line.

Proposed resolution

Ticket author noted:

Drupal knows when update.php needs to be run, so instead of just announcing the important fact that update.php needs to be run at the right time, it could not display the message at all when update.php does not need to be run and say "You need to run update.php right now because you upgraded modules X, Y, and Z" when it does need to be run.

Remaining tasks

We need to agree on the appropriate language for this notice.

API changes

As the patch has changes in text, any translations will need to be redone.

Screenshots

Update disabled

Before:

After:

Update enabled

Before:

After:

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

base system

Created by

πŸ‡ΊπŸ‡ΈUnited States bjaspan

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

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

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024