Support

Akeeba Backup for Joomla!

#12264 Akeeba Backup 3.5a2

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 Saturday, 12 May 2012 03:10 CDT

Friday, 11 May 2012 21:44 CDT

kimhuff
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the tickets before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: (2.5.4)
PHP version: (5.2.14)
MySQL version: (5.0.77)
Host: (Dedicated)
Akeeba Backup version: (3.4.3)

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:

I did not attach the log because I felt I had a generic question.

I tried upgrading to the 3.5a2 which I know was in alpha. It did not work so I had to go back to the older version. My question, I only want to Joomla to remind me of "stable" updates. I do not mind testing out alpha and beta extensions on non-live sites, but I do not want it to pop up telling me to update unless it is a stable release.

I know there is a section in options that talks about alpha, beta, RC and stable and I have checked STABLE ONLY. But, for some reason, Joomla keeps telling me to update.

Any suggestions would be greatly appreciated.

Have a GREAT weekend!

Kim Huff
Indianapolis, Indiana

Saturday, 12 May 2012 02:40 CDT

nicholas
Hi Kim,

This is a limitation of Joomla!'s extension updater. It will remind you of any version, no matter the stability. The next version of Akeeba Backup will remove support for Joomla!'s extension updater and use it own (Live Update) which actually respects your minimum stability settings. I am also going to make a few more changes in Live Update to make it very hard to accidentally install an unstable release. Basically, I want it to display a big warning message when you try installing an alpha, beta or RC version, something which is not possible with Joomla! extension updater.

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!

Saturday, 12 May 2012 03:03 CDT

kimhuff
Thank you for the quick response.

Do you know if it has been determined why the 3.5a2 is causing the main control panel page in Joomla to be blank? I was able to get around it with your suggestions by renaming the file, but I had to go back to the stable version to make Akeeba work. I have not installed it on a fresh install of Joomla, but I did install it on a Joomla 1.7 that had been updated to 2.5.

Thank you for all you do.

Kim

Saturday, 12 May 2012 03:10 CDT

nicholas
Yes, I have. It's a known Joomla! issue. When you are updating a component and there are new top-level directories or files in the new version, the first time you try to install the update these directories are not copied. This causes the component to be in a half-installed state and not work properly. By default, we are installing the mod_akadmin module which adds an icon in the control panel to notify you of the need to backup your site. When the module tries to load the backup engine to query the backup status, a fatal error is thrown because the component is in a half-installed state. The workaround is to remove the module and install the same version of the component on top of what you already have. Joomla! now copies all of the directories and, what do you know, everything works... Unfortunately, fixing this is beyond what I can do on my end. The only thing I could do would be entirely sidestepping Joomla! and using my own installer, but I consider this a silly approach. Instead, I am doing something different. I have modified the icon module to deactivate itself if it causes a fatal error, thus allowing you to log back in and reinstall the component without having to use FTP.

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!