Problem with EPSO update from UI - Class "Espo\Core\Utils\Layout" not found

[MONBERG]

Hello there
I am trying to update Espo CRM from 8.4.2 to 9.0, and as we don´t have access to console of the server, we need to do this by UI.

As i upload a ZIP file, it´s ready to update, then when i start - ERROR 500 - Class "Espo\Core\Utils\Layout" not found and the ESPO is not updated.
Can someone please help us with this situation?
Thanks

[Kharg]

Can you provide the list of installed extensions?

[MONBERG]

Would you please help me , where can i find this list - or some history of the extensions? In case you dont mean this

[Kharg]

That’s exactly what I meant, thank you.

Unfortunately I do not have enough knowledge of AutoCRM extensions to help you.

You should reach out to someone from Apertia as probably one of their extension needs to be updated to be compatible with Espo 9.0.

Maybe check the logs to see if it tells you which extensions is causing this?

if you can update from CLI it will exactly tell you which extension is causing the issue.

[MONBERG]

I reached console of server, and tried to update, but it told me only the same information - Error: Class "Espo\Core\Utils\Layout not found" . I checked directory of that file, and this file/folder really doesnt exist,

I tried to contact Apertia, but they are not responding sadly so we are alone in this, do u please have any other idea how i could findout which extension is problematic in this?
Also, we have a message New Advanced Pack version 3.6.3 is available. It can be downloaded on the customer portal, could it be that we dont have latest update on Advanced Pack?
As i dont know where to download update on this pack...

Thanks a lot for helping us

[Kharg]

Can you post the full message provided by the console while updating?

I think that it also tells you which file is using that class

[MONBERG]

This is the message from console.

[Kharg]

Maybe there are more details in the log?

[MONBERG]

[2025-01-29 11:17:45] DEBUG: API (500) Class "Espo\Core\Utils\Layout" not found; POST /Admin/action/runUpgrade; Input data: {"id":"679a0e0e3037a9f1e"}; Route pattern: /{controller}/action/{action}; Route params: Array ( [controller] => Admin [action] => runUpgrade )
[2025-01-29 11:17:45] ERROR: (500) Class "Espo\Core\Utils\Layout" not found :: POST /Admin/action/runUpgrade :: /data/2/d/2d23500b-a7ce-4fdc-a463-6e00651b25b8/monberg.eu/sub/crm/application/Espo/Core/Upgrades/Actions/Base.php(176)

[Kharg]

MONBERG

maybe you can use grep to search for where this class is being used:

grep -rl Espo\\Core\\Utils\\Layout *.php 

[MONBERG]

Our CRM is under



And when i am moving through console, i go by

[lazovic]

Try to run this command in the "crm" directory.

[lazovic]

Hi MONBERG,

This error indicates that some extension file contains this line with a class that no longer exists (many classes have changed in the EspoCRM v9.0). You can search for this line via VSCode, for example, or any other file manager. You have many third-party extensions; it is very difficult to say which one is causing the issue. One thing I can say for sure is that the Advanced Pack extension does not cause such problems.

[MONBERG]

Alright thanks, i could use that VSCode, but i guess there is gonna be a lot of folders to check (i mean lot of files), so its like i will have to open in VS every file of those extension and look for that connection with Layout file/folder?

[Kharg]

In VS code you can search for a string in all files, so it would be pretty fast

[MONBERG]

Command was sucessfull but nothing happened?

[Kharg]

The extension may be installed in the custom directory, please run grep from the root of the crm folder

[MONBERG]

I did what you guys recommended, and i found out, that (probably) AutoCRM extension is what creates the problem to update (you can see on the photos)





So,now when the file Espo\Core\Utils\Layout doesnt even exist, its possible to experiment and remove those lines of codes, to delete the problem with update?
Or is it gonna be much more complicated ?

[lazovic]

Classes are predefined for a reason: they are used inside the code in each file, so if you simply delete the lines mentioning them, it will only make the situation worse.

The best solution in this case is to uninstall the problematic extension from your EspoCRM instance, and then you will only have to wait for the developers of this extension to adapt it to the EspoCRM v9.0.

[MONBERG]

Yeah i thought of this, as i don´t know what this extension contains and i dont want to break our system apart, i will probably have to hope that company that sold us this system will respond. I really thanks to all of you for helping me identify this problem and that i learned something new. Thanks!