Important: iThemes Security now requires WordPress 5.8 or later.
New Feature: Introduce a new Import Export feature that allows for greater customization and flexibility.
Bug Fix: Scroll to top of window when navigating.
Bug Fix: Allow searching for Password Requirements.
Bug Fix: Login page would be blank when Passwordless Login was configured to use the "Username First" flow.
Bug Fix: Don't load WordPress and System Tweaks modules when the `ITSEC_DISABLE_MODULES` constant is enabled.
Bug Fix: Prevent incidentally loading the Two-Factor module when it is unregistered.
Bug Fix: Conditionally display the NGINX File Path setting.
Bug Fix: Allow saving Notifications when "default recipients must contain at least 1 item" error is present.
Enhancement: Reintroduce Feature Flags management UI.
Tweak: Reposition "Advanced" and "Tools" menu items to be more readable on lengthy screens.
Bug Fix: Sites that did not support HTTPS, but had the SSL module active, but not configured, on upgrade would get redirected to the HTTPS version of the site.
Bug Fix: When the Change Admin User tool is run, update any User Groups referencing the old user id.
Bug Fix: Unregister the iThemes Security Two-Factor module when the Two-Factor Feature Plugin is enabled.
Bug Fix: Add missing and correct erroneous textdomains.
Bug Fix: WordPress footer would appear in the middle of the logs page.
Tweak: Move "Have I Been Pwned" integration to the Core plugin.
Tweak: Reduce filename length and complexity for built CSS and JS files.
Bug Fix: Disable XML-RPC rules in server config files. Previously, XML-RPC was being disabled using the XML-RPC enabled filter.
Bug Fix: Fatal error on logs page when User Logging and Two-Factor are enabled and a user logs in using Two-Factor.
Bug Fix: Add missing constants to the debug page.
Bug Fix: Fatal error when sending the "Inactive Users" notification.
Bug Fix: Remove deleted recipients when saving notifications.
Bug Fix: Allow using reserved words as prefixes for the Hide Backend Login Slug.
Bug Fix: Enforce SSL would not redirect users from HTTP to HTTPS on the front-end of the website.
Bug Fix: Correct Site Scan statuses for scans with no issues.