WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 4 years ago

#16021 closed defect (bug) (fixed)

Localization mistake in /wp-admin/network/update-core.php

Reported by: settle Owned by:
Milestone: 3.2 Priority: normal
Severity: minor Version: 3.1
Component: Upgrade/Install Keywords: has-patch
Focuses: Cc:

Description

I'm using WP NightBuild.
When I open http://localhost/wp-admin/network/update-core.php , it says that there is a new version of WP (although sometimes there is no new version), it also suggests me to update to latest nightbuild or download it manually.

But below it is written that I'm going to install 3.0.3 (latest stable version).
This mistake is only visible in non-english admin panel.

You can see the problem in screenshot
http://blog.lrytas.lt/settle/files/2010/12/screenshot1.1.png

Attachments (1)

16021.patch (1010 bytes) - added by SergeyBiryukov 5 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 @SergeyBiryukov5 years ago

I guess it's related to the update API rather than localization itself.

http://api.wordpress.org/core/version-check/1.5/ returns only current stable release.

comment:2 follow-up: @ocean905 years ago

  • Component changed from I18N to Upgrade/Install

I think this string should be hidden if you are using a development version.


it says that there is a new version of WP (although sometimes there is no new version)

Because you are using a development version.

@SergeyBiryukov5 years ago

comment:3 in reply to: ↑ 2 @SergeyBiryukov5 years ago

Replying to ocean90:

I think this string should be hidden if you are using a development version.

Created the patch for this.

comment:4 @ocean905 years ago

  • Keywords has-patch dev-feedback added

comment:5 @dd325 years ago

  • Keywords 3.2-early added; dev-feedback removed
  • Milestone changed from Awaiting Review to Future Release

Will take a look at this in 3.2

comment:6 @ocean904 years ago

  • Keywords 3.2-early removed
  • Milestone changed from Future Release to 3.2
  • Resolution set to fixed
  • Status changed from new to closed

Fixed in r18224.

Note: See TracTickets for help on using tickets.