WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 5 years ago

#11739 closed feature request (fixed)

Add changelog or version info link to wp-admin/update-core.php

Reported by: dtoj Owned by: nacin
Milestone: 3.0 Priority: normal
Severity: normal Version: 3.0
Component: Upgrade/Install Keywords:
Focuses: Cc:

Description (last modified by dd32)

From http://llbit.se/?p=398

How should I know if I really want to apply an update if I can’t see what it changes? Sure some people might be OK with changing their software without knowing what changes are being made, but I am not.

Changelogs and release notes are important. The user needs to be able to see them, and they should be available before installing any kind of update. If it’s a bugfix update, I want to know which bugs were eliminated. If it’s a security update, I want to know which vulnerabilities were fixed. If it’s a feature update, I want to know which features have been added!

The most logical thing would be to have a link to the changelog right next to the “Upgrade Automatically” button in Wordpress.

Attachments (2)

wp-admin_update-core.diff (930 bytes) - added by dtoj 6 years ago.
wp-admin_includes_update.php (716 bytes) - added by dtoj 6 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 follow-up: @dd326 years ago

  • Description modified (diff)

Quick comments, That HTML doesnt seem like its valid, ...string...<p>...string...</p> the first isnt in a paragraph?

comment:2 in reply to: ↑ 1 @dtoj6 years ago

Replying to dd32:

Quick comments, That HTML doesnt seem like its valid, ...string...<p>...string...</p> the first isnt in a paragraph?

You are correct. The string $message is used in the context

echo '<p>';
echo $message;
echo '</p>';

so $message should be on the form 'line1</p><p>line2'.

I'll upload a new patch.

@dtoj6 years ago

comment:3 @hakre6 years ago

I like the idea to have a link to the changelog.

Related: #11666

comment:4 @dtoj6 years ago

  • Milestone changed from Unassigned to 3.0

comment:5 @janeforshort5 years ago

The idea with the GUU was that when an upgrade was available, text would display that told users why they should upgrade, giving that top few features, and a link to the Codex if they wanted more information.

comment:6 @nacin5 years ago

  • Owner set to nacin
  • Status changed from new to accepted

I really like this. Can we add it to all relevant upgrade strings across core? There's potentially up to a dozen of them. Having all of those in the same patch would be great.

comment:7 @nacin5 years ago

(In [13250]) Add links to the codex changelog in update notification strings. props dtoj, see #11739

comment:8 @nacin5 years ago

  • Resolution set to fixed
  • Status changed from accepted to closed

I avoided wp-admin/includes/update-core.php, as that file is actually copied from a downloaded installation to the current installation, which means new strings aren't available when it is seen. I imagine we can eventually use the same "You cannot upgrade" strings found in wp-admin/update-core.php and upgrade.php.

Closing as fixed.

Note: See TracTickets for help on using tickets.