Owner's reply: You tried to restore a site whose **third party** software – not written or maintained by our company – is incompatible with PHP 8 on a server running PHP 8. This is something that is not only common sense, but also explicitly documented. You never gave us the opportunity to discuss this productively with you. You sent us a borderline abusive email in the middle of our night, merely informing us that your false assumptions and misunderstandings would be submitted here on the JED as a review. Regrettably, this puts us in the distasteful situation of having to publicly rebuke your disinformation, with everything that entails about how other people will perceive you.

I am afraid that you are wrong on all four complaints you made namely that a. it cost you months of work, b. finding the backup path was difficult, c. support is paid because we have a [mild profanity redacted] product, and d. that Akeeba Backup was at fault.

a. It cost you nothing. Your site is still running after switching it back to PHP 7.4. You admitted this yourself.

b. The path to the backup archives is documented: https://www.akeeba.com/documentation/akeeba-backup-joomla/backup-now.html#qa-backup-location This page appears in the documentation index under the self-explanatory title "Where are my backups". It is also shown to you in the Manage Backups page, when you click the info icon to get the information about the backup archive. It's literally a folder called "backups" under the folder Joomla installs the component in.

c. The description here on the Joomla! Extensions Directory literally reads "The Akeeba Backup Core component, its documentation and its video tutorials are free of charge. Support for the software and an edition with advanced features (not listed above) are, however, not free of charge" and it also says to read the documentation. We discontinued free support in June 2011 because of the number of people who failed to employ common sense, or read the documentation, and hurled uncalled for abuse at us as a result – exactly as you are doing here.

If someone asks **politely** and provided that we're not up to our eyeballs with work, we do answer simple questions like yours. As it happens, this week is slow (since most of the US is off for Thanksgivings, severely lightening our load). Had you asked politely about what happened during your restoration we would have politely pointed you to the documentation page and explained further what to do.

d. Your entire problem is that you transferred your site from a PHP 7.4 server to a PHP 8 server. However, your third part (NOT written by us) extensions are **NOT** compatible with PHP 8.

Kindly remember that Akeeba Backup makes exact copies of your sites. It does not, and objectively cannot, rewrite the software installed on your site to make it compatible with a different PHP version. The very first page of the restoration script displays very clearly the PHP version you backed up on and the PHP version you are restoring on, as shown in https://www.akeeba.com/documentation/akeeba-backup-joomla/angie-joomla.html#angie-joomla-first Moreover, the fact that you need to pay attention to the PHP versions and that problems due to a PHP version mismatch are NOT restoration issues is explicitly documented in "Common issues on restored sites due to PHP incompatibilities between the source and target server" (https://www.akeeba.com/documentation/akeeba-backup-joomla/prphpissues.html)

Akeeba Backup – which is compatible with PHP versions 7.2 to the as-yet-unreleased version 8.3 inclusive since several months ago – did work. If it had not, switching your PHP version back to 7.4 would've had no effect. The fact that switching back to PHP 7.4 allowed your site to work further proves that the root cause of your issue is third party software on your site which is still incompatible with PHP 8, four years since it was first released.

I understand your frustration, but the way you conducted yourself is entitled, unfair, uncalled for, and unprofessional. In the end of the day, it was third party software not under out control which failed, not our software. In the end of the day, it was you who did not exercise common sense, read the documentation, or approached us for a clarification.