Site Health component

Recent posts on the make/core blog

View all posts tagged site-health.

51 open tickets in the Site Health component

51 open tickets defect (bug) enhancement feature request task (blessed)
1 0 0 0
5.4 5 7 1 1
Awaiting Review 12 15 0 0
Future Release 4 3 0 2

51 open tickets. Last 7 days: +2 tickets

5 tickets that have no replies

View list on Trac

  • #48199  Check for whether the themes directory writable is incorrect when the current theme is symlinked into the theme directory
  • #48612  critical error on website. please check admin email for instructions.
  • #48929  Recovery mode page references checking your site admin email, even in Multisite multisite ui-copy
  • #48948  Fix the Site Health template to produce valid HTML
  • #49188  Add a check for tables structures.

14 tickets slated for 5.4

View list in Trac

  • #44592  Add support for required WP and PHP versions to themes
  • #46910  Allow wp_die to called after html has started output
  • #47043  i18n: Merge similar translation strings – database related strings administration
  • #47606  Display Site Health score on Dashboard ui
  • #47880  Extend unit tests for Site Health component.
  • #47985  Site Health: log errors to public file
  • #48105  Move Site Health async checks to a REST API endpoint rest-api
  • #48333  Show success notice when the admin verification screen is "snoozed" ui administration
  • #48390  Improve the Servehappy dashboard notice wording
  • #48491  [Theme compatibility] WP/PHP compatibility tests for single site theme updates/activation administration
  • #48507  [Theme compatibility] WP/PHP compatibility tests for multisite updates administration multisite
  • #48578  Change health check accordion appearance on focus ui accessibility administration
  • #48716  Improve wording for PHP update warning // Part 2 ui-copy
  • #48964  version 5.3.1 – Critical Errors Updating Plugins & Themes

51 open tickets

Open bugs: 22. 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: