Make WordPress Core

Opened 4 years ago

Closed 3 years ago

#42291 closed enhancement (wontfix)

Filename "update-core.php" and Heading "WordPress Update" inaccurate/redundant

Reported by: pixelverbieger Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Text Changes Keywords:
Focuses: Cc:


The page under "wp-admin/update-core.php" does not only show available core updates but also those for plugins, themes and translations.

Therefore the file name and the heading on this page are misleading and might be changed to "update.php" and "Updates" – which equals to the menu entry on the left ;)

This also effects the link "Return to WordPress Updates page".

Change History (2)

#1 @pixelverbieger
3 years ago

  • Summary changed from Filename "update-core.php" and Heading "WordPress Update" somehow misleading to Filename "update-core.php" and Heading "WordPress Update" inaccurate/redundant

… or, in other words: the mentioned update page does not only update WordPress, but also other components – and it should be obvious that we aren't updating Firefox, Photoshop or macOS on this page … so lets' give it the name it deserves, "Updates".

#2 @pento
3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Thank you for the suggestions, @pixelverbieger!

Interestingly, this file is called update-core.php, because update.php used to contain all of the update functionality, but the core-specific bits were split into their own file. It's only in relatively recent years that update-core.php has been expanded to include UI for plugins and themes.

While I appreciate the desire to fix an incorrect filename, there's a significant risk to doing so, as it would likely break a lot of existing tools. This is also why upload.php shows the media library list, for example.

On your second suggestion, the "WordPress Updates" title is correct: the page is about updates for WordPress, not just updates of WordPress. The content of the page itself gives the context to explain the difference.

Note: See TracTickets for help on using tickets.