WAF Exceptions now work with the Block Suspicious URL Parameters feature. Since this feature is likely to cause false positives on misbehaving extensions, we changed our WAF Exceptions feature to also override the Block Suspicious URL Parameters when an exception is matched.
Even better workaround for the Joomla! Database Maintenance page bug. The Database page in Joomla incorrectly claimed that Admin Tools' database tables where out of date, even though they were not. Even though we had removed the old update file Joomla! was tripping itself over, Joomla! would of course not remove it on upgrade (because Joomla; it doesn't make sense, it's how it works). We are now attacking this problem with a one-two punch. First, we have put back the file, but empty, so that Joomla! does not trip over it. Moreover, we have added post-update code to delete that very same file, doing what Joomla! would not do by itself. In case one workaround fails, the other will most likely work and rid you of this annoying problem.
Updated environment stats collection code. We base our decisions on how long to support End of Life PHP and Joomla! versions based on the anonymous, aggregate environment statistics we collect (the versions of our software, PHP, Joomla!, and database server you are using). We have updated the code which collects this information, modernising the “temporary solution” we had for the past ten years. Please remember that this feature is opt-out. If you want, you can always disable the collection of stats in the component's Options. We kindly ask you to leave it enabled; it's anonymous, and help us make better decisions about how long we support obsolete software. If you disable it, please don't complain that we stopped supporting an obsolete version you're still using since you literally chose to not count (we're stating this in the absolutely literal sense: disabling stats collection means your site is not in the aggregate count data we look into when making these decisions!).
Bug fixes and minor improvements. Please take a look at the CHANGELOG below.
Critical bugs and important changes
- CSS compilation error
- Block Suspicious Core Parameters feature
- [HIGH] The “Add persistent offenders to the IP Disallow List” did not work due to a typo
- [LOW] Missing language string
- [LOW] Missing translations when using Joomla Scheduled Tasks
- [LOW] PHP 8.3 deprecated notice in ComponentParameters service (no functional issue)
- [LOW] PHP deprecated notice about implicit float to integer conversion on PHP File Change Scanner (no functional issue)
- [LOW] The additional context of blocked requests was not shown in the Blocked Requests Log page
- Move Unblock My IP into Security when not showing the Graphs panel to balance the display
- The reason in emails reporting a blocked IP was always reported as blocked IP which wasn't useful
- Workaround for the Joomla! bug making it erroneously claim in the Maintenance: Database page that Admin Tools' database tables are not up-to-date when they actually are.
- Support bCrypt encryption for Administrator Password Protection on Apache 2.4+
- [HIGH] NginX Conf Maker: Backend protection would make backend unavailable in newer NginX versions
- [LOW] HSTS option UI wouldn't let you turn it off
- [LOW] Htaccess Maker: Fixed PHP notices when a particular combination of options was used
- [LOW] URL Redirections appears in the Core version, even though it won't do anything; removed
- Fixed [HIGH] PHP File Change Scanner scans all files, regardless of the configured extensions
- [LOW] Possible PHP error when updating this along other extensions using the same post-installation script
Changed Block uninstallation of child extensions
Fixed [LOW] opcache_invalidate may not invalidate a file
Fixed [LOW] Wrong documentation link in the scheduling information page
Fixed [LOW] Cannot save the password authentication when WebAuthn preference is enabled from the regular user edit page
- [LOW] “Disable editing user properties for these user groups” does not let you select the Super Users group
- [MEDIUM] PHP File Change Scanner fails when the MySQL packet size is too small (e.g. 1MiB) when scanning big files (>400KiB) with Calculate File Diffs enabled
- Only show warning to regenerate the server configuration file if it was generated by Admin Tools to begin with
- Workaround for CloudAccess and other hosts with broken Apache installations that don't understand the If directive