Otto Kekäläinen
Otto Kekäläinen
Most of these are about server settings. We need something that warn users/site admins if their WordPress settings/plugins are dangerous, and which they need to fix themselves. For the server...
Some of this could be implemented as part of #66. Note that we already have some things reported under _Tools > Security_.
Thanks, good ideas!
Thanks for the suggestion about how to enhance https://github.com/Seravo/seravo-plugin/blob/master/lib/canonical-domain-and-https.php – we will look into this.
Include disk quota usage in report. Send report as goaccess html attachment and send it only if quota is exceeded.
Disk quota is already available via Tools > Reports, but as our internal API is not available yet, customers cannot what their max quota would be.
This was also requested in #kehityskeskiviikko on June 6th 2018, in particular the availability reports.
We could perhaps extend `wp doctor` to include Seravo specific checks: ``` $ wp doctor check --all Running checks 100% [==========================] 0:07 / 0:11 +----------------------------+---------+----------------------------------------------------------------------+ | name | status |...
On this page, or on a separate database page, we could list the size of the databases and notify something of excess was found, e.g. _transient in database, or duplicate...
Warn if siteurl and home are not https.. If could also warn of deprecated features and plugins, like https-domain-alias or wp-palvelu-plugin (now everybody should be running seravo-plugin).