Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.7
PHP version: 5.3.13
MySQL version: 5.1.63
Host: (optional, but it helps us help you)
Akeeba Backup version: Pro 3.6.5
EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.
Description of my issue:
Dear Nicholas,
Last night I reported you the bug in Akeeba Backup 3.6.4 over Twitter. (BommesX)
An explanation:
Tonight I was working and saw your tweet coming along that you updated Akeeba Backup to version 3.6.4.
I created backup and restorepoint before update. After updating I was not able to backup and configure Akeeba Backup Pro anymore. (You know the 500 error screen). But also I could not restore to version 3.6.3 anymore. A reinstall from version 3.6.3 was not working too. I contacted a friend of me to check if this was only with me, or with her too. She had same behavior and same crippled Akeeba Backup on complete different server. That was it that I thought to warn you and my followers to not update, using Twitter.
A few minutes after me, Brian Teeman posted his tweet that he created already brave a support ticket about same issue, When I visited your support system and saw that Brian and someone else already created tickets about the issue. I was thinking, doubling the ticket makes no sense.
Fortunately you fixed the issue really fast and released version 3.6.5. I really want to thank you for that.
After that I followed the discussion between you and Brian on Twitter.
I understand and respect that you do not want to give support over Twitter, and I never asked you for that. I only wanted to help you not spreading a bug with your extension-update by fast reporting. How earlier find and fix bug, how less support-work it gives to you.
Generally I can help myself and know how to restore to previous versions of a extension or joomla! version. But not everyone is that handy.
I also know the way to your website and your support-ticket system.
Unfortunately I know (and you too I assume) many people hitting the update-buttons without creating backups. Many trust also on the restore-point functionality of Akeeba Backup.
But when Akeeba update cripples it's own restore-point-, configure- and backup-functionality, where people on rely, there we have a main issue!
That's why I used Twitter to report fast to you and my followers not to update. I really never wanted to offend, blame or something else to you.I wanted to help you by reporting!
Your first reactions(tweets) to me were very offending. It's not nice to get such a reaction when you only want to help. Maybe you worked very hard this day and you were very tired, but I think it is not the way to respond to your customers or people anyway. I know your reactions can be rude also to others, also on your previous Twitter account. And I know also that some people can react very stupid or rude against you!
But: please realize that from people you treat respectfully you get much more back in live, as from beaten or rude treated people.
In Dutch we have a proverb: "Voer geen oorlog voer de eendjes". It means something like: "Don't feed the war, feed the little duckies".
I only wanted to say this to you!
Finally: I still am a big fan of your extensions and I still will spread the positive words about your extensions in our Joomla! usergroups and on multiple Joomla! forums.
Best regards and have a nice weekend,
Benno Stulemeijer
BTW: I do not mind when you delete this ticket after read (but maybe copy first ;-))
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.7
PHP version: 5.3.13
MySQL version: 5.1.63
Host: (optional, but it helps us help you)
Akeeba Backup version: Pro 3.6.5
EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.
Description of my issue:
Dear Nicholas,
Last night I reported you the bug in Akeeba Backup 3.6.4 over Twitter. (BommesX)
An explanation:
Tonight I was working and saw your tweet coming along that you updated Akeeba Backup to version 3.6.4.
I created backup and restorepoint before update. After updating I was not able to backup and configure Akeeba Backup Pro anymore. (You know the 500 error screen). But also I could not restore to version 3.6.3 anymore. A reinstall from version 3.6.3 was not working too. I contacted a friend of me to check if this was only with me, or with her too. She had same behavior and same crippled Akeeba Backup on complete different server. That was it that I thought to warn you and my followers to not update, using Twitter.
A few minutes after me, Brian Teeman posted his tweet that he created already brave a support ticket about same issue, When I visited your support system and saw that Brian and someone else already created tickets about the issue. I was thinking, doubling the ticket makes no sense.
Fortunately you fixed the issue really fast and released version 3.6.5. I really want to thank you for that.
After that I followed the discussion between you and Brian on Twitter.
I understand and respect that you do not want to give support over Twitter, and I never asked you for that. I only wanted to help you not spreading a bug with your extension-update by fast reporting. How earlier find and fix bug, how less support-work it gives to you.
Generally I can help myself and know how to restore to previous versions of a extension or joomla! version. But not everyone is that handy.
I also know the way to your website and your support-ticket system.
Unfortunately I know (and you too I assume) many people hitting the update-buttons without creating backups. Many trust also on the restore-point functionality of Akeeba Backup.
But when Akeeba update cripples it's own restore-point-, configure- and backup-functionality, where people on rely, there we have a main issue!
That's why I used Twitter to report fast to you and my followers not to update. I really never wanted to offend, blame or something else to you.I wanted to help you by reporting!
Your first reactions(tweets) to me were very offending. It's not nice to get such a reaction when you only want to help. Maybe you worked very hard this day and you were very tired, but I think it is not the way to respond to your customers or people anyway. I know your reactions can be rude also to others, also on your previous Twitter account. And I know also that some people can react very stupid or rude against you!
But: please realize that from people you treat respectfully you get much more back in live, as from beaten or rude treated people.
In Dutch we have a proverb: "Voer geen oorlog voer de eendjes". It means something like: "Don't feed the war, feed the little duckies".
I only wanted to say this to you!
Finally: I still am a big fan of your extensions and I still will spread the positive words about your extensions in our Joomla! usergroups and on multiple Joomla! forums.
Best regards and have a nice weekend,
Benno Stulemeijer
BTW: I do not mind when you delete this ticket after read (but maybe copy first ;-))
