JoomlaPack 2.3.3 Maintenance Release just released.
JoomlaPack Developers is pleased to announce the immediate availability of the new 2.3.3 maintenance release of our accredited Joomla! site backup component. This release addresses incomplete database backups - usually associated with relevant PHP warnings - experienced by some of our users, especially those on shared hosts. If you were experiencing incomplete database backups you must urgently upgrade your JoomlaPack installation and retake a backup of your site.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!
Detailed information on the incomplete database backup issue
The Joomla!-powered (default) database backup engine had a minor bug which caused the database server being queried twice, in rapid successions, for the all of the table data which were being dumped. When this happened on tables holding many rows, or on tables with big data chunks per row a host-specific flood protection was triggered, causing an empty dataset to be returned from the database. Since this wasn't expected by the database engine - which had already determined that the table had more data to back up - it caused a PHP warning to be issued and the database dump of this table was incomplete. This problem manifested itself on slower, shared hosts and had gone undetected throughout the beta period, only reported a few hours before the release of our 2.3.1 version.
This release addresses the bug in question, removing the multiple queries per data chunk, which leads to greater backup engine stability and improved performance. If you were afflicted by this bug you are advised to urgently upgrade to release 2.3.3 and retake your backups.
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 about 30 months 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.3.2.
Bug fixes
- Stability problems in default database dumper, casuing incomplete database backups under certain circumstances
- Multiple databases definitions: a warning was shown if no records were found, prohibiting the creation of new multiple database definitions under certain configurations
- The Services_JSON class could already be defined, causing CRON backup errors
- The PEAER class could already be defined, causing backup errors when TAR or TAR.GZ engines were used
Known Issues
The following minor issues were known to our team at the time of release:
- Restoring a backup which includes MySQL views having also changed the database prefix will result in restoration errors.
- Changing the Super Administrator password in JPI4 has no effect.
- There is a possible Kickstart problem on IIS-powered hosts, causing the backup archive to not be extracted at all.
The importance of those issues was not considered critical. Therefore, we chose to release the 2.3.3 Maintenance Release anyway because the issues which were being addressed are more important and could cause serious backup failure, which is simply unacceptable for us. Be reassured that these known issues, as well as any others which might be found in the time following the release, will be addressed in the next official release.