WordPress.org

Make WordPress Core

Opened 3 weeks ago

Last modified 3 weeks ago

#50389 reopened enhancement

Improve support for site health issues in WordPress

Reported by: evapparao Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.2
Component: Site Health Keywords: 2nd-opinion
Focuses: docs Cc:

Description

after we upgraded to wordpress 5.4, we are getting these performance issues. this is what was mentioned in the site health report. can you pl tell us how to fix them?

PHP modules perform most of the tasks on the server that make your site run. Any changes to these must be made by your server administrator.

The WordPress Hosting Team maintains a list of those modules, both recommended and required, in the team handbook (opens in a new tab).

Warning The optional module, imagick, is not installed, or has been disabled.
Warning The optional module, zip, is not installed, or has been disabled.

Change History (8)

#1 @audrasjb
3 weeks ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Severity changed from major to normal
  • Status changed from new to closed

Hi there, Welcome to WordPress Trac and thank you for opening this ticket,

Please note that this Trac is used for WordPress core software Core development, not for individual support questions. You should open a question on WordPress support forums: https://wordpress.org/support/welcome/

Thanks!

#2 follow-up: @johnbillion
3 weeks ago

  • Component changed from General to Site Health
  • Focuses docs added
  • Keywords 2nd-opinion added
  • Milestone set to Awaiting Review
  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Type changed from defect (bug) to enhancement
  • Version set to 5.2

While the individual issues are indeed up to @evapparao to address, I think the Site Health screen could do a better job of providing information about how to address issues that it reports.

Currently several reported issues are a dead end, while some have links to support articles.

I think we should aim to have a corresponding support article for every site health issue.

Thoughts?

#3 @audrasjb
3 weeks ago

Good point @johnbillion. I think this could be a dedicated page on HelpHub.
I'll point out this concern during today’s Docs team meeting.

#4 follow-up: @audrasjb
3 weeks ago

To elaborate my thoughts: I think a "Site health issues" HelpHub page would be easier to link on site health screen and easier to maintain. If each site health issue is documented in a single page, we just need to maintain this specific page when something is modified on site health feature :)

#5 in reply to: ↑ 4 @johnbillion
3 weeks ago

  • Summary changed from performance issues in wordprpess to Improve support for site health issues in WordPress

Replying to audrasjb:

To elaborate my thoughts: I think a "Site health issues" HelpHub page would be easier to link on site health screen and easier to maintain.

There are actually only two site health checks that link to a support article currently (I thought there were more).

I can see the value in having a central support page for all site health issues.

This ticket was mentioned in Slack in #docs by audrasjb. View the logs.


3 weeks ago

#7 in reply to: ↑ 2 @SergeyBiryukov
3 weeks ago

Replying to johnbillion:

I think we should aim to have a corresponding support article for every site health issue.

Previously: [45170] / #46734.

#8 @audrasjb
3 weeks ago

@johnbillion FYI, I raised this to the Docs team during today’s meeting, and there is an agreement concerning using a single Site health HelpHub page. I think we can probably use site-health-issues as a slug for this page.

For reference: https://make.wordpress.org/docs/2020/06/15/summary-for-docs-team-meeting-15-june-2020/

Note: See TracTickets for help on using tickets.