Version 1.2.4

This is a security and maintenance release for Health Check version 1.2.x, that also affects version 1.1.x and we recommend updating to version 1.2.4, which includes the following changes:

• Security: Prevent arbitrary file viewing through the integrity file actions. Independently reported by Julien Legras of https://synacktiv.com and siliconforks.
• Security: Site status was available to any user with a subscriber role or higher on a site. Reported by Julien Legras of https://synacktiv.com.
• Security: Hardened the troubleshooting mode session so it is lock to the users location when active.
• New enhancement: Check that various PHP extensions exist, as recommended by the WordPress Hosting Community.
• New enhancement: Check if update APIs are being manipulated by plugins or themes.
• Fix: Copying debug information had the wrong indentation for easier readability.
• Fix: Toggling plugins and themes from the troubleshooting widget on in the dashboard now lets you expand/collapse them as intended.
• Fix: When debugging was enabled in WordPress, disabling a plugin in troubleshooting mode would cause a WSOD if the disabled plugin caused a fatal error.

Version 1.2.1

This is a maintenance release for version 1.2, addressing the following issues:

• Make sure only those with access to the plugin see the backup encouragement notice.
• Make sure the is_troubleshooting() checks are available to the Site Status tester when the MU plugin may not have updated yet.
• Avoid a warning of an undefined variable if you have the latest WordPress version installed.

Version 1.2.0

Changes and improvements in version 1.2.0

• Changed plugin name, it now better describes the plugins two primary purposes.
• Changed the Health Check tab, it's now named Site Status, as we used the old name too many places and it was confusing.
• Site status tests now run asynchronously, making the page load much faster.
• The HTTPS tests now also check your Site URL settings to make sure they are following recommended best practices.
• Fixed a warning preventing plugin names from displaying on the front-end in some cases.
• Fixed an issue where you might get a 500 error if you tried using Troubleshooting Mode while using a child theme.
• Automatically disable/enable a plugin or theme in Troubleshooting Mode if they are detected to cause errors.
• Introduce a new dashboard widget during Troubleshooting Mode (and a simplified version on the plugins screen) to better explain what is going on, and make available actions more discoverable than the admin menu is.
• Some text improvements throughout the plugin.
• When loopback tests fail, we previously tested all plugins at once, for sites that have many plugins this may fail as the request times out. We now test one plugin at a time to avoid this, while also showing more information at the tests are running to the end user.

Version 1.2.0-beta1

An early build of 1.2.0, with specific fixes in place, and some of our new enhancements.

This is intended for external testing.

Version 1.1.2

This is a maintenance release, based on recurring issues users have reported.

• Fixed child themes not displaying properly in Troubleshooting Mode.
• Improved styling for the backup warning, shown when activating the plugin, so it doesn't block mobile users.
• Added explanations to the plugins screen if you enter Troubleshooting Mode there, so users know what is going on.
• Fixed admin menu overflowing if too many plugins exist.

Version 1.1.1

This is a maintenance release to address a potential fatal error in the plugins Troubleshooting view.

Users that have previously used Troubleshooting Mode in an earlier release might get a fatal error, preventing the button to enable the mode from being shown.

Version 1.1.0

Changes and improvements in version 1.1.0

• Check for theme, plugin and WordPress updates when visiting the debug tab.
• Improved wording on some failure situations.
• Made the Debug Information tab a bit easier to read with fixed table styles.
• Redesigned tools page, with added accordion to avoid information overload, and different features mixing together.
• Mail test tool now allows you to include an optional customized message.
• Users can now change between any installed theme while in troubleshooting mode.
• Renamed the Must-Use plugin, making it align with what features present in the file.
• Improved the plugin cleanup process, when the plugin is deleted.
• Show full plugin names, and not slugs, in the troubleshooting admin bar menu.
• Check if the .htaccess file contains any rules not added by WordPress core in the debug section.
• Allow the disabling of Troubleshooting Mode from the same page as you previously enabled it from.
• Removed cURL checks from the automated test page, this was more confusion than help.
• Add installation size to the debug information.