2.4 Beta 2

21 October 2009 Last updated on 16 January 2012

JoomlaPack 2.4 Beta 2 just released.

JoomlaPack Developers is pleased to announce the immediate availability of the new 2.4 Beta 2 formal release of our accredited Joomla! site backup component. This release addresses a serious show-stopper issue, hindering backing up your site if you are using a backup directory under your site's root. You can always download it following the links on our Downloads page. If you have any problems, suggestions, wishes or want to contact the team members, you can drop by our support forum.

If you find this software useful, please consider donating a small amount using the donation buttons found on the left hand column of this site and on the component's Control Panel page. This gives us the incentive to keep on coding great software and keeping it Free, both as in speech and as in beer!

We need your help

Help us help you, by submitting cool new ideas in our support forum. There is a dedicated section for feature requests. Ask for anything, even if you think it's nonsensical, ridiculous or not very useful. Remember that three years ago a reliable Joomla! backup solution written entirely in PHP, without requiring exec() privileges and able to work on slow servers was ludicrous. Then, JoomlaPack happened. Throw ideas around. We hear you and we try to implement them. You power Open Source, you power JoomlaPack!

Change log

The following is a list of changes since the last official release, 2.4.b2.

Bug fixes

  • Double slashes could cause the backup file to be backed up recursively, leading to infinite backup size increase (usually failing upon reaching 2Gb)
  • "Minimum execution time per step" feature, applied on ALL backup types. Fixes compatibility bugs with mod_evasive, mod_security, Joomla! Plugin Sentinelle and other anti-DDoS security solutions.
  • Automatic enforcement of 'raw' format type in front-end backup types (f.e.b. classic, CRON Helper Scripts' JSON and the Light Mode). This is a minor importance fix, as using the &format=raw part in the URL wouldn't expose this problem during normal use anyway.

On behalf of the JoomlaPack Project,

Nicholas K. Dionysopoulos
Lead Developer and Project Leader