Support

Akeeba Backup for Joomla!

#39685 Admin Tools - An unhandled Exception has been detected - Layout default not found

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
4.4.0
PHP version
8.1.17 >> 8.1.23
Akeeba Backup version
9.8.1

Latest post by maggus86 on Tuesday, 24 October 2023 04:12 CDT

maggus86

Dear Nicholas!

I refer to this ticket as I experience the same issue. Steps to reproduce:

  1. Develop website with latest Joomla! 4.4.0 on XAMPP 3.3.0, using latest Akeeba Backup Pro 9.8.1 and Admin Tools Pro 7.4.3
  2. Create local backup with only 1 exclusion (templates/yootheme/cache)
  3. Extract on public server with latest Kickstart Core 8.0.3
  4. Install with ANGIE
  5. Backend reports above mentioned error in Admin Tools

I have checked it twice. I have reinstalled both Admin Tools and Akeeba Backup on the local server and repeated the procedure. The error is raising again.

Deleting the administrator/cache/autoload_psr4.php doesn't help. What helps is reinstalling Admin Tools on the destination server.

I want to ask you if I have to worry that there are more files missing in the backup or if it could be an issue with Admin Tools or Akeeba Backup?

It seems that this is the only error I have found after restoring the backup. For safety reasons I will reinstall the Joomla! Core Files...

Best regards,

Markus

System Task
system
The ticket information has been edited by Markus Mauthe (maggus86).

maggus86

It seems that the destination server has a memory_limit of 72MB. Re-installing the Joomla! Core files fails and results in a 500 error... Could that be the problem?

My own server uses minimum 128MB, better 256MB, but unfortunately this isn't my own server but a shared hosting provider claiming that he has specialized to Joomla!...

nicholas
Akeeba Staff
Manager

Very important question: did you try restoring the backup on top of an existing Joomla! 3 (or earlier) site? If you did, that's the problem. Joomla fails in weird ways when you mix files from different version families. Delete the existing files, then restore the backup.

If that's not the case, let's follow standard troubleshooting operating procedure. Edit  the configuration.php file and set $debug = true and $error_reporting = 'maximum'. Reproduce the error and you'll get a debug trace. I need that debug trace to see where this error comes from.

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!

maggus86

Thank you for your quick reply!

I have restored the backup to a clean folder without any remaining files. Before creating the backup I have migrated that site from latest J!3 to latest J!4 Core. I have conducted about 30 migrations in total in the last months, but this is the first time, this issue occurs.

As the site works now and as I don't want to stress that customer's webspace with more tests, you can close this case - if possible with the option that I reopen that case next time when the same issues arises. Then I will definitely follow your instructions and provide you all the information needed.

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!