💡 Site Health changes about classicpress-v2 HOT 5 CLOSED

Is it worth adding these to PR #57 or should we have a separate PR?

from classicpress-v2.

I've created a new branch that should address a lot of the list above and also some things I noted on a fresh install.

I have not yet created a PR, would suggest a check over the branch and maybe discuss the items above at a weekly meeting first.

from classicpress-v2.

@mattyrob thanks for working on this. I checked off items in this issue that your branch fixed.

One question:

• For the version number, should we display what WP version current CP version is based on? Right now, it shows Version: 2.0.0+nightly.20230518 (Latest version: 2.0.0+nightly.20230523). Or maybe create a new row, WP Version:.

from classicpress-v2.

I thought I'd addressed the clipboard issues as well and the checksums problem may well be addressed already in #79

As for the version, it is pulled from the current $cp_version from wp-includes/version.php. $wp_verision can be reported easily enough. We should avoid an API call here in my opinion as it duplicates information already available on the update page in admin.

from classicpress-v2.

• If we can include $wp_version that would be great, but I'm also OK with leaving it out. Whatever you think is best.
• For clipboard, one other item that we should consider changing is the section headings in the copied data. Such as wp-core and wp-paths-sizes. We should change it to cp-core, etc. to make sure there's no confusion.
• I will wait for #79 to merge and then will check checksums issue.
• The last thing, I think, is the hosting team wording. I would change "ClassicPress Hosting Team" to simply "ClassicPress" and the "in the team handbook" to "in the server requirements." since we don't have handbooks. I assume we can change the URL via gettext() method. I will need to create that page in the docs.

from classicpress-v2.