What's new?

Backend/Frontend file types allowed in selected directories are now case–insensitive. In the past you would have to specify a case–sensitive extension to be allowed in the .htaccess / Web.config / Nginx Conf maker. For example, allowing the png extension would cause a file named example.PNG or example.Png to return a 403 Forbidden error when you try to access it. Starting with this version the file extensions are case insensitive. Obviously this only matters on case–sensitive filesystems, e.g. ones used on live servers running Linux.

Bug fixes and minor improvements. Please take a look at the CHANGELOG below.

Joomla! and PHP versions supported

Please consult our Compatibility page. It explains our version support policy and lists which versions of our software are compatible with which versions of Joomla and PHP.

Changelog

Bug fixes

• [HIGH] Database error on blocked request if the Do Not Log Reasons list is empty
• [HIGH] PHP 8 error in some features when legacy data is stored in the configuration
• [HIGH] PHP 8 error using the Quick Setup Wizard
• [HIGH] PHP error if you leave “Do not send email notifications for these reasons” empty.
• [MEDIUM] Emails not sent for successful/failed admin long, critical files monitoring and super users monitoring
• [MEDIUM] Exception emails were missing information
• [MEDIUM] Feature "Change administrator login directory to" was missing

Miscellaneous changes

• Backend/Frontend file types allowed in selected directories are now case–insensitive