Downloads

Akeeba Backup for Joomla!

Akeeba Backup for Joomla!

version 4.7.4 Stable

Released on: Sunday, 31 July 2016 16:30

Release highlights

Last release compatible with PHP 5.3 and Joomla! 1.6 to 3.3 (inclusive).. If you are on PHP 5.4+ and Joomla! 3.4+ please install Akeeba Backup 5.

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. Joomla and its extensions 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. You should have just read our documentation. We've warned you about this since 2007.

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 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.

THIS PROCESS ONLY NEEDS TO TAKE PLACE ONCE PER BACKUP PROFILE AND SITE!

  • Go to your Akeeba Backup 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. 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.

Joomla! 1.6 or later

This version is compatible with Joomla! 1.6, 1.7, 2.5, 3.0, 3.1, 3.2, 3.3, 3.4 and 3.5.

Please note that we do NOT recommend using Joomla! 1.x / 2.x or 3.0 to 3.3 inclusive on production sites due to major security issues. Support for these old versions is intended to give you the option of taking a full site backup prior to upgrading to the latest available Joomla! release.

PHP 5.3.3 or later 5.x version is required

If you have Joomla! 3.4 or later and PHP 5.4 or later please use Akeeba Backup 5.x. This version of Akeeba Backup (4.7.x) will only receive very irregular security fixes but NO bug fixes or new features. This version of Akeeba Backup is only published for people managing older sites so that they can back them up before upgrading them. Any other use is strongly NOT recommended!

The minimum required PHP version is 5.3.03. All versions of PHP from 5.3.03 onwards are supported, including 5.4, 5.5, 5.6 and the just released PHP 7.0. The component will not work on PHP 5.2 or earlier and will, in fact, refuse to install on it. We'd like to remind you that Joomla! 3.4 and earlier does NOT support PHP 7. Joomla! 3.5 (currently in beta) does support PHP 7. Akeeba Backup will work just fine in a Joomla! 3.5 site running on PHP 7.0.

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.

Changelog

Bug fixes

  • [MEDIUM] Multi db view wasn't saving the values

New features

  • Restoration: a warning is displayed if the database table name prefix contains uppercase characters

Miscellaneous changes

  • 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 https://blogs.dropbox.com/developers/2016/06/api-v1-deprecated/ Please use the Dropbox API v2 integration instead.

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 Already a subscriber? Log in.