Akeeba Backup for Joomla!

#36740 Joomla Picking Up To Update Core.. When In Fact I'm usung Pro

Posted in ‘Akeeba Backup for Joomla!’
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
PHP version
Akeeba Backup version


I run the Akeeba Pro On all my site (68).. but this site that I am Running Pro.. is calling for "Akeeba Core" to be updated.  this has been for many updates.. and the only way I can make it update it to install the latest pro version Manually again.


Site is asking for this update..

Akeeba Backup Core package Site Package 8.1.1 8.1.2 N/A Update

Akeeba Staff

Thank you for the more specific information, I can not understand the situation better!

This is a Joomla bug. The following procedure only applies to Joomla 3 and Akeeba Backup 8 — that's why I needed the version numbers!

  1. Go to Extensions, Manage, Update Sites.
  2. Search for Akeeba Backup.
  3. Select all items on the list and click on Delete.
  4. Go to Components, Akeeba Backup.
  5. Click on Options, Live Update and remove the Download ID.
  6. Click on Save & Close.
  7. Click on Options, Live Update again, this time entering your Download ID.
  8. Click on Save & Close again. Please note that the last four steps are NOT redundant and must be carried out at exactly this order, without doing anything else in between.
  9. Then go to Extensions, Manage, Update and click on Clear Cache.
  10. Go to System, Clear Cache. Select Administrator from the drop-down and click on Clear All.
  11. Go back to to Extensions, Manage, Update and click on Clear Cache again.
  12. Now click on Find Updates.

Now let's see why that works.

You had Akeeba Backup Core installed on that site and then installed Akeeba Backup Professional. There are two discrete issues in Joomla:

  • Joomla is supposed to remove the Core update site and install the Pro update site when you upgrade from Core to Pro. Because of a bug — the existence of which is confirmed as of late January 2022, eight years after I first reported it, but the actual trigger is not yet discovered — Joomla sometimes thinks the update is not an update(!) and doesn't modify the update site, doesn't copy all files, does not update its cache of the package extension's XML manifest, does not delete the XML manifest of Akeeba Backup Core or does a combination of the above.
  • If you use the Rebuild button in the Update Sites page Joomla uses its cached information for the package extension's XML manifest. Because of the bug above it may pick up the manifest of Akeeba Backup Core (which is no longer installed on your site but Joomla doesn't actually know that's the case because its cache is borked!) and install the update site for Akeeba Backup Core.

Steps 1 to 3 remove the wrong update site.

Step 4 reinstalls the correct update site but because of another Joomla issue that has to do with how it caches component options (even when Joomla's cache is disabled!) you may end up with an update site to the Professional version which does not have the Download ID applied to it.

Steps 5 to 8 are NOT redundant. They address the problem described above. Steps 5 to 6 bust the Joomla component options cache but also mean that you do not have the Download ID at all. Steps 7 and 8 re-establish the download ID, bust the component options cache once again and apply the download ID to the update site for the Professional version.

Normally, you'd think you're done. However, the caching issue extends to how Joomla lists and finds updates (thankfully, this WAS fixed in Joomla 4 after the fifth time I explained to a core maintainer how it happens, it was an one line fix, something which should have been done eight years ago; better late than never). So, steps 9 to 11 try to get Joomla to bust that cache. 

Only at this point you can search for updates again, using the correct update site and correct download ID, hence step 11.

Joomla 4 addresses most of those issues. It may still find the wrong update site but you can delete just the one wrong update site and enter the correct Download ID directly into the Update Site itself, without having to go through the component. The component options caching is irrelevant. Moreover, the Updates page is reworked so that the button to Clear Cache actually does clear cache instead of going halfway there. So if you were on Joomla 4 you'd have different steps, with a slight variation depending on whether you were using Akeeba Backup 8 or 9. And now you know why I was insisting on the exact version numbers. Trying to work around what's broken in Joomla requires knowing which Joomla version we're dealing with and whether the Download ID is applied by the component (Akeeba Backup 8) or directly in the update site (Akeeba Backup 9).

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!

System Task
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.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.