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!

Here you will find the downloads to Akeeba Backup for Joomla!, our award-winning full site backup and transfer component for Joomla!. Both the Core (free) and Professional (paid) editions can be found in here.

Download and install translation files from our translations page

Stable 4.5.3

Maturity
Stable
Released on
Tuesday, 09 February 2016 03:23
Viewed
0 times

This is a maintenance release.

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.

Moreover, the enryption format of JPS archives (available in the Professional version) is 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.

Release highlights

Backup check quick icon module for Joomla! 1.6/1.7. 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. If you do choose to use it, well, now you have an icon module to notify you about the necessity to take backups.

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 System – Akeeba Backup Update Check plugin caused Admin Tools to fail with a white page

Take me to the downloads for this version

Stable 4.5.2

Maturity
Stable
Released on
Sunday, 07 February 2016 10:31
Viewed
0 times

This is a maintenance release.

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.

Moreover, the enryption format of JPS archives (available in the Professional version) is 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.

Release highlights

Backup check quick icon module for Joomla! 1.6/1.7. 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. If you do choose to use it, well, now you have an icon module to notify you about the necessity to take backups.

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

Bug fixes

  • [HIGH] ANGIE for Drupal 7: Fixed fatal error in setup page
  • [HIGH] Static Initialization Vector (derived from the encryption key) for Rijndael-128 encryption in JPS files and app settings weakened the encryption strength
  • [LOW] A fatal error is recorded in the PHP error log if you try to access a front-end view which doesn't exist
  • [MEDIUM] ANGIE for Wordpress: Fixed data replacement in case-sensitive filesystems
  • [MEDIUM] Some servers with problematic libcurl implementations are unable to use Dropbox API v2, always receiving an error message.
  • [MEDIUM] Upload to OneDrive occasionally fails when their API doesn't report the folder creation correctly

New features

  • Added option to automatically exclude hosting web stats (e.g. Webalyzer)
  • Backup check quick icon module for Joomla! 1.6/1.7
  • The backup check quick icon now launches a single click backup

Miscellaneous changes

  • Disable CLI script workaround necessary only under Joomla! 3.4.7 on all other versions of Joomla!
  • Improved display of backup check quick icon module

Critical bugs and important changes

  • Joomla! 3.5 breaks CLI scripts, workaround applied

Take me to the downloads for this version

Stable 4.5.1

Maturity
Stable
Released on
Tuesday, 22 December 2015 08:49
Viewed
0 times

This is a bugfix release, addressing a major issue regarding CLI scripts introduced by Joomla! 3.4.7 as well as other known issues.

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.

Release highlights

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.

Workaround for CLI scripts. Joomla! 3.4.7 introduced a major bug which made it impossible for third party CLI scripts, used in CRON jobs, to complete successfully. Unfortunately it also affected the CLI scripts of our own software. This release applies a workaround which lets the CLI scripts execute without a problem.

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.

Text log in ALICE, the log analyzer. You can paste that text when you are requesting support to help us help you more efficiently.

Automatically run ALICE if an error occurs (only applies to backups taken from the interactive web interface).

Support for Amazon S3's Standard- Infrequent Access storage type (Professional versions only)

More stable Site Transfer Wizard thanks to improved transfer chunk size calculations

Security update #1 (low importance issue). Someone who already knows your Secret Word can store XSS in the database if the remote backup is enabled and you're not using the security enhanced .htaccess file (discovered by NCC Group). Low importance because this security issue requires the attacker to already know your Secret Word. However, if they have it they can already take and download backups of your site, exposing you to much higher and immediate risk. Therefore we consider it a low importance issue: it requires your site to essentially be already compromised.

Security update #2 (low importance issue). Open redirection in back-end backups (discovered by Calum Hutton, NCC Group). This only works if you are able to run an automatic backup while already logged in to your site's back-end as a Super User. Furthermore, this requires that the attacker knows the session token. As a result, the only way to exploit this is by using a malicious Joomla! extension running on your site while you are logged in as a Super User. In this case the malicious extension has already fully compromised your site BEFORE it can exploit this security issue. Therefore we consider it a low importance issue: it requires your site to be already fully compromised.

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.

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

Bug fixes

  • [HIGH] Joomla! 3.4.7 has a major bug which prevents CLI (CRON) scripts from executing
  • [HIGH] MySQL error on Joomla! 1.6 when updating statistics
  • [HIGH] Possible backup failure when the database being backed up is of a different type (e.g. PostgreSQL vs MySQL) than the one containing the backup profile configuration
  • [HIGH] The Configuration Wizard popup is illegible under Joomla! 3.x
  • [LOW] "Copy" label untranslated in Profiles page under Joomla! 1.6
  • [MEDIUM] Automatic update CLI script throws fatal error
  • [MEDIUM] Test FTP Connection results didn't display properly under Joomla! 3.x
  • [MEDIUM] Test SFTP Connection results didn't display properly under Joomla! 1.x / 2.5

Take me to the downloads for this version

Stable 4.5.0

Maturity
Stable
Released on
Friday, 18 December 2015 05:23
Viewed
0 times

This is a major features and security release. We suggest that all clients update.

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.

Release highlights

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.

Text log in ALICE, the log analyzer. You can paste that text when you are requesting support to help us help you more efficiently.

Automatically run ALICE if an error occurs (only applies to backups taken from the interactive web interface).

Support for Amazon S3's Standard- Infrequent Access storage type (Professional versions only)

More stable Site Transfer Wizard thanks to improved transfer chunk size calculations

Security update #1 (low importance issue). Someone who already knows your Secret Word can store XSS in the database if the remote backup is enabled and you're not using the security enhanced .htaccess file (discovered by NCC Group). Low importance because this security issue requires the attacker to already know your Secret Word. However, if they have it they can already take and download backups of your site, exposing you to much higher and immediate risk. Therefore we consider it a low importance issue: it requires your site to essentially be already compromised.

Security update #2 (low importance issue). Open redirection in back-end backups (discovered by Calum Hutton, NCC Group). This only works if you are able to run an automatic backup while already logged in to your site's back-end as a Super User. Furthermore, this requires that the attacker knows the session token. As a result, the only way to exploit this is by using a malicious Joomla! extension running on your site while you are logged in as a Super User. In this case the malicious extension has already fully compromised your site BEFORE it can exploit this security issue. Therefore we consider it a low importance issue: it requires your site to be already fully compromised.

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.

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

Bug fixes

  • [HIGH] ANGIE for Drupal: Fixed endless loop while trying to read the configuration
  • [LOW] ANGIE for Wordpress: Fixed missing email address in site setup
  • [LOW] ANGIE for Wordpress: Fixed missing version number
  • [LOW] Low encoding of media folder permissions check could show an erroneous message on some sites (thanks Angel!)
  • [LOW] Notice thrown by the auto-update CLI script
  • [LOW] Open redirection in back-end backups (discovered by Calum Hutton, NCC Group)
  • [LOW] Site Transfer Wizard, bad performance of the test FTP/SFTP servers could lead to an instant error when accessing this feature
  • [LOW] Someone who already knows your Secret Word can store XSS in the database if the remote backup is enabled and you're not using Joomla!'s or Admin Tools' .htaccess file (discovered by Calum Hutton, NCC Group)

New features

  • Added textual output to ALICE so it could be included in support tickets
  • Automatically run ALICE if an error occurs during the last domain of a backup
  • Integrated updater (optional for Joomla! 3.2+, mandatory for Joomla! 1.x/2.x/3.0/3.1)
  • Support for Amazon S3's Standard- Infrequent Access storage type

Miscellaneous changes

  • More stable Site Transfer Wizard thanks to improved transfer chunk size calculations
  • Now compatible with Joomla! 1.7, 2.5, 3.0, 3.1, 3.2, 3.3, 3.4 and 3.5 running on PHP 5.3.03+, 5.4, 5.5 and 5.6.

Critical bugs and important changes

  • Front-end and remote backup features will be DISABLED if we detect an insecure Secret Word

Take me to the downloads for this version

Stable 4.4.3

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

Stable 4.4.2

Maturity
Stable
Released on
Wednesday, 14 October 2015 11:08
Viewed
12352 times

This is a stable release of Akeeba Backup with significant changes both in the user interface and under the hood.

Release highlights

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 multipart uploads. We are now working around it.
  • [HIGH] Google Storage and DreamObjects would not work
  • [HIGH] Obsolete jQuery Tooltip plugin could cause JavaScript errors
  • [HIGH] Under rare circumstances temporary data could be committed to the database and break future backups.
  • [HIGH] Upload to S3 would fail due to cacert.pem issues with some hosts and versions of PHP
  • [HIGH] Upload to S3 would fail if a file was an integer multiple of the Amazon S3 chunk size (5242880)

Take me to the downloads for this version

Beta 4.4.2.b1

Maturity
Beta
Released on
Thursday, 01 October 2015 10:37
Viewed
3332 times

This is a beta release of Akeeba Backup with significant changes both in the user interface and under the hood. If you find any issues please let us know by submitting a bug report in our Contact Us page (even if you are not a subscriber) or by filing a support request in our Ticket System (only if you are a subscriber).

If you have version 4.4.0 or 4.4.1 installed we recommend either downgrading to the previous version (4.3.1) or installing this beta release.

Release highlights

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.3/3.4 only

Only Joomla! 3.3 and 3.4 (and 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

We have raised the minimum PHP version requirement to 5.4.0 in this version. The component will not work on PHP 5.3 and will, in fact, refuse to install 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] No error thrown when the engine state cannot be saved while the backup is in progress
  • [HIGH] The database storage option for the temporary data didn't work
  • [LOW] Database schema self-healing was disabled
  • [LOW] The backup size would be inflated if "Upload each part immediately" is enabled and it takes multiple step to post process a single archive part [PRO]
  • [MEDIUM] FTP/SFTP browser would fail on some servers when you don't provide a starting directory [PRO]
  • [MEDIUM] Updated Dropbox post processing engine due to changes on their servers [PRO]

New features

  • "Exclude error logs" filter, enabled by default, to prevent broken backup archives when error logs change their size / are rotated while the backup is in progress
  • ANGIE: Added throttle speed for replacing data
  • Akeeba Backup will ask you to enter your Download ID before showing you available updates. [PRO]
  • Akeeba Backup will ask you to run the Configuration Wizard when it detects it's necessary. One less thing for you to remember!
  • Automatically exclude folders related to version control systems
  • JSON API: Return an error if preflight configuration checks indicate a critical error (e.g. output directory not writeable)

Miscellaneous changes

  • ANGIE: Removed the confusing messages about restoring to a different site or PHP version
  • ANGIE: Simplified the final page ("Finished")
  • CLI scripts should now print a warning instead of immediately dying if you try running them in PHP 5.2 or earlier (what are you doing with this kind of archaic PHP versions on your production servers anyway?!!) [PRO]
  • Desktop notifications are now optional. If you have already enabled them don't worry, they won't be disabled (your browser remembers the previous setting).
  • Improved layout for the Control Panel page
  • Make it more obvious that the Scheduling Information tabs actually DO work when you click on them
  • Manage Backups: "Part 00" would be displayed when there is just one backup part present. Button label changed to "Download".
  • Manage Backups: Simplified the page layout
  • New icon colour palette for easier identification of the Control Panel icons
  • No more yellow flash when loading the Akeeba Backup control panel page
  • Remove the title from the popover tips
  • The profile ID is displayed in the profile selection drop-down

Removed features

  • Removed post-installation messages
  • Removed the "Upload to Amazon S3 (legacy API)" post-processing engine. Existing backup profiles will be automatically migrated to the "Upload to Amazon S3" engine. [PRO]

Take me to the downloads for this version

Stable 4.3.1

Maturity
Stable
Released on
Thursday, 06 August 2015 01:18
Viewed
35961 times

This release of Akeeba Backup fixes a low priority, minor, cosmetic issue. Never before have we released a new version within a day just to address such a low priority, minor, cosmetic issue. We have not even done this with medium priority issues which could have some operational impact to the software. But given the amount of communication we received over the least important cosmetic bug in the 9 years of this project's history we made a new release and have to ask you to please stop contacting us about the wrong dispkay of the total backup size. Thank you.

Release highlights

This release of Akeeba Backup fixes a low priority, minor, cosmetic issue. Never before have we released a new version within a day just to address such a low priority, minor, cosmetic issue. We have not even done this with medium priority issues which could have some operational impact to the software. But given the amount of communication we received over the least important cosmetic bug in the 9 years of this project's history we made a new release and have to ask you to please stop contacting us about the wrong dispkay of the total backup size. Thank you.

Joomla! 3.3/3.4 only

Only Joomla! 3.3 and 3.4 (and 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.3. Using older versions is NOT recommended for security reasons.

PHP 5.4 or later 5.x version is required

We have raised the minimum PHP version requirement to 5.4.0 in this version. Even though the component might work on PHP 5.3 we have no tested it with it and we will not support 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

  • [LOW] Core: Archive integrity test would not run due to a file not being installed
  • [LOW] The Size in Manage Backups would be wrong as the last part's size was counted twice

Take me to the downloads for this version

Stable 4.2.4

Maturity
Stable
Released on
Monday, 22 June 2015 19:00
Viewed
27893 times

This is a bugfix and features release of Akeeba Backup, solving some issues regarding restoration of sites on different MySQL versions and an issue affecting uploads to Dropbox on PHP 5.5 and 5.6.

Alternatives to obsolete features removed in 4.2.0

Since Akeeba Backup 4.2.0 the features deprecated since 4.0.0 have been removed. Below you can find alternatives if you miss the functionality and need an equivalent solution.

Post-setup page. All messages are now handled through Joomla!'s Post-Installation Messages component. This change first appeared in Akeeba Backup 4.0 when installed on Joomla! 3.2 and later. Now this is now the only way to review the post-installation messages.

Site Transfer Wizard. The wizard didn't make site transfers possible, it only helped you set up the backup profile. You can still use the DirectFTP and DirectSFTP archiver engine to the same effect – after all, that's the only thing the wizard did for you, enable these archiver engines. However we recommend using regular JPA or ZIP backup archives with the Upload to FTP and Upload to SFTP post-processing engines along with the Upload Kickstart option. This new method is much more stable and far less likely to fail midway through the site transfer.

System Restore Point and Extension Filters. These two features were removed for the same reason: since Joomla! 1.6 it is no longer feasible to backup and restore, or even exclude, a single extension of your site. Joomla!'s ACL system means that everything in it (articles, categories, extensions and even third party items) are linked together through the #__assets table. On top of that, the Tags and Content Versioning features added in Joomla! 3.1 and 3.2 respectively made everything also depend on the UCM set of tables. Due to the way these tables are constructed it's impossible to make a complete backup of an extension's state without also backing up the entire system states. This makes the System Restore Points either incomplete backups (they were, indeed) or would make their restoration potentially kill your site (we didn't go that way for obvious reasons). Furthermore, removing a single extension would either leave behind orphan records or create holes in the tables, both options leading to database inconsistencies which could make your site fail to work correctly. For these reasons we removed both features and have to note that no, they DID NOT work properly in Joomla! 1.6, 1.7, 2.5, 3.0, 3.1, 3.2, 3.3 and 3.4; no, they cannot be fixed (what do you think we were trying to do the last four years?); and no, they are not coming back exactly because they DO NOT work and CAN NOT be made to work. There is no alternative. We recommend simply taking full backups of your site before any major change such as upgrading to a new major version of an extension.

Lite Mode. This feature was developed back when featurephones with limited web browsers were the norm. In the eight years which have elapsed since that time smartphones with full featured browsers became the norm, Joomla! became responsive and other mobile devices with full features web browsers (tablets, netbooks / mini-laptops such as the 2015 MacBook, two-in-ones such as Microsoft Surface Pro etc) have emerged. For this reason the easiest, most stable and outright convenient way to back up your site while on the move is logging in to the backend of your Joomla! 3 site from your mobile device and use Akeeba Backup normally. Our interface is responsive and touch-optimised since mid-2012!

Joomla! 3.3/3.4 only

Only Joomla! 3.3 and 3.4 (and 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.1. Using older versions is NOT recommended for security reasons.

PHP 5.3.4 or later 5.x version is required

This version requires PHP 5.3.4 or later (e.g. 5.3.29 which is twenty five versions newer than PHP 5.3.4), 5.4, 5.5 or 5.6. Please note that PHP 5.3 is obsolete since August 2014 and we're going to stop supporting it without warning in future versions of our software. 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] Restoring on MySQL would be impossible unless you used the MySQL PDO driver
  • [LOW] Desktop notifications for backup resume showed "%d" instead of the time to wait before resume
  • [LOW] Push notifications should not be enabled by default
  • [MEDIUM] Dropbox integration would not work under many PHP 5.5 and 5.6 servers due to a PHP issue. Workaround applied.

New features

  • Support utf8mb4 in CRON jobs

Miscellaneous changes

  • ANGIE: Improve memory efficiency of the database engine
  • Switching the default log level to All Information and Debug

Take me to the downloads for this version

Stable 4.1.2

Maturity
Stable
Released on
Monday, 02 February 2015 18:00
Viewed
74219 times

The most major issue fixed affect sites hosted on really bad hosts which block the innocent parse_ini_file() PHP function when they really meant to block the ini_set() function which can have security implications on very badly configured servers. In other words if you didn't see most interface icons with Akeeba Backup 4.1.0/4.1.1 you are hosted on a really bad host who has no idea about PHP security. In this case we strongly recommend you to immediately move your site to a decent host, for security reasons.

Additionally we fixed some issues affecting the restoration and a high priority issue which would result in the partial inclusion of the restoration script (with a warning), making it impossible to perform a proper restoration.

Finally, we'd like to remind you that this is the last version of Akeeba Backup with Joomla! 2.5 support. Future versions will only support the latest Joomla! 3 release.

Bugfix release

This is a bugfix release of Akeeba Backup. The most major issue fixed affect sites hosted on really bad hosts which block the innocent parse_ini_file() PHP function when they really meant to block the ini_set() function which can have security implications on very badly configured servers. In other words if you didn't see most interface icons with Akeeba Backup 4.1.0/4.1.1 you are hosted on a really bad host who has no idea about PHP security. In this case we strongly recommend you to immediately move your site to a decent host, for security reasons.

Additionally we fixed some issues affecting the restoration and a high priority issue which would result in the partial inclusion of the restoration script (with a warning), making it impossible to perform a proper restoration.

Changelog

Bug fixes

  • [HIGH] ANGIE (restoration): Some bad hosts disable the innocent parse_ini_file PHP function resulting in translation and functional issues during the restoration
  • [HIGH] Missing interface options on bad hosts which disable the innocent parse_ini_file PHP function
  • [LOW] ANGIE for Wordpress: fixed changing Admin access details while restoring
  • [LOW] Configuration Wizard: detected minimum execution time was ignored; default value of 2 seconds always applied
  • [LOW] On some hosts you wouldn't get the correct installer included in the backup
  • [MEDIUM] ANGIE for Wordpress: Site url was not replaced when moving to a different server

New features

  • ANGIE for Wordpress: Db collation set to "utf8_general_ci" by default
  • Added "Apply to all" button in Files and Directories Exclusion page

Take me to the downloads for this version

Stable 4.0.5

Maturity
Stable
Released on
Tuesday, 30 September 2014 15:14
Viewed
72959 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

Bug fixes

  • [HIGH] The integrated restoration is broken after the last security update

Take me to the downloads for this version

Stable 3.2.10

Maturity
Stable
Released on
Monday, 29 September 2014 19:00
Viewed
22807 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

Stable 3.4.6

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

Stable 4.0.4

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: