Opened 4 months ago
Last modified 2 months ago
#61967 new feature request
Allow site health managment
Reported by: | peopleinside | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | |
Component: | Site Health | Keywords: | |
Focuses: | Cc: |
Description
Currently Site Health does't allow the administrator to exclude some checks added by WordPress or third part plugin. This can be annoying as no always a notification who indicate a critical problem is real and the admin want disable the alert.
There is a great old abandoned plugin that does do the job but is no more updated since 4 years and soon since more: https://wordpress.org/plugins/site-health-tool-manager/
I would suggest to introduce the same but with an update code.
Change History (4)
#3
@
3 months ago
The plugin works partially with some UI error and some error in PHP logs.
The plugin has been abandoned as is no more updated since 4 years so I don't feel safe use it with PHP errors and UI issues.
Someone has created a unofficial GitHub repo (https://github.com/marcissimus/site-health-tool-manager) that seems solve the issues but it's safe?
Who know. Will be better an official and secure way to do it with a supported feature in the core or a plugin maintained or for avoid site health security warning user will maybe expose himself to security issue by using unofficial plugin that are not in the WordPress store because no other way to fix and manage that.
#5
in reply to:
↑ 4
@
2 months ago
Replying to flagusers:
I am also getting the same error. But after I know it is due to php version. then I update it. now it's working fine
I always use the latest PHP version and the extension that is 4 years old produce some errors on the user interface and on PHP also... is not very safe and good say to WordPress users to use an extension that is 4 years old. I don't know if that can be a security issue and some security extension that I use report this extension as abandoned as security risk medium or height.
I hope someone can take care of an updated and maintain solution :)
Currently the best but not fully safe option is to use an unofficial extension fork in GitHub but this is not the best for security.
I think the main question is whether this should land in core, or is "plugin territory".
The plugin is quite small and well-written. It'll probably work just fine, and modernizing it should be quite doable.