WordPress.org

Make WordPress Core

Opened 6 weeks ago

Last modified 9 days ago

#51976 accepted defect (bug)

Core update footer displays incorrect message when on current release -- sometimes

Reported by: afragen Owned by: afragen
Milestone: 5.7 Priority: normal
Severity: normal Version:
Component: Upgrade/Install Keywords: has-patch has-screenshots commit
Focuses: ui Cc:

Description

When the user is on the current release, but is set to receive nightlies, via the Beta Tester plugin or otherwise, the footer message will be You are using a development version... technically this is incorrect.

In wp-admin/includes/update.php core_update_footer() --
It displays because the $cur->response is development. I propose that the message be changed under these conditions to Your next update will be to a development version...

Attachments (4)

51976.diff (1.0 KB) - added by afragen 6 weeks ago.
core-update-footer.png (20.8 KB) - added by afragen 6 weeks ago.
51976.2.diff (2.1 KB) - added by afragen 5 weeks ago.
simplified footer
simple footer.png (13.5 KB) - added by afragen 5 weeks ago.

Download all attachments as: .zip

Change History (18)

@afragen
6 weeks ago

#1 @pbiron
6 weeks ago

This ticket came about from a conversation Andy and I were having last night.

Suppose I'm running 5.6 and have configured core updates to only happen for RCs (either with the Beta Tester plugin or by define( 'WP_AUTO_UPDATE_CORE', 'rc' ). As it stands, for several months the footer will show You are using a development version (5.6). Cool! which is not true (it might as well say The moon is made of green cheese. :-).

Previously, that incorrect message would only show for at most 12 hours (when the next auto-update happens and then the site would be on trunk). But now with the ability to only auto-update to betas and/or RCs it could be showing for much longer...and the string should be corrected.

51976.diff looks good to me.

The only suggestion would be to, maybe, use the logic from the Beta Tester plugin to show what the "next development version" will be based on the current settings. That is, Beta Tester (in it's Settings screen shows: version 5.7-RC1, or 5.7, whichever is released first.). Not sure if that's worth the trouble, but something to consider.

#2 @azaozz
6 weeks ago

  • Focuses ui added
  • Keywords 2nd-opinion added

Hmm, not sure 51976.diff is a good idea. The version in the footer is for the currently running code, not what it may be in the future. The settings (for the future updates) are/should be on the Updates screen. The Your next update will be to a ... version belongs there imho :)

As it stands, for several months the footer will show You are using a development version (5.6). Cool! which is not true

Right, should be fixed to show what the current version is. Also thinking, after the Updates screen changes, the word "development" may not belong there. A simple: WordPress version 1.2.3 or WordPress version 4.5-beta6 would be simpler and better imho. If it is a dev. version that will be clearly visible from the $wp_version string.

Last edited 6 weeks ago by azaozz (previous) (diff)

#3 @pbiron
6 weeks ago

Yeah, I never really seen the need for the existing wording that mentions that the current version is a dev version...the version number itself does that.

So maybe the only thing that should be different in the footer for dev versions is including the Stay updated link if $cur->response === 'development.

This ticket was mentioned in Slack in #core by afragen. View the logs.


6 weeks ago

This ticket was mentioned in Slack in #core-auto-updates by audrasjb. View the logs.


5 weeks ago

@afragen
5 weeks ago

simplified footer

@afragen
5 weeks ago

#6 @afragen
5 weeks ago

  • Milestone changed from Awaiting Review to 5.7
  • Owner set to afragen
  • Status changed from new to accepted

#7 @afragen
5 weeks ago

Remind me not to try and change the status again -- anywhere.

This ticket was mentioned in Slack in #core by afragen. View the logs.


2 weeks ago

#9 follow-up: @audrasjb
10 days ago

  • Keywords needs-refresh added; 2nd-opinion removed

Hi @afragen, thank you for putting this patch together,

I see a small i18n issue here:

/* translators: s: URL to WordPress Updates screen. */
$stay_updated = sprintf( __( 'Please <a href="%s">stay updated</a>.' ), network_admin_url( 'update-core.php' ) );
$msg          = $is_development_version ? $msg . '&nbsp;' . $stay_updated : $msg;

Indeed, RTL Locales may need to control the order of the displayed message. Using sprintf would allow them to switch the content of the $msg and $stay_updated strings 🌎😎

Last edited 10 days ago by audrasjb (previous) (diff)

This ticket was mentioned in PR #866 on WordPress/wordpress-develop by afragen.


10 days ago

  • Keywords needs-refresh removed

When the user is on the current release, but is set to receive nightlies, via the Beta Tester plugin or otherwise, the footer message will be You are using a development version... technically this is incorrect.

Simplify the footer message to Version 5.7-alpha-xxx. Please stay updated. or Version 5.6.

Trac ticket: https://core.trac.wordpress.org/ticket/51976

#11 in reply to: ↑ 9 @afragen
10 days ago

Replying to audrasjb:

Hi @afragen, thank you for putting this patch together,

I see a small i18n issue here:

/* translators: s: URL to WordPress Updates screen. */
$stay_updated = sprintf( __( 'Please <a href="%s">stay updated</a>.' ), network_admin_url( 'update-core.php' ) );
$msg          = $is_development_version ? $msg . '&nbsp;' . $stay_updated : $msg;

Indeed, RTL Locales may need to control the order of the displayed message. Using sprintf would allow them to switch the content of the $msg and $stay_updated strings 🌎😎

Updated in https://github.com/WordPress/wordpress-develop/pull/866

#12 @audrasjb
10 days ago

The PR looks good to me. @SergeyBiryukov any thought on this localization issue?

This ticket was mentioned in Slack in #core-auto-updates by afragen. View the logs.


9 days ago

#14 @audrasjb
9 days ago

  • Keywords commit added

As per todays #core-auto-updates meeting, let's move this one for commit.

Note: See TracTickets for help on using tickets.