Akeeba Backup for WordPress

Akeeba Backup for WordPress

version 1.9.2 Stable

Released on: Friday, 08 July 2016 07:54

Release Notes

What's new

Removed Dropbox API v1 integration.. If you are still using it please upgrade to our Dropbox API v2 integration immediately. Unfortunately, due to the way the two Dropbox API versions work it is impossible to have an automatic switch to the v2 API. Please read below for more information about the Dropbox switch.

Restoration: a warning is displayed if the database table name prefix contains uppercase characters. Keep in mind that MySQL does not work reliably with table names containing uppercase characters on servers with a case-insensitive filesystem such as all Windows and most macOS installations. The only RELIABLE way to transfer a site between these servers and a case-sensitive server (e.g. Linux, what most hosts out there use) is having all lowercase table names. PHP CMS / applications already do that. However, if you set up a database table name prefix in uppercase or mixed case letters you are triggering MySQL's limitations which will result in problems backing up and restoring your site. If that's the case with your site the restoration script will warn you. Conversely, we added some smart code during backup to look for the wrong case table names and try to back them up. It usually can do that unless you've got tables with the same name in all lowercase. In this case you've got a broken database and nobody can help you.

Removal of the Dropbox v1 API integration and how to switch to the v2 API

We have removed integration with the Dropbox v1 API because Dropbox itself announced it is deprecated and will be turned off by June 28th, 2017. We chose to remove support for the deprecated API now to make sure that all of our clients will be ready for Dropbox' deprecation next year. If you think that's an overkill please keep in mind that we added Dropbox v2 support in November 2015 with the documentation note that it's the recommended version and that the v1 API may stop working at any point.

Unfortunately, Dropbox' v1 and v2 APIs are very different and there is no way to have an automatic migration from v1 to v2. The access tokens used in the two API versions are and work different. This means that by upgrading to a new version of Akeeba Backup / Solo your backup profiles which were using the deprecated Dropbox v1 API integration are no longer linked to a post-processing engine and produce errors.

Luckily there's a very simple process you have to follow once on every site and backup profile you want to (re)link to Dropbox.


  • Go to your Akeeba Backup / Solo main page.
  • Select the backup profile you want to relink.
  • Click on Configuration.
  • In the Post-processing Engine dropdown select “Upload to Dropbox (v2 API)”
  • Click on “Configure” next to it.
  • Click on the “Authentication – Step 1” button.
  • You may have to log in to Dropbox if you are not already logged in. Also, if you had not authorized another Akeeba Backup or Akeeba Solo installation to use Dropbox you may see a confirmation about it. If you are already logged in and have authorized our software to use Dropbox you will not see any of that.
  • You then see a page with the big title “Dropbox Authentication is almost complete”. Click on the blue “Complete Dropbox authentication” button below it.
  • Now you're back to Akeeba Backup / Solo. Click on Save & Close to complete the setup.

Unlike the Dropbox v1 API you must not copy the token from one profile / site to another. Instead, repeat the process above. Dropbox API v2 produces a new token every time you link a new backup profile or site to Dropbox without revoking the previous one.

Again, we apologize for having to go through this process but this is due to changes made on Dropbox' side. On the upside, the Dropbox API v2 is much more stable, allows for bigger uploads and lets us perform “chunk uploads”, a technique which allows us to transfer very large backup archives without you having to set up small part sizes. You can now safely use a Part Size for Split Archives up to 2047 Mb without any upload worries.

Updating Akeeba Backup for WordPress to version 1.9.x

Due to changes in the packaging format and / or issues in the updater, you cannot update automatically from Akeeba Backup for WordPress versions 1.0 through 1.8.2 (inclusive) to version 1.9.0 and beyond. You will have to do that manually.

Heads up! You must NOT uninstall or deactivate the plugin before the update. Doing so may result in loss of your backup settings and / or your backup archives. Instead, here's what to do:

  • Download the ZIP file for Akeeba Backup for WordPress 1.9 and extract it locally. You will see an extracted folder named akeebabackupwp.
  • Upload the files from the extracted akeebabackupwp folder into your site's wp-content/plugins/akeebabackupwp folder, overwriting your existing files, using FTP or SFTP. Please note that the name of the folder on your site may be different than akeebabackupwp, e.g. akeebabackupwpcore, akeebabackupwp (1) or something similar. It depends on how you installed the plugin.
  • Log in to WordPress' wp-admin and access Akeeba Backup for WordPress to automatically complete the update process. There is no message when the process completes. You just see the main page of Akeeba Backup for WordPress (this means the update succeeded).

You will only need to do this once, upgrading to version 1.9 or later for the first time.

PHP 5.3.3 or later or PHP 7 is required

Akeeba Solo and Akeeba Backup for WordPress 1.9 are compatible with PHP 5.3.04 and later versions, including 5.4, 5.5, 5.6 and the newest version of PHP, 7.0. We'd like to remind you that most third party software which can be backed up by our software do not support PHP 7 yet. As a result we can't guarantee a trouble-free restoration or tha the restored site will work on PHP 7 as this depends entirely on the software powering your site.

Note: there is no such thing as PHP 6. PHP versions jumped from 5.6 to 7.0. Why? Well, it's a long story. TL;DR: It doesn't have to make sense, just accept it.


Bug fixes

  • [HIGH] Conservative time settings (minimum execution time greated than the maximum execution time) cause the backup to fail
  • [HIGH] Infinite loop if the #__ak_profiles table does not exist
  • [LOW] Integrated Restoration: The last response timer jumped between values
  • [LOW] Restoration: Database error information does not contain the actual error message generated by the database
  • [LOW] WordPress restoration: the absolute path restoration missed the leading / for sites originating from non-Windows systems
  • [MEDIUM] Restoration: The PDOMySQL driver would always crash with an error

New features

  • Restoration: a warning is displayed if the database table name prefix contains uppercase characters
  • WordPress restoration: all tables with the WP prefix are now pre-selected in the Replace Data page to minimise post-restoration issues from partial data replacement
  • WordPress restoration: the default replacement data now includes the JSON-encoded versions of the data as well

Miscellaneous changes

  • The backup engine will now warn you if you are using a really old PHP version
  • Workaround for sites with upper- or mixed-case prefixes / table names on MySQL servers running on case-insensitive filesystems and lower_case_table_names = 1 (default on Windows)
  • You will get a warning if you try to backup sites with upper- or mixed-case prefixes as this can cause major restoration issues.

Removed features

  • Removed Dropbox API v1 integration. The v1 API is going to be discontinued by Dropbox, see Please use the Dropbox API v2 integration instead.

Release Files

Akeeba Backup CORE for WordPress

PHP 5.3 PHP 5.4 PHP 5.5 PHP 5.6 PHP 7.0 WordPress 3.8+

Download now

Our Core versions are provided free of charge,
but they only scratch the surface of what's possible.

Subscribe today to get access to the exclusive features and enhanced support of our Professional releases!

Subscribe and get full access!

Already a subscriber? Log in.

Cookies Notification - Action required

This website uses cookies to provide user authentication and improve your user experience. Please indicate whether you consent to our site placing these cookies on your device. You can change your preference later, from the controls which will be made available to you at the bottom of every page of our site.