Akeeba Backup for Joomla!

Wednesday, 12 January 2011 15:07 CST

user13813

Backup Pro has been running fine as a cron job on Lunarpages on both production and development website (2 separate backups). I now receive the following error on the production website:



Starting a new backup with the following parameters:

Profile ID  1

Description "Command-line backup"



Domain	: 

Step	: 

Substep	: 






Fatal error:  Class 'JText' not found in /home/tstte9/public_html/libraries/joomla/utilities/date.php on line 296

The development website is set up with the exact same profile and it works OK.

I did see another post related to the use of the [WEEKDAY] field in the backup name as being a cause of the same JText error. I have confirmed that I do not use that field. My backup name is as follows: PRD-[HOST]-[DATE]-[TIME]

Any help is appreciated. Please help!
Thanks

Tim

Edited by user13813 on 2011-01-12 15:11 CST

Wednesday, 12 January 2011 15:39 CST

nicholas

This is a known issue. It was fixed in Akeeba Backup 3.2.b4. Can you install that version and verify the fix, please? Thank you!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 12 January 2011 15:50 CST

user13813

Both prod and dev are using v3.1.5.

I can try to upgrade to v3.2.b4 however:
- This was working fine up until 2 weeks ago. With no changes to the backup software or the host environment that I know of.
- The exact same profile works fine for the dev web site.

Is there addtional information you can provide on what would casue this to stop working only on one web site.

Thanks
Tim

Wednesday, 12 January 2011 17:17 CST

nicholas

The root cause of the problem is that some date parameters require JText which wasn't being loaded in the CRON mode backup. These are used in many places, including the directory names of post-processing engines (e.g. S3, DropBox, etc). The only way to trigger that is use some of those parameters anywhere in Akeeba Backup's configuration. 3.2.b4 solves this issue. So, you have two options:
1. Find where you're using any of those variables and remote it, or
2. Install 3.2.b4

Do note that the bug will only be triggered from a command-line CRON backup. It will not be triggered by a back-end backup or any other backup method.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 20 January 2011 10:56 CST

user13813

I upgraded to v3.2.b4 as instructed and the issue seems to be resolved.

Thanks for your quick response.
Tim

Edited by user13813 on 2011-01-20 10:57 CST

Thursday, 20 January 2011 12:14 CST

nicholas

You're welcome!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support