Support

Description of my issue:
Upgraded to 3.10.0 apparently successfully (the one-click feature does not work for me, so I upload the zipped file via cPanel and extract using File Manager; then run upgrade script. This process worked OK for a previous upgrade to 3.9.2)

Daily CRON backup subsequently failed with message:
'Could not open input file: /home/laverdaf/public_html/cli/akeeba-backup.php'

Checking the /cli folder I found these files:
deletefiles.php
garbagecron.php
index.html
update_cron.php

Before going further I decided to contact you.

A backup triggered manually from the backend worked successfully after the failed command line job. I wonder if my workround for installing the upgrade has caused this issue?

Thanks in anticipation

Bob

Hi, Bob.

Your Live Update problem is most likely due to your Download ID. With our site upgrade on December 25, all of the Download IDs changed. You need to enter the new Download ID from our website in your Backup program. You can read more about this issue in the article here: https://www.akeebabackup.com/home/news/1537-new-site-and-changes-in-dlid.html.

I think the CRON failure is related. I think you have a Core version of Backup installed instead of the Pro version. If this is the case, you can just download the Pro version and install it over the Core version. Please install the Pro version twice, back to back. Do not uninstall the Core version, that will cause you to lose all of your settings and possibly your stored backup archive files.

Dale - thanks for the quick reply.

I am using the Pro version, and the file I uploaded was com_akeeba-3.10.0-pro.zip

Anyway, I did as you suggested and reinstalled using the Direct Link feature with the standard Joomla! installer. All good...two extra files appeared in /cli (akeeba-backup.php and akeeba-altbackup.php, along with those previously listed). I tested the CRON job and it works fine.

I had read about the AkeebaBackup site change and the need for a new download ID when researching this problem. So I performed the required update but still no success with the one-click update. I guess there is no way to investigate further until the next update becomes available...

Thanks again

Robert

I can't explain it. :-( It makes sense if you were upgrading from Core to Pro, the problem is a "gotcha" in the Joomla! installer where it doesn't like to copy new files while in update mode. The double install usually gets around it. I can't think of any reason why the file would not be there in a straight upgrade Pro to Pro.

The other thing that has gotten a number of our users is that you have to refresh the Live Update screen after you enter the new Download ID. If you don't, the old url for the old ID is still there and it fails. If that was the case, it won't be a problem with the next update.