Support

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

The command always failed at the same point right after locating the profile to copy, which is why it fataled with that exact error on every run.

We've fixed this in development. You can test the fix 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

This same build also fixes a related bug you may run into separately: akeeba:profile:modify and akeeba:profile:copy failing with a MySQL "Incorrect integer value" error unless --quickicon=1 was explicitly passed, and both commands silently blanking the profile's description when --description was left out. If you'd like more detail on that one, it's covered in our reply to your other ticket (43323).

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

Technical information

• Root cause: component/backend/src/CliCommands/ProfileCopy.php loaded the profile through the component's model, which returns a plain PHP stdClass object, then called getProperties() on it — a method that only exists on the underlying database table class, not on stdClass. That call was therefore always fatal.
• Fixed by reading the loaded object's properties directly instead of calling a method that was never available on it.