Forgot your username?             Forgot your password?

Want more?

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.

Akeeba Backup for Joomla!

Version 5.1.2 Stable

Released on: Friday, 08 July 2016 07:51

 

Maturity
Stable
Released on
Friday, 08 July 2016 07:51
Viewed
0 times

This is a minor bugfix release, addressing known issues in the previous 5.1.x versions.

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. 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! 3.4 or later

We only support Joomla! 3.4 or later, including 3.5. We strongly advise you to run Joomla! 3.4.7 or later for security reasons. Older versions of Joomla! have known major security issues which are being actively exploited to hack sites. Do note that these security issues were fixed on Christmas Eve 2015 thanks to the effort of our development team who contributed their time and knowledge to make Joomla! more secure.

PHP 5.4.0 or any later 5.x/7.x version is required

Support for PHP 5.3 is discontinued. It's end of life since August 2014 and widely considered a security risk, unfit for production sites. Our software requries PHP 5.4 or later and is compatible with PHP 5.4, 5.5, 5.6 and 7.0. We strongly recommend using PHP 5.6 or 7.0.

Note: even though this version of our software will install and work on PHP 5.3.3 and later we WILL NOT provide support to anyone who is using PHP 5.3.

We'd like to remind you that Joomla! 3.4 does NOT support PHP 7. PHP 7 is only supported by Joomla! 3.5.0 and later versions. Akeeba Backup will work perfectly fine (and very fast!) on a Joomla! 3.5 or later site running on PHP 7.0.

Changelog

Bug fixes

  • [HIGH] Conservative time settings (minimum execution time greated than the maximum execution time) cause the backup to fail
  • [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
  • [MEDIUM] Akeeba Backup's control panel would not be displayed if you didn't have the Configure privilege (the correct privilege is, in fact, Access Administrator Interface)
  • [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

Miscellaneous changes

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

Take me to the downloads for this version

Version 5.1.1 Stable

Released on: Thursday, 23 June 2016 10:09

 

Maturity
Stable
Released on
Thursday, 23 June 2016 10:09
Viewed
0 times

This is a minor bugfix release. No, it doesn't fix any bugs in our software, it works around bugs in badly set up servers. If 5.1.0 didn't work for you please call your host and tell them that running eAccelerator on their production servers a whole four years after eAccelerator was abadnoned is ridiculous as much as it is dangerous. Next thing, use Akeeba Backup 5.1.1 which can now work on these badly configured server and move your sites off these hosts.

What's new

Work around badly configured hosting environments. It has come to our attention that certain abysmal quality hosts are using the eAccelerator code caching PHP extension on PHP 5.4 and later versions. eAccelerator was abandoned in 2012 and never fully supported the new features in PHP 5.4 and later versions. As a result, any software using any PHP 5.4 and later features, such as Traits, will not work properly when you're using eAccelerator. This was the case with Akeeba Backup 5.0.0 to 5.1.0 inclusive. Even though this is your host's fault (they MUST NOT run end of life software on production web servers, let alone software that breaks the scripts running on the server) we decided to work around their wrong setup in our software. THIS IS NOT A PERMANENT THING. You will receive non-dismissable warnings until your host fixes their setup. Moreover Akeeba Backup 5.2.0 will DROP support for these broken servers and go full PHP 5.4 and later ONLY. You have been warned. Ask your host to fix their servers. DO NOT let them run out of date software on their servers which breaks your sites and can introduce security issues (make your sites easier to hack).

Joomla! 3.4 or later

We only support Joomla! 3.4 or later, including 3.5. We strongly advise you to run Joomla! 3.4.7 or later for security reasons. Older versions of Joomla! have known major security issues which are being actively exploited to hack sites. Do note that these security issues were fixed on Christmas Eve 2015 thanks to the effort of our development team who contributed their time and knowledge to make Joomla! more secure.

PHP 5.4.0 or any later 5.x/7.x version is required

Support for PHP 5.3 is discontinued. It's end of life since August 2014 and widely considered a security risk, unfit for production sites. Our software requries PHP 5.4 or later and is compatible with PHP 5.4, 5.5, 5.6 and 7.0. We strongly recommend using PHP 5.6 or 7.0.

Note: even though this version of our software will install and work on PHP 5.3.3 and later we WILL NOT provide support to anyone who is using PHP 5.3.

We'd like to remind you that Joomla! 3.4 does NOT support PHP 7. PHP 7 is only supported by Joomla! 3.5.0 and later versions. Akeeba Backup will work perfectly fine (and very fast!) on a Joomla! 3.5 or later site running on PHP 7.0.

Thank you, beta testers!

We want to sincerely thank all the people who took the time to download, install and test the two beta releases of Akeeba Backup 5.1.0. Their feedback has been invaluable in identifying and fixing all remaining bugs – including some obscure ones that have been there for several years. You guys and gals rock!

Changelog

Bug fixes

  • [HIGH] gh-592 Misleading 403 Access forbidden error when your Akeeba Backup tables are missing or corrupt.
  • [LOW] PHP warning in the File and Directories Exclusion page when the root is inaccessible / does not exist.
  • [LOW] Seldom fatal error when installing or updating (most likely caused by bad opcode optimization by PHP itself)

New features

  • Added optional filter to automatically exclude MyJoomla database tables

Miscellaneous changes

  • Better information about outdated PHP versions
  • Removed dependency on jQuery timers
  • Taking into account Joomla! 3.6's changes for the log directory location
  • Warn about broken eAccelerator
  • Work around broken hosts with invalid / no default server timezone in CLI scripts

Take me to the downloads for this version

Version 5.1.0 Stable

Released on: Tuesday, 07 June 2016 13:16

 

Maturity
Stable
Released on
Tuesday, 07 June 2016 13:16
Viewed
0 times

This is the stable version for Akeeba Backup 5.1.0. It supersedes the broken 5.0.x releases, fixes known issues in the beta versions and introduces new features.

What's new

Integrated restoration in the Core version. Users of Akeeba Backup Core, our free version, can now restore backups on the same server through the component, without having to upload Kickstart and go through all the manual restoration hassle.

Improved display of large log files. Some really big log files could crash the browser or cause a server timeout, preventing you from being able to download the log file. Now you have to explicitly allow the display of these large logs and when you do they are rendered using more efficient plain text display.

Improved tooltip display. Tooltips in the Configuration page are no longer static. If you want to make them static click on the label: the tooltip will remain open so you can use it as a reference for changing the respective configuration field. Please note that you can no longer copy text from tooltips as a result of this change.

Bug fixes. The 5.0.x series were arguably very buggy. Rewriting the component from scratch did introduce several obscure issues we had never run into before and couldn't test for: tests will only detect the problems the testers have run into into the past and designed their tests to detect. This time, with your collective feedback, we ran more tests than we thought was sane – and fixed the issues you reported and a few more which almost everybody missed. We hope we get bonus points for fixing issues caused by third party extensions that break the Joomla! core API (FaLang, I'm looking at you) and hosts disabling the public API to innocent built-in PHP features (Tokenizer) which exist in PHP for 10 years and are, ironically, used by PHP itself to parse PHP files. There are a few more obsure issues but we'll spare you the gory details; we fight these dragons so you don't have to.

We also fixed two obscure bugs regarding the use of a dollar sign followed by open curly brace in database passwords (due to a nearly undocumented PHP feature) and compatibility with newer servers where the get_magic_quotes_runtime function is correctly not available. We also noticed that many servers out there have operating system kernel core dumps in the public_html directory and you were backing them up. That's a waste of space so we now exclude all core dump files (named similar to core.1234) automatically. This will cause the backup size to decrease, substantially in many cases. Please don't report this to us as a bug, it's a bug in your server setup: these core dump files should never be there in the first place! Tell your host.

The following features were originally added in the 5.0.x series.

Automatic detection and working around of temporary data load failure. Some servers remove Akeeba Backup's "memory" files, causing the backup to fail. Now Akeeba Backup detects this error condition and automatically works around that, using the much slower but safer database storage instead.

Better workarounds for PHP opcode caches during and after backup extraction and site restoration.

Direct download link to Akeeba Kickstart in the Manage Backups page for easier manual restoration.

Easier discoverability of backup scheduling with links shown after the Configuration Wizard has completed and a toolbar button in the Configuration page.

Download log button in ALICE for easier filing of tickets.

Better workarounds for browsers' password auto-fill, making sure that the ANGIE and JPS password fields are not magically filled in by your browser with the wrong password.

Joomla! 3.4 or later

We only support Joomla! 3.4 or later, including 3.5. We strongly advise you to run Joomla! 3.4.7 or later for security reasons. Older versions of Joomla! have known major security issues which are being actively exploited to hack sites. Do note that these security issues were fixed on Christmas Eve 2015 thanks to the effort of our development team who contributed their time and knowledge to make Joomla! more secure.

PHP 5.4.0 or any later 5.x/7.x version is required

Support for PHP 5.3 is discontinued. It's end of life since August 2014 and widely considered a security risk, unfit for production sites. Our software requries PHP 5.4 or later and is compatible with PHP 5.4, 5.5, 5.6 and 7.0. We strongly recommend using PHP 5.6 or 7.0.

We'd like to remind you that Joomla! 3.4 does NOT support PHP 7. PHP 7 is only supported by Joomla! 3.5.0 and later versions. Akeeba Backup will work perfectly fine (and very fast!) on a Joomla! 3.5 or later site running on PHP 7.0.

Thank you, beta testers!

We want to sincerely thank all the people who took the time to download, install and test the two beta releases of Akeeba Backup 5.1.0. Their feedback has been invaluable in identifying and fixing all remaining bugs – including some obscure ones that have been there for several years. You guys and gals rock!

Changelog

Bug fixes

  • [HIGH] PHP's INI parsing "undocumented features" (read: bugs) cause parsing errors when certain characters are contained in a password.
  • [LOW] Database dump could fail on servers where the get_magic_quotes_runtime function is not available

New features

  • Better display of tooltips: you now have to click on the label to make them static
  • Big, detailed error page when you try to use an ancient PHP version which is not supported.
  • Do not automatically display the backup log if it's too big
  • Enable the View Log button on failed, pending and remote backups
  • Halt the backup if the encrypted settings cannot be decrypted when using the native CLI backup script

Miscellaneous changes

  • Automatically exclude core dump files

Take me to the downloads for this version

Version 4.7.3 Stable

Released on: Tuesday, 07 June 2016 11:49

 

Maturity
Stable
Released on
Tuesday, 07 June 2016 11:49
Viewed
0 times

Last release compatible with PHP 5.3 and Joomla! 1.6 to 3.3 (inclusive).

Release highlights

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

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

  • [HIGH] JSON API (remote) backups were broken if used a profile other than 1.
  • [LOW] Database dump could fail on servers where the get_magic_quotes_runtime function is not available

Critical bugs and important changes

  • Compatibility issues with PHP 5.3

Take me to the downloads for this version

Version 4.6.1 Stable

Released on: Sunday, 20 March 2016 13:00

 

Maturity
Stable
Released on
Sunday, 20 March 2016 13:00
Viewed
0 times

This is a new minor version release, adding new features.

Release highlights

Google Drive integration. On popular request we added native suport for Google Drive. Please read the documentation! Unlike other storage options file and folder names are not guaranteed to be unique in Google Drive, making for some interesting potential problems.

UTF8MB4 support under Joomla! 3.5. Akeeba Backup was already able to backup and restore database tables encoded in UTF8MB4 (Multibyte Unicode). Now you can use multibyte characters (e.g. Emoji) in the backup comment as well.

Ability to downgrade UTF8MB4 data to UTF8 during restoration. One challenge with the new UTF8MB4 support in Joomla! 3.5 is how do you move your site to a server which does not support UTF8MB4. Such a downgrade is nearly impossible to do manually. Luckily for you, Akeeba Backup can automatically perform the downgrade for you as long as you enable the option to convert the data to utf8 before restoring your database.

Joomla! 1.6 or later

This is not a typo! After considering the vast amount of changes in third party services Akeeba Backup integrates with (such as Dropbox and Amazon S3) we decided to reinstate compatibility 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

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

Critical bugs and important changes

  • Update failure on ancient servers lacking UTF8MB4 support

Take me to the downloads for this version

Version 4.5.5 Stable

Released on: Friday, 19 February 2016 14:56

 

Maturity
Stable
Released on
Friday, 19 February 2016 14:56
Viewed
0 times

This is a maintenance and bugfix release.

Release highlights

The file integrity check feature would fail on some servers because Joomla! randomly forgets to install a low importance plugin (the update notification email plugin). Unfortunately the only fix we can provide is disabling the file integrity / self-check feature of Akeeba Backup.

The backup check quick icon now launches a single click backup. Also, Improved display of the icon plugin.

Added option to automatically exclude hosting web stats (e.g. Webalyzer)

IMPORTANT! Behaviour change. The enryption of JPS archives was improved. As a result you need to use Kickstart 4.1.3 or later and UNiTE 2.0.2 or later to extract JPS archives taken with Akeeba Backup 4.5.2 and later. At this point Akeeba eXtract Wizard DOES NOT support the new improved JPS archive format. No further updates to eXtract Wizard are planned.

IMPORTANT! Behaviour change. All remote backup features (front-end URL, JSON API) will be automatically disabled if you are using a Secret Word that's not strong enough. This is done to protect your against brute forcing of the Secret Word which could allow attackers to take and download backups of your sites. Please read our release announcement for more information.

Integrated updater to be optionally used instead of Joomla!'s own extensions updater. Please note that under Joomla! 1.6, 1.7, 2.5, 3.0 and 3.1 you do not have a choice: you will use the integrated updater instead of Joomla!'s. If you try using Joomla!'s extensions updater under these old versions of Joomla! to update Akeeba Backup Professional you will get an error.

Extended Joomla! and PHP support. We now support Joomla! 1.6, 1.7, 2.5, 3.0, 3.1, 3.2, 3.3, 3.4 and 3.5 running on PHP 5.3.03 or later including PHP 5.4, 5.5, 5.6 and 7.0. Please note that not all versions of Joomla! run on all versions of PHP. Furthermore, we do NOT support PHP 5.2 even though older versions of Joomla! may run on it. If unsure please check our Compatibility page.

Joomla! 1.6 or later

This is not a typo! After considering the vast amount of changes in third party services Akeeba Backup integrates with (such as Dropbox and Amazon S3) we decided to reinstate compatibility with Joomla! 1.6, 1.7, 2.5, 3.0, 3.1, 3.2, 3.3 and also support the current Joomla! version 3.4 and the upcoming 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.

PHP 5.3.3 or later 5.x version is required

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

Critical bugs and important changes

  • The file integrity check feature would fail on some hosts due to Joomla!'s installer being broken. The feature was removed.

Take me to the downloads for this version

Version 4.4.3 Stable

Released on: Thursday, 29 October 2015 11:32

 

Maturity
Stable
Released on
Thursday, 29 October 2015 11:32
Viewed
9315 times

This is a bugfix and maintenance release. We suggest that all clients update.

Release highlights

One-click backup icons. Selected profiles will appear at the top of the Control Panel as icons. Clicking on an icon will start a backup using that profile immediately, without asking you any further questions.

More prominent site restoration and transfer instructions in the Manage Backups page. Once you visit Manage Backups for the first time you'll be shown a prominent popup with backup restoration and site transfer instructions. You can demote that popup to a reminder that appears above the list of backups if you get tired by the intrusive nature of the popup.

Several bug fixes, mostly regarding the cloud storage integrations (Professional version only).

Highlights from the previous 1.5.x releases

Simplified interface. You will notice substantial changes in the user interface as far as the control panel (main page), Manage Backups and Configuration pages go, as well as the backup restoration script (ANGIE). These changes were implemented as the result of our user experience (UX) study in partnership with UX experts Lucid Fox. This is just the beginning of this process, with the ultimate goal of making Akeeba Backup even easier to use.

Site Transfer Wizard. Yes, the Site Transfer Wizard is back! We wrote everything from the ground up, taking your feedback about easier site transfers to heart. We believe it's so self-explanatory that we decided to not document it; instead, all the instructions appear on the wizard itself as you use it. We are looking forward to your feedback on this feature which is available on both the Core (free of charge) and Professional (for a fee) versions!

New Amazon S3 engine. After several hard to fix issues with Amazon's official SDK we decided to write our own S3 engine. We read the API documentation, made ourselves a couple of gallons of coffee and three weeks later we have a faster, smaller and more stable S3 connection engine. Moreover, there's now only one "Upload to Amazon S3" Post-Processing option. If you were using the "Upload to Amazon S3 (Legacy)" option your backup profiles will be automatically upgraded. As a result of the smaller S3 engine size your backup size MAY be smaller after the update by one to two Megabytes.

We are aware that the video tutorials do not reflect the current interface and may be slightly off with regards to your experience using the component (the tutorials look more complicated than what you actually experience). We kindly ask for your patience as we're preparing new tutorials.

Joomla! 3.4 only

Only Joomla! 3.4 (and possibly 3.5 which is planned for release in a couple of months) is supported by this version. We strongly recommend using the latest Joomla! At the time of this writing it is 3.4.4. Using older versions is NOT recommended for security reasons.

PHP 5.4 or later 5.x version is required

The minimum required PHP version is 5.4.0. The component will not work on PHP 5.3 and will, in fact, refuse to install on it. We'd like to remind you that Joomla! 3.x does not currently support PHP 7. Since our software runs inside Joomla! by definition our software doesn't currently run on PHP 7 either.

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

  • [HIGH] Amazon S3 has a major bug with Content-Length on some hosts when using single part uploads. We are now working around it.
  • [HIGH] Chunked upload to OneDrive would result in an error
  • [HIGH] Multipart upload to S3 fails when the file size is an integer multiple of the chunk size
  • [HIGH] Only 5Mb would be transferred to Amazon S3 on some hosts with PHP compiled against a broken libcurl library; workaround applied.
  • [LOW] Extra databases definition page, trying to validate the connection without any information entered results in a success message
  • [LOW] Fixed backing up multiple external folders
  • [LOW] Fixed supplying additional Download ID directly from the Control Panel page
  • [MEDIUM] Using "Manage remote files" in the Manage Backups page could mangle backup profiles under some circumstances

New features

  • ANGIE: Added support for PrestaShop 1.4.x
  • More prominent site restoration and transfer instructions in the Manage Backups page
  • One-click backup icons. Select which profiles to display as one-click icons in Akeeba Backup's control panel

Take me to the downloads for this version

Version 3.4.6 Stable

Released on: Monday, 29 September 2014 19:00

 

Maturity
Stable
Released on
Monday, 29 September 2014 19:00
Viewed
34254 times

This is a security release addressing a high impact, but very unlikely, security issue with the Professional version's integrated restoration feature. All Professional users are advised to upgrade. For more information please consult our news article.

Please note that this old release of Akeeba Backup is end of life and no longer supported. This security fix is provided as a courtesy and does not imply that we will provide any kind of support for it.

Please consult our news article.

Additional note: this version also allows the software to run on servers using MySQL 5.6 or later.

Take me to the downloads for this version

Version 4.0.4 Stable

Released on: Tuesday, 30 September 2014 03:45

 

Maturity
Stable
Released on
Tuesday, 30 September 2014 03:45
Viewed
13919 times

This is a regular maintenance release of Akeeba Backup.

Release highlights for this version

Fixed issues with backups on Windows hosts using PHP 5.3. There is a bug on PHP 5.3 on Windows regarding the handling of open files which would cause an error regarding renaming the last part to .JPA when using a non-zero Part Size for Split Archives on a Windows host running PHP 5.3. This version of Akeeba Backup works around the PHP bug. To the best of our knowledge PHP 5.4, 5.5 and 5.6 on Windows, as well as all versions of PHP on Linux and Mac OS X are not affected by this bug.

Important note about RackSpace CloudFiles

Throughout September 2014 and at least until the time of this writing (September 13th, 2014) RackSpace is experiencing severe issues with their API stability. Even though all information you have entered in our software is correct you may get authentication, timeout or upload errors. This is not a bug in our software and we have no control over it. This is an issue with RackSpace and affects all software trying to connect to CloudFiles (e.g. CyberDuck). Moreover, the issues seem to be of an intermittent nature, both regarding time and region. Please do not file support requests and bug reports concerning CloudFiles. We will ignore them until we have determined that CloudFiles works consistently for at least 48 hours straight.

Release highlights for version family 4.0

Resumable backups. If a back-end backup halts with an AJAX error, Akeeba Backup will try resuming it. This allows the backup to complete when it halted due to a temporary network or server issue.

One log per backup attempt. On popular request, a different log file will be created for each backup attempt. This allows you to examine the impact of your configuration changes between backup attempts.

Simultaneous backups. You can now execute several backups at the same time using the front-end, remote JSON API and CLI methods. You are still only able to execute one back-end backup at a time for reasons that have to do with the Joomla! session management and the way browsers work.

Client-side minimum execution time delay. You can now have your browser enforce the minimum execution time preference. This reduces the processor load on the web server, allowing you to take more reliable backups on restrictive shared hosts.

Improved AJAX URL randomisation. The randomisation part of the AJAX action URL has been improved to avoid issues with the security rules of certain hosts. Essentially we will be avoiding cases similar to what happened with GoDaddy in June 2014.

Massive performance boost on large tables. You will observe a massive performance boost when backing up tables larger than a few thousand rows. This might shave up to 85% of the backup time of sites with huge database tables.

Work-arounds for several issues with third party code. We have devised and implemented workarounds for badly written third party code affecting Javascript execution on the page, as well as the badly written error pages of some hosts which contain page-modifying Javascript. Moreover we have worked around the majority of extremely zealous password managers which will auto-fill an irrelevant password into the ANGIE password and/or JPS password fields in the Configuration page without asking you, without letting you know, despite us using the standard autocomplete="off" attribute to let the browser know that it should never auto-fill that field. Our solution is to make the page slower to load and include a lot of delayed Javascript to reset the fields after the browser auto-fills them.

Support for the new MySQL (PDO) driver in Joomla! 3.4. That's right, we support Joomla! 3.4 before it's even released! Akeeba Backup 4.0.0 is designed to support the new MySQL PDO database driver which will be included in the upcoming Joomla! 3.4.0, due for release towards the end of September 2014.

Less hassle. Remember the Post-installation Configuration page you had to go through after each and every installation or update of Akeeba Backup? If you have Joomla! 3.2.0 or later (including 3.3.x and 3.4.x) you will no longer have to put up with it. We are now using the Post-installation Messages component included with Joomla! to display and manage the post-intallation / post-upgrade messages of our component.

Help us get more insight. Our software includes code to anonymously report your PHP, MySQL, Joomla! and Akeeba Backup version. This information cannot be linked to a particular site or person. It will help us get a glimpse at which versions are in use in real world servers, in what relative percentage, and let us to better plan our deprecation strategy. If you don't wish to take part to this anonymous data collection you can opt out from the component's Options page at any time.

PHP 5.3, 5.4, 5.5 or 5.6 is required

This version requires PHP 5.3, 5.4, 5.5 or 5.6. The rationale behind this is explained in our statement of mid-February 2013. It won't install on hosts running PHP 5.2 or earlier. PHP 5.3.4 or later is required, due to show-stopper bugs in earlier versions of PHP 5.3. Important note on reading PHP versions: PHP 5.3.20 is newer than 5.3.10 which is newer than 5.3.4. Moreover, PHP 5.4.0 is newer than PHP 5.3.4.

Due to the necessary Joomla! API changes found only in Joomla! 2.5.6 or later, this version will not install on Joomla! 2.5.5 or earlier versions. In any case, if your server doesn't meet the minimum requirements it will tell you exactly why it cannot be installed (minimum PHP or Joomla! version not satisfied).

Joomla! 2.5, 3.2, 3.3, 3.4 are supported

This version of our software can be installed on Joomla! 2.5.6 or any later 2.5.x release, as well as any 3.2.x, 3.3.x or 3.4.x release. It is not compatible with Joomla! 3.0 or 3.1. These versions of Joomla! are old and vulnerable. If you are using them please upgrade to the latest Joomla! 3 release available from Joomla.org.

Changelog

Critical bugs and important changes

  • [SECURITY: Medium] Possibility of arbitrary file writing while a backup archive is being extracted by the integrated restoration feature

Take me to the downloads for this version

Releases per page: