Support

Akeeba Backup for Joomla!

#42357 Dashboard error after restore

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
5.4
PHP version
8.4.12
Akeeba Backup version
10.1.0

Latest post by johannes68 on Monday, 20 October 2025 05:47 CDT

johannes68

Hello Nicholas,

i just want to inform you about an error, which happened only on restoration via the Joomla backend.  The error was only at the dashboard: "Cannot instantiate abstract class Joomla\Module\Popular\Administrator\Helper\PopularHelper",  and under System-Database is showed corrupt entries, which were repaired by button-click, but without success.

The 3 DB errors were:
The row „'is_current'“ is not in table „'zkg_history'“ included.
The row „'is_legacy'“ is not in table „'zkg_history'“ included.
Wrong manifest version (sorry i dont have concrete mentioned versions noted)

On separate manual restoration with the Kickstart script, all went fine, no errors in dashboard or database.

Server environment: AlmaLinux 8.10;  Litespeed Webserver Pro

This is just for your information.  I dont need support, as the site is running again with the manual restored backup.

Kind regards,
Johannes

nicholas
Akeeba Staff
Manager

As per our documentation:

Do not try to overwrite one Joomla! version family with a different one. Overwriting a major version with another (e.g. restoring a backup taken on Joomla! 3.7 on top of a site running Joomla! 2.5 or vice versa) or between different minor versions (e.g. restoring a backup taken on Joomla! 3.7 on top of a site running Joomla! 3.6 or vice versa) will NOT work. Joomla! moves files around between minor and major versions. Since the backup does not delete files not present in the backup archive this will end up with Joomla! being "confused" and malfunctioning. In these cases you should delete the existing files and folders (except, perhaps, user generated content) before restoring the backup. You can safely restore a sub-minor (path-level) version on top of another. For example, you can safely restore a Joomla! 3.7.5 site on top of a Joomla! 3.7.3 site or vice versa.

Delete the site's folders. Upload Kickstart and your backup archive. Run Kickstart and proceed with the restoration. In the database restoration page use the same database prefix when restoring the site and set With Existing to Drop Same Prefix to clean up your database tables so that you do not end up with a situation that makes it impossible to later upgrade your site.

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!

johannes68

Ah, ok, that makes sense.  Yes indeed, i tried to restore from J6 back to J5, and manual restore (with deleting all files/folders/db entries before) worked fine. 
Thank you very much, Nicholas!

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!