-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Site Status string audit #256
Comments
There will soon be an interaction between the WP version and the PHP version, as there already is some between plugin version and PHP version. Does Health Check take that into account? It doesn't seem to be reflected in these strings. |
I'm not sure I understand the question? There's a PHP version check which includes both recommended and minimum PHP versions for WordPress. |
What I mean is that older versions of WP will have one range of PHP versions that will work, and newer versions will have another range. The message about which WP version should be installed could be influenced by the PHP version that is installed, and vice versa. |
That's an added complexity that will confuse users, officially we only support the most recent major release, and that's what we'll focus on in core, and the plugin will give recommendations based on this even though it'll work for older versions of WordPress. |
Yes, so the string for WP version might be "A new version of WordPress is available. You will need to update PHP first." |
Things that may need to be added:
|
I'm walking through the suggested strings and making comments over at |
Do we need to add any string for: |
Fixed in #312 |
Thank u so much, I want to share the solution of this error (Nginx Users):
solution:
|
@stan0ne , thank you, you just saved my day 👍🏻 |
Another way is to edit the "wp-includes/rest-api.php' on line 327. method name " remove or comment this line |
For apache ? thanks. |
The Site Status does, at this time, 16 different tests to check for common problems, and provides actionable tasks when possible here.
With the new UI/UX design of #227 we've got a prime opportunity to make string changes to better suit users, and ensure the tests are all relevant, or if anything important is missing.
The old format was a table with a "keyword" like label, and then a success or failure message and maybe some bullet points on the right side.
The new UI allows for more user friendly labels, with a read more section for those that want more details, this means we can provide better descriptions of what a test means to the end user, if multiple failures are an option we can provide these a bit more contextually, and most importantly: We can provide actionable items right away.
It should be noted that the proposed new labels change based on the test state, to give a more contextually correct label for the users benefit, this means a fair amount of added and changed strings, but this is an acceptable trade-off to ensure a good user experience.
Some of these are missing descriptions or actions, suggestions on actionable items are more than welcome to ensure a good experience for users without sending them on wild goose chases.
In light of this, following are the current tests, with their potential states of critical (previously
failure
), recommendation (previouslywarning
), and success states and strings.WordPress Version
Red badge, labeled
Security
.Plugin Versions
Red badge, labeled
Security
.Base description (Is always displayed first, before any other description):
Your site has %d active plugins, and they are all up to date.
Your site has %d plugins waiting to be updated.
Your site has %d inactive plugins, it is recommended to remove any unused plugins to enhance your site security.
Theme Versions
Red badge, labeled
Security
.Base description (Is always displayed first, before any other description):
Your site has %d installed themes, and they are all up to date.
Your site has %d themes waiting to be updated.
Your site has %1$d inactive themes. To enhance your sites security it is recommended to remove any unused themes. You should keep %2$s, the default WordPress theme, %3$s, your current theme and %4$s, the parent theme.
Your site has %1$d inactive themes, other than %2$s, the default WordPress theme, and %3$s, your active theme. It is recommended to remove any unused themes to enhance your sites security.
PHP Version
Red badge, labeled
Security
.Base description (Is always displayed first, before any other description):
Database Server version
Red badge, labeled
Security
.Base description (Is always displayed first, before any other description):
Special consideration
It's possible to use a dropin file here, which will add the following to the description field:
You are using a <code>wp-content/db.php</code> drop-in which might mean that a %s database is not being used.
PHP Extensions
Orange badge, labeled
Performance
.Base description (Is always displayed first, before any other description):
The recommended and required modules are based off the list maintained by the Hosting Team at https://make.wordpress.org/hosting/handbook/handbook/server-environment/#php-extensions
Because of this, the severity of a module missing may be either
Critical
orRecommended
depending on the module. If a module is required, the severity is set toCritical
, if not it is set asRecommended
, and the description field includes a required or recommended indicator for each module that is missing for completeness.MySQL utf8mb4 support
Orange badge, labeled
Performance
.Base description (Is always displayed first, before any other description):
HTTPS status
Red badge, labeled
Security
.Secure communication
Red badge, labeled
Security
.Scheduled events
Orange badge, labeled
Performance
.Base description (Is always displayed first, before any other description):
Plugin and Theme Updates
Red badge, labeled
Security
.Base description (Is always displayed first, before any other description):
HTTP Requests
Orange badge, labeled
Performance
.Base description (Is always displayed first, before any other description):
Communication with WordPress.org
Red badge, labeled
Security
.Base description (Is always displayed first, before any other description):
Background updates
Red badge, labeled
Security
.Base description (Is always displayed first, before any other description):
Loopback request
Orange badge, labeled
Performance
.Base description (Is always displayed first, before any other description):
REST API availability
Orange badge, labeled
Performance
.Base description (Is always displayed first, before any other description):
The text was updated successfully, but these errors were encountered: