Support

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 updated to Akeeba 4.7.5 from a much earlier version 4.1.2 (2015-02-03) - seems this might have been a bit ambitious! It gave an error that FOF not installed as in attached pic. I tried a second install as suggested in one of the other fault reports but no different.
Is there a simple fix or perhaps best if I do an uninstall and first time install my setup is simple.

I did take a backup before starting using the old 4.1.2 version - log file attached. Had hoped to update site to Joomla! v3.6 in next few days.
Colin

Colin,

We can beat it into submission. Please try to install Akeeba Backup twice, back to back, without doing anything in between. This usually works around a problem with the Joomla! installer where it fails to copy some files during an installation or update.

If it still gives you problems, please download FTP 3.0.18 from our Downloads page and install it separately.

Dale
The Double install did not work. So I downloaded FoF 3.0.18 as suggested. That installed AOK. But Akeeba backup still not working. So tried another install and got same error message as before.
Is FOF 3.0.18 OK for Joomla! 2.5.28 or should it have an earlier one? Script script.fof.php indicates it is only for version 3.3 and above. I did not get a minimum version error.
I also looked at the install script for Akeeba 4.7.5 and this says OK for Joomla 2.5
The error message says it cannot find file 'Autoloader' but should it be looking for 'Autoloader.php'?

Colin

Colin,

I apologize, I missed that it was 2.5. Let's rename /libraries/f0f/version.txt, then the installer won't "find" it and will reinstall. After you rename, you can install Akeeba Backup again and that should work. The FOF (the name changes depending on the version) library is shared between multiple Akeeba packages, and some third party packages. If the installer sees that it is already there, it doesn't reinstall. That's great except when you're trying to force a reinstall and the installer outsmarts you.

Hi
I still have a problem! Noted it was zero in f0f.
Renamed /f0f/version.txt to /f0f/OLDversion.txt then uploaded and installed com_akeeba-4.7.5-pro.zip but again failed with same error message. So did another install immediately - no joy!!

The first error message is
JInstaller: :Install: File does not exist /home/site-name/public_html/tmp/install_58ff5266a6016/fof/Autoloader

It seems to be trying to find something called 'Autoloader' in the install package in directory /fof/ so I looked in the unzipped com_akeeba-4.7.5-pro.zip. There is a directory fof and it contains a directory 'autoloader', not 'Autoloader'. Directory fof does not contain any files, only directories. There are references in the code to both Autoloader.php and autoloader.php
So what next as I am a bit confused.
Colin

Dale
Decided to try 4.7.4 it loaded aok. Seems to me distribution 4.7.5 is flawed.
The version.txt file contains
2.5.4
2016-03-19

I deleted OLDversion.txt

Colin

Colin,

You are correct, there was a problem with 4.7.5. Nicholas just fixed it and re-uploaded the file. There is no version number change, so it is still 4.7.5.

Thank you for the report!

Dale,
Thanks for follow up. I have just successfully installed 4.7.5 (also please thank Nicolas for fast support).
I will start another backup when I have done working this evening, and report on its operation.

Which version of Kickstart would you recommend? I guess 4.2.1 is compatible rather than the v5 series.

Thanks
Colin

PS just for info I work with Arno Betz on the jDownloads component; mainly support, documentation and CSS.

Colin,

Either version of Kickstart should be backwards compatible for your version. The 5.x series will extract the new jps encrypted archives, the older Kickstart will not.

It's always good to talk to someone else who does this.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.