Log the full path to the computed site's root, without
Core (free of charge) version only: the PayPal donation link included a tracking pixel. The donation code was originally added around 2007. Apparently it was never revised and included a tracking pixel, part of PayPal's default donation button form code. We changed that to a donation link, without any kind of tracking.
Integrated restoration: sanity checks were not applied, resulting in extraction errors. This applies only to the Professional release and then again only for backups stored remotely. The backups needs to be fetched back to the server before trying to restore the site. This check was not being made, resulting in an indecipherable error about the archive file being corrupt when, in fact, there was no backup archive on the server to begin with.
Core (free of charge) version only: the system/akeebaupdatecheck plugin would always throw an error. It looks like it was looking for a piece of code that only shipped with the Professional version. This has now been addressed.
Restoration will fail if a table's name is a superset of another table's name and ends in a number. This is an extremely rare case. You'd need something like a table named foo_example_2020 whose name is a superset of another table named foo_example_2 and ends with a digit. In this case the name of the table in the backup was getting corrupt and that caused the restoration to always fail if you used the Drop setting (default) for the "With existing" option in the Database Restoration page.
WebDav post-processing engine: first backup archive was always uploaded on the remote root, ignoring any directory settings. This was a case of late initialisation gone wrong.
We only officially support using our software with PHP 5.6, 7.1, 7.2, 7.3 or 7.4.
We strongly advise you to run either of the two latest available version branches of PHP on a branch currently maintained by the PHP project for security and performance reasons. Older versions of PHP have known major security issues which are being actively exploited to hack sites and they have stopped receiving security updates, leaving you exposed to these issues. Moreover, they are slower, therefore consuming more server resources to perform the same tasks.
Kindly note that our policy is to officially support only the PHP versions which are not yet End Of Life per the official PHP project with a voluntarily extension of support for 6 to 9 months after they become End of Life. After that time we stop providing any support for these obsolete versions of PHP without any further notice. New version branches of PHP will be supported experimentally starting sometime during their Release Candidate phase and fully about 4 to 8 weeks after the first stable version of that branch is released.
We officially only support the latest WordPress 5.x release.
Our software should also work on WordPress 4.9 and ClassicPress 1.x since we do not rely on any features added in later WordPress versions.
We fully support single site and multi-site installations of WordPress. Multi-site installations can be converted on restoration from directory-based to subdomain-based or vice versa. You cannot restore a single site backup into a multi-site installation. You cannot restore / convert a blog of a multi-site network installation into a single site WordPress installation (in fact, there is no official WordPress method to do that safely).
We do not recommend using our software with WordPress versions earlier than 4.6 as some WordPress features we rely on for our software to function properly did not exist in these vintage versions. We generally strongly advise against running old, no longer maintained versions of WordPress for security and performance reasons.