Support

You've found a genuine bug in akeeba:profile:modify.

Any call to that command which didn't explicitly pass --quickicon=1 ended up building the update in a way that MySQL's strict SQL mode rejects for the quickicon column, so the command failed with the error you reported on every run.

We've fixed this in development, and while investigating we found the same command (and akeeba:profile:copy) had a related bug: leaving out --description would silently blank the profile's description instead of leaving it unchanged.

You can test both fixes with the following developer's release. This is an unofficial, alpha-quality build for testing only — please don't rely on it for a production backup without a backup of the site itself that you trust:

https://www.akeeba.com/download/akeebabackuppro-dev/10-4-1-dev202609080738-reve920cb08.html

Please let us know if this resolves the issue for you.

Technical information

• Root cause: component/backend/src/CliCommands/ProfileModify.php cast the --quickicon option to a PHP boolean before checking whether it had been provided. Since (bool) null is false rather than null, the fallback to the profile's existing value never triggered, so quickicon was always written as a raw boolean false when the option was omitted. Joomla's database layer stringifies booleans before escaping them, and (string) false is an empty string, producing quickicon = '' in the SQL — which MySQL strict mode rejects for an integer column, matching the "Incorrect integer value: ''" error.
• Same root cause pattern affected the --description option, which is why it silently reset to blank instead of failing loudly.
• Fixed by reading the raw CLI option, checking for null before it is cast, and storing quickicon as an integer (0/1).