Please help. And by the way, your products are the gold standard for all Joomla extensions. Thank you. Also, I consider my Joomla experience to be advanced/expert.
Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
I read AND FOLLOWED EACH STEP REPEATEDLY.
https://www.akeebabackup.com/documentation/troubleshooter/abbackup.html
https://www.akeebabackup.com/support/akeeba-backup-3x/11687-ajax-loading-error-http-status-500-while-backup.html
Have I searched the tickets before posting? Yes - I tried every suggestion I could find, most suggested changes to minimum, maximum time, bias
Have I read the documentation before posting (which pages?)? Yes - https://www.akeebabackup.com/documentation/akeeba-backup-documentation/instts-unsupportedjoomla.html
https://www.akeebabackup.com/home/news/56-releases/1485-akeeba-backup-3-6-0.html
https://www.akeebabackup.com/compatibility.html
And others.
Joomla! version: Version 2.5.6
PHP version: 5.2.17
MySQL version:5.0.77
Host: godaddy
Site: rubyredfrog.com
Akeeba Backup version: Akeeba Backup Professional 3.6.0 (2012-07-30)
Log file attached.
Description of my issue: I can backup my site, no problem when I use the normal backup procedure of clicking Backup Now tab or button. However, when I attempt to update on Control Panel using the method UPDATE FOUND CLICK TO UPDATE, the "automatic" backup starts but then fails almost instantly (see below for error message text). Important: The same thing happens when I try to complete the same type of upgrade to to Admin Tools.I have tried many different browsers - no change.
Please note that it appears the following issue would not happen (it seems to me) if I was presented with the option to NOT BACKUP AUTOMATICALLY before upgrading, because I can successfully backup the site by clicking the Backup Now button.
Message received:
Backup Failed
The backup operation has been halted because an error was detected.
The last error message was:
AJAX Loading Error
HTTP Status: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:
Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
I read AND FOLLOWED EACH STEP REPEATEDLY.
https://www.akeebabackup.com/documentation/troubleshooter/abbackup.html
https://www.akeebabackup.com/support/akeeba-backup-3x/11687-ajax-loading-error-http-status-500-while-backup.html
Have I searched the tickets before posting? Yes - I tried every suggestion I could find, most suggested changes to minimum, maximum time, bias
Have I read the documentation before posting (which pages?)? Yes - https://www.akeebabackup.com/documentation/akeeba-backup-documentation/instts-unsupportedjoomla.html
https://www.akeebabackup.com/home/news/56-releases/1485-akeeba-backup-3-6-0.html
https://www.akeebabackup.com/compatibility.html
And others.
Joomla! version: Version 2.5.6
PHP version: 5.2.17
MySQL version:5.0.77
Host: godaddy
Site: rubyredfrog.com
Akeeba Backup version: Akeeba Backup Professional 3.6.0 (2012-07-30)
Log file attached.
Description of my issue: I can backup my site, no problem when I use the normal backup procedure of clicking Backup Now tab or button. However, when I attempt to update on Control Panel using the method UPDATE FOUND CLICK TO UPDATE, the "automatic" backup starts but then fails almost instantly (see below for error message text). Important: The same thing happens when I try to complete the same type of upgrade to to Admin Tools.I have tried many different browsers - no change.
Please note that it appears the following issue would not happen (it seems to me) if I was presented with the option to NOT BACKUP AUTOMATICALLY before upgrading, because I can successfully backup the site by clicking the Backup Now button.
Message received:
Backup Failed
The backup operation has been halted because an error was detected.
The last error message was:
AJAX Loading Error
HTTP Status: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:
