Support

As I already told you, the problem is in Joomla! itself, and the third party extensions AcyMailing and Fabrik on your site.

As I already told you, this problem has been reported to Joomla and already fixed: https://github.com/joomla/joomla-cms/issues/42210. However, the Joomla! project HAS NOT released a bug fix release Joomla! 5.0.1 yet.

As I already told you, neither Joomla's core code, nor third party extensions' code is under our control. We cannot accept any responsibility for bugs in Joomla! and third party extensions code exactly because that code IS NOT UNDER CONTROL. There is not debatable, it is tautological.

As I already told you, this is something you can prove yourself, on your own site.

• Uninstall Akeeba Backup from your site. You will lose all your backups and backup settings.
• Now, run the same cli/joomla.php command WITHOUT any arguments (without the akeeba:backup:take and so on).

As you can see, the CLI application is still broken, without any of our code on your site. Therefore, as I already told you, exactly as the linked issue states, we have proven beyond any doubt that the problem lies with Joomla! itself and third party software.

As I already told you, in Joomla! 3 we had our own command line script which were not loading any third party plugins and worked fine. We had to discontinue them and replace them with Joomla! CLI Application commands because standalone CLI script are deprecated in Joomla! 4.0 and will be completely removed in Joomla! 6. Therefore, we had to use the Joomla! CLI Application.

As I already told you, the fact that you are using the Joomla! CLI Application and not just code written by us is objectively proven by the fact that your command line is using cli/joomla.php, a file distributed with Joomla! itself.

As I already told you, the problem happens before Joomla! loads our code.

As I already told you, beyond the blatantly obvious fact above, the fact that you are using the Joomla! CLI Application which is part of Joomla! itself is explicitly documented.

As I already told you, and as is proven above both as something blatantly obvious and as something explicitly documented, when backing up your site using a Joomla! CLI Application command, you are using Akeeba Backup through the Joomla! CLI Application — just like when you are backing up your site through the backend of your site you are using Akeeba Backup through the Joomla! Administrator Application.

As I already told you, and is objectively and unquestionably obvious, when Joomla! is broken due to its own bugs, or because of a broken third party plugin there is nothing we can do. We can only fix problems in our code, not problems in Joomla's and third party extension's code.

As I already told you, your issue is closed with prejudice. This means that any further attempt to raise the exact same issue will result in your issue being closed.

As I already told you, I had given you a final warning to mind the way you are talking to me. Instead, you are calling me incompetent. This is unacceptable.

As I already told you, I have, in my own spare time, written the definitive software development book for Joomla! 4 and Joomla! 5. I cannot make third party developers read it, or force them to follow it so their software isn't chronically broken. I cannot prevent them or the Joomla! project from making mistakes and/or not caring about the quality of their software. What I can and have been doing consistently the last 17 years is ensure that our software follows all Joomla! coding standards and is of a consistent, great quality. That's what is under my control, that's what I can objectively do.

If you want to question the competence of someone who has been contributing core code to Joomla! itself (indicatively, all of the following features were written by me: Joomla! Update, Two-factor Authentication, Multi-factor Authentication, WebAuth, Quick Icons, Post-Update Messages, Update Sites management, Download ID integration with the Joomla! extensions update, managing the Download Keys, and many more I don't care to list here), the person who started the Joomla! 4 Working Group, the person who made the very first commit to Joomla! 4, the person who wrote and improved the Joomla! event-based plugin system, the person who proved that namespacing worked trouble-free in Joomla! 3 and led to the deprecation of the JPlugin class in favour of the \Joomla\CMS\Plugin\CMSPlugin namespace class, GIVE ME YOUR CODE ANALYSIS. You have one hour. You can of course apologise and we'll leave it at that. Failure to do either will result in your immediate account termination without a refund as per our Terms of Service for calling me incompetent. This kind of language is unacceptable!

This is not Facebook, sir. You cannot attack the professional ability of other people without any repercussion. Back your accusations with irrefutable evidence, or suffer the consequences of your actions after receiving a warning to mind your behaviour.