+ Fuzzy search for archive header to work around single part archives with junk at the start of the file. This will allow you to extract single part archives which have been damaged when downloading through the browser as long as the only damage is up to 128Kb of junk output at the beginning of the archive. This is the most common failure mode of downloading through the browser. Please note that we can't do anything about archives which have been truncated (cut short) as it's impossible to reconstruct data out of nothing — that's an objective limitation imposed by fundamental Physics. Furthermore, this workaround DOES NOT apply to multipart archives; if the .j02, .j03, ... or .z02, .z03, ... files are damaged they cannot be recovered since there is no good way to determine at which point the junk data ends. Finally, do note that some broken files cannot be recovered e.g. when the invalid data is more than 128Kb, when the invalid data contains information which looks likes a valid backup archive header or when the nature of the damage to the file is anything other than junk data at the start of the file (e.g. your server sent the data encoded in a way that your browser failed to properly decode). As per our usual warning, you are strongly discouraged from using your browser to download backup archives.
Bug fixes and minor improvements. Please check the changelog below.
We only officially support using our software with PHP 5.6 or later. For more information please check the Compatibility Information page on our site.
Kindly note that while Kickstart (the archive extraction script) and ANGIE (the database restoration and site reconfiguration script) currently support End of Life PHP versions this does NOT mean that your restored site will run on these PHP versions. After the restoration is complete please make sure that your site is running on a PHP version supported by all software running on your site.
Further to that, please note that we only test our software with currently maintained PHP versions. We do not have reliable cross–platform access to End of Life PHP versions to test with.
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.