Support

Akeeba Solo

#42889 Error on new feature check file upload

Posted in ‘Akeeba Solo’
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

PHP version
8.5
Akeeba Solo version
9.1.2

Latest post by carcam on Tuesday, 21 April 2026 05:59 CDT

carcam

Hi,

I just updated to 9.1.2 to use the shinny new feature to check backup uploads and I it's not working for me.

 

I have tested it in PHP 8.3, 8.4 and 8.5 and also on PHP 7.4. For the latest I got this error:

 

Checking for failed uploads

* * * E R R O R * * *
1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''' AND `status` = 'complete' AND `type` != 'dbonly' AND `filesexist` = '1' AND `' at line 3 SQL=SELECT *
FROM `solo_ak_stats`
WHERE `profile_id` IN '' AND `status` = 'complete' AND `type` != 'dbonly' AND `filesexist` = '1' AND `remote_filename` EMPTY '' AND `backupstart` > '0000-00-00 00:00:00'
ORDER BY `id` DESC
/

 

For the PHP 8 versions I got this error:

 

You are using PHP 8.4.19 (cli)

Checking for failed uploads

* * * E R R O R * * *
0: mysqli_real_escape_string(): Argument #2 ($string) must be of type string, array given
/srv/users/carritos/apps/carritosbaratos/public/solo/vendor/akeeba/engine/engine/Driver/Mysqli.php:204
#

 

I think the issue is choosing the profile on the command, but I have tried adding --profile=2 but that changed nothing.

 

Best!!

nicholas
Akeeba Staff
Manager

Thank you for the detailed report. It was very helpful in tracking down the issue quickly.

The problem was in the backup engine's filter query builder. The new "check file upload" feature introduced two filter types (IN and EMPTY) that the query builder didn't know how to handle properly.

As for the different error messages, on PHP 8.x, this caused a type error because an array was passed where a string was expected. On PHP 7.4, the array silently converted to an empty string, producing invalid SQL.

The fix had already been applied to the backup engine, but it looks like I had forgotten to update it in the package. This is addressed now. The fix will definitely be included in the next release, planned for tomorrow.

Thank you again for taking the time to report this!

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!

carcam

Thanks for the explanation and the fix to come!!

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!