Upgrade/Install component

Recent posts on the make/core blog

View all posts tagged upgrade-install.

Recent posts on the make/test blog

View all posts tagged upgrade-install.

187 open tickets in the Upgrade/Install component

187 open tickets defect (bug) enhancement feature request task (blessed)
5.0 1 1 0 2
5.0.1 2 0 0 0
5.1 3 7 0 0
Awaiting Review 77 34 4 0
Future Release 24 27 2 2
WordPress.org 0 0 0 1

187 open tickets. Last 7 days: +1 ticket

30 tickets that have no replies

View list on Trac

  • #28300  Two issues in the code for auto-uploading to subfolders
  • #28845  Better error messages when uploading theme as plugin and vice versa administration
  • #32652  Use `ignore_user_abort()` to avoid some update failures
  • #34649  Support for filtering constants and .htaccess message in network setup multisite
  • #34986  Add Upgrade Notice for Themes
  • #35707  On installation page, autocompleted password should not be visible.
  • #37130  Auto-download language packs when installing manually
  • #37341  Improvements to the list-table.css (breaks the plugin info popup)
  • #37850  Auto-scroll to error notice on failed inline updates (plugins/themes) ui javascript
  • #38084  Fix Inconsistency Theme and Plugin Update Process When No Package Found ui administration
  • #39364  Introduce a trigger to handle a custom queue job and run them javascript administration
  • #39459  Database upgrade is triggered on AJAX request
  • #40006  $response var in comments not an array but an object docs
  • #40094  Fatal error during update WordPress
  • #40326  One Click Install Problems with WordPress 4.7.3
  • #40873  Fatal Error from class-wp-ajax-upgrader-skin.php file
  • #41241  questioning for sftp-hostname while update does not accept final slash ui
  • #42307  Installing WP in Subfolders and https Issue
  • #42448  Add 'upgrader_pre_unpack' hook
  • #42923  Add new Docs to WordPress upgrade/install classes docs administration
  • #43503  Problematic handling of folder name when using upload to add a new theme and problem with delete when forder name have a version number in filename.
  • #43916  Auto update translations when the respective plugin/theme is updated
  • #44032  Use random_bytes() for generating keys and salts
  • #44418  fs_unavailable while auto-updating plugins
  • #44546  Missing function description. docs
  • #44596  Welcome page text is repetitive administration
  • #44629  UI Add scrollbars for webkit on Update Plugins ui
  • #44804  pretty_permalinks capability may not be detected correctly during a fresh install on a server without mod_rewrite
  • #44895  Outsource network option handling from `populate_network()` to a new `populate_network_meta()` multisite
  • #44896  Introduce new `populate_site_meta()` function multisite

14 tickets slated for 5.1

View list in Trac

  • #39309  Secure WordPress Against Infrastructure Attacks
  • #40470  WordPress installation steps – button press differences ui accessibility
  • #42008  Show warning that usernames can't be changed administration
  • #42133  Add filter to emails sent by wp_new_blog_notification() multisite
  • #43301  wp_maybe_auto_update action is missing a docblock docs
  • #44619  Colorize plugin card compatibility icons
  • #44767  dbDelta allow spaces between column names and between lines
  • #44893  Add support for an optional `$options` parameter to `populate_options()` multisite
  • #44895  Outsource network option handling from `populate_network()` to a new `populate_network_meta()` multisite
  • #44896  Introduce new `populate_site_meta()` function multisite
  • #45073  Upgrading to 5.0 and handling the Gutenberg plugin
  • #45123  Deactivate Gutenberg feature plugin upon upgrading to 5.0
  • #45151  Convert 'Sample Page', 'Hello World', and 'Privacy Policy' to block content
  • #45270  5.0 Upgrade – add an information message for Assistive Technologies users accessibility

187 open tickets

Open bugs: 107. View list on Trac

Help maintain this component

Component maintainers:

Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.

Contributors following this component: