Integrate Health Check & Troubleshooting plugin

[discobot]

It is an official plugin by the community started from a ticket Health Check & Troubleshooting – WordPress plugin | WordPress.org

I think that we can integrate to improve the debugging and also help the customers/users to understand the system data.

---

Read-only archive: Issues · ClassicPress/ClassicPress · GitHub

Author: Daniele Scasciafratte

Vote count: 8

Status: open

Tags:

• request-add-feature

---

Comments

That looks like it should stay plugin territory to me. There is also the Query Monitor plugin, Query Monitor – WordPress plugin | WordPress.org, which I personally use a lot. But, again, I don’t think we should attempt to bring something like that into core.

~ posted by KTS915

That plugin is intended to be merged in the core in the future, is not a debugging plugin like query monitor.
The purpose is to show as example how much ram you have for your website etc.
This information are valuable for who give support to customers and doesn’t have access to the hosting.

~ posted by Daniele Scasciafratte

I understand that this has been the eventual purpose of the Health Check plugin. But (a) feature plugins often don’t make it into core and (b) I don’t see why that makes any difference anyway. We don’t have to mimic what WP has planned.

We seem to have already developed a concept for CP of having “core plugins.” Maybe this would make another candidate for that category. But I don’t see it as part of the CP core itself.

~ posted by KTS915

Yes we don’t have to mimic WP but as developer and guy that do support to customers I have always to ask to them to install a plugin and enable for me an user with permissions or an access to the hosting to check that informations (this with exchanges by email).
Instead other cms show that information as example during the installation or in a page.

~ posted by Daniele Scasciafratte

I’d prefer this remain plugin functionality.

~ posted by John

This is only something devs will look at and therefore should not clutter the install of the average user: plugin territory in my opinion

~ posted by Pieter Bos

It is only a page that show the hosting information and all the cms do that.
Think about that common user case: user that is not highly skilled install a plugin and is getting issues. That plugin specify to have a php version or specific php extension installed or a minimum of ram. How that user can see that?
Need to access the hosting and this can be not easy to explain because every hosting has a different panel or way to show that information or don’t access to this information.
Instead with a page that show this information is easy to achieve and help the users.
Think also a case where the user don’t have admin access to install a plugin but enough to access to the dashboard and want to see this information?

~ posted by Daniele Scasciafratte

The main use case for this is regular users requesting support with a technical issue.

~ posted by James Nylen

I think this should be included in core since it’s will help a lot to know this information when you help others that aren’t developer. Then you can request screenshots of this and roll out any problems with the server or php version and so on.

This will also help when you can’t control your hosting.

~ posted by Fredrik Forsmo

Maybe located in the Tools menu? Pretty simple page, similar to the system overview seen in WooCommerce.

~ posted by Fabian Wolf

I think it would be useful an integrated ticketing system with real time chat.

~ posted by Paolo Falomo

Paolo: I think this is a separate petition! Some crossover would be possible though, like a link to create a post on the support forum with your site’s info.

~ posted by James Nylen

We seem to have already developed a concept for CP of having “core plugins.” Maybe this would make another candidate for that category. But I don’t see it as part of the CP core itself.

I agree, it would be good to get a ClassicPress plugin going for this. Forking the WP health check plugin to a repo at ClassicPress Research · GitHub would be a good start.

If you’re interested in doing this, DM me on Slack and I’ll get you set up.

~ posted by James Nylen

[Health Check & Troubleshooting] Reviews | WordPress.org

Seems like their “troubleshooting mode” has some issues. It would probably be a good idea to fix or remove that feature.

~ posted by James Nylen

Plugin.

~ posted by James Walker

[joyously]

@discobot

Seems like their “troubleshooting mode” has some issues. It would probably be a good idea to fix or remove that feature.

The Troubleshooting mode is the best part of the plugin, actually. It installs a file in the mu-plugins folder so it can load first and monitor everything else.
The rest of it has been refactored since this petition started, and merged into WP core. While I don’t think all of it is needed, the Site Health feature is a good thing for non-techy users. And it has hooks for plugins to add their own information in, much like the CP attempt at a security page.

[viktor]

This will be included in v2 re-fork.

GitHub - ClassicPress/wp-cms-experimental: ClassicPress v2.0 can be found...