Support

Akeeba Backup for Joomla!

#14113 My ticket #14111

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Tuesday, 13 November 2012 10:23 CST

SmossErKen

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: 3.0.2
PHP version: 5.3.x
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Akeeba Backup version: 3.6.8 (before update)

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:

Hi Nicholas,

Just want to inform you that my ticket with the number mentioned in title can be ignored. Typo ;)

I do want to let you know that the same issue as mentioned in another ticket (not mine) #13816 is occuring again. I know how to get it solved, but it is uncomfortable knowing that with the next available update (Admin Tools or Backup) I'll maybe have to fix this again.

Luckily this is not a production site but for testing purposes only :)

Β 

Best regards,

Chris

Β 

Kind regards,
Chris K.
Redpider Webdesign

nicholas
Akeeba Staff
Manager

Chris, that other ticket is a month old. Since then I have already published new versions of Admin Tools AND Akeeba Backup which have fixed this issue. As you can see in that thread, I confirmed the fix with the affected user so it's not like I'm making this stuff up. Which exact version of whihc software did you install and had this issue?

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!

SmossErKen

Hi Nicholas,

I'm sure you solved the issue earlier, but I still experience this atm. I was using Akeeba Backup Pro 3.6.8 (upgraded now to 3.6.9) and Akeeba Admin Tools Pro 2.4.1 (upgraded now to 2.4.2) on a Joomla 3.0.2 site. I removed the plugins/system/akeebaupdatecheck directory which solved the issue (site displayed normally again) after which I upgraded Akeeba Backup & Akeeba Admin Tools.

I'm using this site to test extensions, but apparently in this case it's the Akeeba Backup Updatecheck plugin that causes this issue.

Best regards,

Chris

Kind regards,
Chris K.
Redpider Webdesign

nicholas
Akeeba Staff
Manager

I will quote myself from the other ticket:

As you can read in Akeeba Backup 3.6.6's changelog I am already aware of it and have already fixed it :)

The bug you described doesn't happen anymore.

However, you do have a point. There is a completely different issue happening under Joomla! 3.0.x. If you have Admin Tools Professional installed on the site, this line is executed:

$model = JModel::getInstance('Storage','AdmintoolsModel');

but this doesn't work anymore in Joomla! 3 because some wise guy decided to rename the class to JModelLegacy. So, yes, there is a bug which nobody reported so far and it went unfixed. Now that I could reproduce it it was easy for me to fix, doing this:

if(version_compare(JVERSION, '3.0', 'ge')) {
$model = JModelLegacy::getInstance('Storage','AdmintoolsModel');
} else {
$model = JModel::getInstance('Storage','AdmintoolsModel');
}

This will be included in the next release. On that Joomla! 3.0 site of yours you should keep this plugin disabled until the next official release.

Now, regarding Joomla! 3.0, please note that it is definitely not a production-ready release. It is an unstable Joomla! release, recommended for use only by developers and people who don't mind their sites breaking badly every now and then. 3.1 will be a testing release, meaning that it will be more suitable (but still not recommended) for production sites. The next stable Joomla! release will be 3.5. And that's how we do testing for our software. Joomla! 2.5 is the currently stable release and this is where we make sure everything works perfectly. Joomla! 3.0 is an unstable release and doesn't enjoy the same level of testing. Obviously, since this bug went unreported for so long, my users also don't use it a lot :)

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!

SmossErKen

Hi Nicholas,

Thx for the info ! Of course Joomla 3.0.x is not suitable for production sites and I'm waiting for the release of Joomla 3.5 before even attempting to build a production site on this platform.

But in the meantime it is very interesting (and necessary) to 'test' all extensions offering Joomla 3.x compatibility on this platform.

Thx for the great support and have fun at the Joomla World Conference !

Best regards,

Chris

Kind regards,
Chris K.
Redpider Webdesign

nicholas
Akeeba Staff
Manager

But in the meantime it is very interesting (and necessary) to 'test' all extensions offering Joomla 3.x compatibility on this platform.

Absolutely! Doing that and reporting the bugs you find is the only way for us developers to make sure that when Joomla! 3.5 is released we will have stable, tested software for the new platform.

Thx for the great support and have fun at the Joomla World Conference !

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!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!