Hi, on the latest version 5.4, Site Hardening is reporting ‘Bad’ for child sites using a Child Theme, with the Main Theme as inactive (Example, Divi/Divi Child). I cannot find anywhere to adjust a threshold as I am sure many site owners will also leave the default latest WP theme inactive, leaving 1 active, 2 inactive - but adhering to WP recommendations.
I just logged in to report the same thing but found you beat me to it. Every site I create I have the main theme inactive as I use a child theme for custom changes etc. so the changes to site hardening are now reporting all sites as having issues when in reality they’re not as you can’t have the child theme without an inactive main theme.
Update. I’ve logged out of my Dashboard site, cleared cache, history etc and resynced. My Dashboard site, with only one active theme it’s reporting as ‘bad’
For the one theme, or pair of main/child theme, this has resolved for me, but then nearly 95% all use the same main/child pairing. As Jos Klever says, WP site Health reports “Your site does not have any default theme. Default themes are used by WordPress automatically if anything is wrong with your chosen theme.” So perhaps an additional step may be required to ignore the Default theme of our choice in the MainWP Site Hardening.
Once a WP Core update arrives, we will be back to square one, as it will install the default theme once more.
This is what I now see when I have a site with a child/main theme pair in the site list page. If I check the site itself then everything shows as good, so this hover help text isn’t correct as the site is connected and everything’s actually good.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
WordPress® is a registered trademark of the WordPress Foundation, and WooCommerce® is a registered trademark of WooCommerce, Inc. MainWP is an independent product and is not affiliated, associated, or endorsed by the WordPress Foundation, WooCommerce, Inc., or Automattic Inc., except where noted under the Jetpack® API and Trademark License Agreement. All product names, logos, and brands are property of their respective owners and are used for identification purposes only.