{"stuck":0,"software":"Akeeba Backup for WordPress","version":"3.6.0","link":"http:\/\/cdn.akeebabackup.com\/downloads\/backupwp\/3.6.0\/akeebabackupwp-3.6.0-core.zip","date":"2019-07-19","releasenotes":"<h3>What's new<\/h3><p>    <strong>Missing language files in embedded restoration script made restoring sites impossible<\/strong>.    While we were trying to make the 3.5.0 release and after we went through all our release pre-flight checklist the Internet went down at the office. The release lead had to switch to his laptop and go to a different location with working Internet to make the release, after running an abbreviated version of the release pre-flight checklist. The laptop was missing links to three language files which caused this issue. This is something we had not come across before. We are adding the full restoration process even to our abbreviated pre-flight checklist to prevent a future occurrence of this issue.<\/p><p>    <strong>Support for PDO PostgreSQL database driver<\/strong>. This is a feature contributed by a third party developer. We no longer test our software with PostgreSQL.<\/p><p>    <strong>Allow Site Transfer Wizard to ignore free disk space requirements<\/strong>. This is useful for servers which report the free space wrong or for servers with 32-bit versions of PHP and free disk space over 2GB. In both cases the Site Transfer Wizard would fail with a message about not enough disk space.<\/p><p>    <strong>Added BackupID in the failed backups email notifications<\/strong>. This lets you pinpoint the failed backup more easily.<\/p><p>    <strong>Critical bugfix: backup under remote JSON API was broken<\/strong>. The JSON API endpoint (remote.php) failed immediately with a fatal error. Unfortunately, our automated tests did not catch the obvious failure despite having tests speciffically for the JSON API. We fixed the issue in our software and are currently working on identifying the issue with the automated tests to prevent regressions in the future.<\/p><p>    <strong>Critical bugfix: backup under CLI was broken<\/strong>. The CLI code would misidentify migrated backup profiles and complain that your encryption settings have changed, aborting the backup.<\/p><p>    <strong>Important bugfix: Folder browser would not work under Windows<\/strong>. An additional check added against arbitrary data injection was misbehaving on Windows servers, causing the Folber Browser page to appear blank. Mostly experienced when you used the Browse button next to the Output Directory in the Configuration page to find a new location for your backups.<\/p><p>    <strong>Removed support for PrestaShop<\/strong>. The release of PrestaShop 1.7.5, which is essentially a completely different application, means that <a href=\"https:\/\/github.com\/akeeba\/angie\/issues\/63\">we can no longer make transferred sites work properly<\/a>. As a result we had to discontinue support for PrestaShop altogether.<\/p><p>    <strong>Better WordPress .htaccess support<\/strong>. Our restoration script handles many more cases for transferring a WordPress site between hosts and folders. Please note that at this point it's not possible to handle .htaccess changes correctly when transferring from the domain root to a subdirectory of the same or a different (sub)domain. Our troubleshooter includes instructions for manually handling these cases \u2013 essentially removing .htaccess content that's not core WordPress and regenerating it manually through the plugins of the restored site.<\/p><p>    <strong>Bug fixes<\/strong>. We regularly fix smaller and bigger issues. Please consult the CHANGELOG below and the full change history available from the software's main page by clicking the CHANGELOG button.<\/p><h3>PHP versions supported<\/h3><p>    We only officially support using our software with PHP 5.6, 7.1, 7.2 or 7.3. We strongly advise you to run the latest available version 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.<\/p><p>    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.<\/p><h3>WordPress versions supported<\/h3><p>    We officially support only the latest WordPress 4.9 and 5.x release.<\/p><p>    We have received reports that Akeeba Backup for WordPress has been installed on WordPress sites as old as 3.8.    Backing up and restoring sites that old should be possible but it's not tested and not officially supported. It is a    bad idea running an unsupported version of WordPress due to security and performance concerns.<\/p><h3>Changelog<\/h3><h4>Bug fixes<\/h4><ul>\t<li>[HIGH] Generated columns were being dumped instead of skipped over<\/li>\t<li>[HIGH] WordPress restoration doesn't work properly when the original site's URL and the restored site's URL have a similar but not identical string in the path and \/ or (sub)domain e.g. backing up http:\/\/localhost\/ample and restoring to http:\/\/example.com<\/li>\t<li>[HIGH] WordPress restoration fails when the connection information to the old site's database allows connection to a database but the database contains a WordPress installation on a different URL than the one backed up<\/li>\t<li>[HIGH] WordPress restoration fails when the connection information to the old site's database allows connection to a database but the database contains a WordPress installation on a different URL than the one backed up e.g. from http:\/\/www.example.com\/foo to http:\/\/www.example.com\/foo\/bar (or even http:\/\/www.example.com\/foo\/foo)<\/li>\t<li>[HIGH] WordPress restoration: restoring to same URL but different filesystem path results in the absolute path to the site not being updated<\/li>\t<li>[HIGH] WordPress restoration: time limits are not respected when replacing data<\/li>\t<li>[LOW] Integrated restoration progress timer was always stuck at zero<\/li>\t<li>[MEDIUM] Fixed Javascript error in Database Tables Exclusion page<\/li><\/ul><h4>New features<\/h4><ul>\t<li>Option for automatic Dark Mode on Safari<\/li><\/ul><h4>Miscellaneous changes<\/h4><ul>\t<li>Configuration Wizard: determining AJAX method is redundant<\/li>\t<li>Google Storage: API endpoint changed from www.googleapis.com to storage.googleapis.com<\/li>\t<li>Improved feedback in the Manage Backups page when uploading a backup archive<\/li><\/ul><h4>Removed features<\/h4><ul>\t<li>Removed support for non-MySQL database engines (PostgreSQL and MS SQL Server)<\/li><\/ul>","infourl":"https:\/\/www.akeebabackup.com\/download\/backupwp\/3-6-0.html","md5":"23911f62fd5d8d0a8da8472843037a6b","sha1":"26e1d98b06fce26f5d132e84c756b689102d0fd7","sha256":"afcb01416c557f11252200464bf229a7926b2211ad4f1643a4fb0ff082729917","sha384":"7ec8519d8f686ea8e74e636f24279ed1a3a8760576e1bbb70021c1dbc549a3044c12cf4af3e8faf5706bd6c558a2daf7","sha512":"5277e155c912a3fa648fbd4c1136cd7b5b3f0b5e5b4c6ee0711ed845503a27c5f01c0c6fe6d7a7fb523d150fb66cb009051bf003fa98635c4208b14fceec08f6","platforms":"classicpress\/1.0,php\/5.6,php\/7.0,php\/7.1,php\/7.2,php\/7.3,wordpress\/3.8+","loadedUpdate":1,"stability":"stable"}