cancel
Showing results for 
Search instead for 
Did you mean: 

Error after migrate a magento 1.9 to a magento 2.4 while loading the frontend content

Error after migrate a magento 1.9 to a magento 2.4 while loading the frontend content

Hello,

I migrated a 1.9.3.1 magento to a 2.4.4 magento, i've faced some issue furing the process but all goes finally ok.

But now i face an error when i run the frontend on a browser.

Here is the complete error in developer mode : 

1 exception(s):
Exception #0 (LogicException): Unable to load theme by specified key: 'ultimo/default'

Exception #0 (LogicException): Unable to load theme by specified key: 'ultimo/default'
<pre>#1 Magento\Theme\Model\View\Design->setDesignTheme() called at [generated/code/Magento/Theme/Model/View/Design/Proxy.php:111]
#2 Magento\Theme\Model\View\Design\Proxy->setDesignTheme() called at [vendor/magento/module-theme/Model/Design.php:145]
#3 Magento\Theme\Model\Design->changeDesign() called at [vendor/magento/framework/App/Area.php:162]
#4 Magento\Framework\App\Area->detectDesign() called at [vendor/magento/framework/View/DesignLoader.php:56]
#5 Magento\Framework\View\DesignLoader->load() called at [vendor/magento/module-theme/Plugin/LoadDesignPlugin.php:53]
#6 Magento\Theme\Plugin\LoadDesignPlugin->beforeExecute() called at [vendor/magento/framework/Interception/Interceptor.php:121]
#7 Magento\Cms\Controller\Index\Index\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#8 Magento\Cms\Controller\Index\Index\Interceptor->___callPlugins() called at [generated/code/Magento/Cms/Controller/Index/Index/Interceptor.php:23]
#9 Magento\Cms\Controller\Index\Index\Interceptor->execute() called at [vendor/magento/framework/App/Action/Action.php:111]
#10 Magento\Framework\App\Action\Action->dispatch() called at [vendor/magento/framework/Interception/Interceptor.php:58]
#11 Magento\Cms\Controller\Index\Index\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]
#12 Magento\Cms\Controller\Index\Index\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#13 Magento\Cms\Controller\Index\Index\Interceptor->___callPlugins() called at [generated/code/Magento/Cms/Controller/Index/Index/Interceptor.php:32]
#14 Magento\Cms\Controller\Index\Index\Interceptor->dispatch() called at [vendor/magento/framework/App/FrontController.php:245]
#15 Magento\Framework\App\FrontController->getActionResponse() called at [vendor/magento/framework/App/FrontController.php:212]
#16 Magento\Framework\App\FrontController->processRequest() called at [vendor/magento/framework/App/FrontController.php:147]
#17 Magento\Framework\App\FrontController->dispatch() called at [vendor/magento/framework/Interception/Interceptor.php:58]
#18 Magento\Framework\App\FrontController\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]
#19 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php:99]
#20 Magento\Store\App\FrontController\Plugin\RequestPreprocessor->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135]
#21 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php:75]
#22 Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135]
#23 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#24 Magento\Framework\App\FrontController\Interceptor->___callPlugins() called at [generated/code/Magento/Framework/App/FrontController/Interceptor.php:23]
#25 Magento\Framework\App\FrontController\Interceptor->dispatch() called at [vendor/magento/framework/App/Http.php:116]
#26 Magento\Framework\App\Http->launch() called at [generated/code/Magento/Framework/App/Http/Interceptor.php:23]
#27 Magento\Framework\App\Http\Interceptor->launch() called at [vendor/magento/framework/App/Bootstrap.php:264]
#28 Magento\Framework\App\Bootstrap->run() called at [pub/index.php:30]
</pre>

I got this issue too when i try to load a new theme in Content > Design > Configuration > Default Store View 

 

Something went wrong while saving this configuration: Unable to load theme by specified key: 'ultimo/default'

I've looked in the table 'core_config_data' 

I've found this entries but for me nothing wrong 

mysql> SELECT * FROM core_config_data WHERE path LIKE '%theme%';
+-----------+----------+----------+----------------------------------+--------+---------------------+
| config_id | scope    | scope_id | path                             | value  | updated_at          |
+-----------+----------+----------+----------------------------------+--------+---------------------+
|      1410 | default  |        0 | facebookchat/general/theme_color | FFFFFF | 0000-00-00 00:00:00 |
|      1421 | websites |        1 | design/theme/theme_id            | 3      | 2022-08-22 20:53:26 |
|      1422 | default  |        0 | design/theme/theme_id            | 3      | 2022-08-22 20:53:52 |
+-----------+----------+----------+----------------------------------+--------+---------------------+
3 rows in set (0.00 sec)

I've changed two entries in cms_page on the row custom_theme from 'ultimo/default' to 'NULL' with this query 

UPDATE cms_page SET custom_theme = NULL WHERE custom_theme = 'ultimo/default';

but it changed nothing 

Then i've checked many tables and i found this entry in the table "design_change"

mysql> select * from design_change;
+------------------+----------+----------------+-----------+---------+
| design_change_id | store_id | design         | date_from | date_to |
+------------------+----------+----------------+-----------+---------+
|                2 |        1 | ultimo/default | NULL      | NULL    |
+------------------+----------+----------------+-----------+---------+
1 row in set (0.00 sec)

If someone have an idea to resolve this issue, please tell me

If you need more details, please tell me

Best Regards

4 REPLIES 4

Re: Error after migrate a magento 1.9 to a magento 2.4 while loading the frontend content

Hello @benjamin_boursault 

 

Sometimes new theme added to theme table in our database with param type=1 (virtual theme). Try to set it to 0 (physical theme). For example:

 

mysql> insert into theme 
(parent_id,theme_path,theme_title,preview_image,is_featured,area,type,code)
VALUES ('1','ultimo/default','MyVendor Base', NULL, 0, 'frontend', 0, 'ultimo/default');

Kindly refer below solution link:
https://github.com/magento/magento2/issues/3409 

 

Problem solved? Click Accept as Solution!

Re: Error after migrate a magento 1.9 to a magento 2.4 while loading the frontend content

The problem is "ultimo/default" is the old theme who was installed on magento 1.9.3.1 

He's blocking me, i can't apply a new adapted theme to magento 2.

Sorry if i wasn't clear in my explications

Thanks 

Re: Error after migrate a magento 1.9 to a magento 2.4 while loading the frontend content

Hi @benjamin_boursault ,

 

You can get help from below links.

https://www.rakeshjesadiya.com/reindex-prices-programmatically-magento-2/

https://devhooks.in/blog/reindexing-specific-products-in-magento-2

 

Problem Solved? Accept as Solution!

 

Hope it helps!

Thanks

Ankit Jasani

Re: Error after migrate a magento 1.9 to a magento 2.4 while loading the frontend content

Hi @benjamin_boursault 

 

Please follow the below step to solve your problem.

1-  Please find theme_id then run the below query in MYSQL.

delete from core_config_data where path= 'design/theme/theme_id' and value='<your key>';

2. Flush Magento cache: php bin/magento c:c && php bin/magento c:f

 

Best Wishes

siddiqui