Support

Admin Tools

#43378 Admin Tools 7.9.3 – PHP TypeError in BlockedRequestHandler on failed frontend login

Posted in ‘Admin Tools for Joomla!’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
5.4.8
PHP version
8.3.33
Admin Tools version
7.9.3

Latest post by nicholas on Tuesday, 29 September 2026 10:29 CDT

agv_akeeba_pro
Hello, We are experiencing a reproducible error with Admin Tools Professional 7.9.3 when a user enters an incorrect username or password on the Joomla frontend. Environment - Admin Tools Professional: 7.9.3 - PHP: 8.3 - Website: Joomla - Frontend login URL: /login?task=user.login Problem When Web Application Firewall → Hardening Options → “Treat failed logins as a reason for blocking the request” is enabled, an incorrect frontend login does not result in the normal Joomla login error message. Instead, the following PHP error is displayed: Akeeba\Plugin\System\AdminTools\Utility\BlockedRequestHandler::escapeLogLine(): Argument #1 ($value) must be of type string, null given, called in /home/gepensione/public_html/plugins/system/admintools/src/Utility/BlockedRequestHandler.php on line 863 The Admin Tools Security Exceptions Log records the request as: - Reason: Login failure - Target URL: /login?task=user.login Steps to reproduce 1. Enable “Treat failed logins as a reason for blocking the request”. 2. Open the Joomla frontend login page. 3. Enter a valid or invalid username with an incorrect password. 4. Submit the login form. 5. The BlockedRequestHandler::escapeLogLine() TypeError is displayed instead of Joomla's normal failed-login message. Test performed We temporarily disabled only “Treat failed logins as a reason for blocking the request”. With this option disabled, the exact same failed login is handled correctly by Joomla and the normal message is displayed: “The username and password do not match or you do not have an account yet.” Re-enabling the Admin Tools option causes the PHP TypeError again. Other WAF functionality remains enabled, including Log blocked requests. Could you please advise whether this is a known issue in Admin Tools 7.9.3, and whether there is a fix or recommended workaround? If required, we can provide the full stack trace, Joomla version, debug log, and additional configuration details. Kind regards, Phons Stokkermans Commissie Systeembeheer Achmea Gepensioneerden Vereniging ageevee.nl

nicholas
Akeeba Staff
Manager

This appears to be due to a latent bug in file logging which has existed throughout Admin Tools 7 ever since its first release in 2021. Version 7.9.3 implemented a change so that a bug like that isn't silently ignored, but raised as a TypeException. However, the release 7.9.3 version did not include the second part of the fix which addressed the root cause and, crucially, also included the missing integration tests for this feature.

The fix will be included in 7.9.4. In the meantime, you can set "Keep a debug log file" to No.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!