Skip to Content
This question has been flagged
migrationassetsv14stylingodoo16features
2 Replies
4653 डेटा देखने का तरीका
अवतार
Kahina

Hello,


I've encountered an error while trying to launch my database migrated from Odoo 14 to Odoo 16. The error message states:

The style compilation failed, see the error below. Your recent actions may be the cause, please try reverting the changes you made.

Error: Undefined variable: "$o-dms-inspector-bg".
        on line 34037:35 of stdin, in mixin `@content`
        from line 78:7 of odoo/addons/web/static/lib/bootstrap/scss/mixins/_breakpoints.scss, in mixin `media-breakpoint-down`
        from line 34010:10 of stdin

>>                 overflow: auto;

   ----------------------------------^
This error occurred while compiling the bundle 'web.assets_backend' containing:
    - /web/static/lib/bootstrap/scss/_functions.scss
    - /web/static/lib/bootstrap/scss/_mixins.scss
    - /web/static/src/scss/mixins_forwardport.scss
    - /web/static/src/scss/bs_mixins_overrides.scss
    - /web/static/src/legacy/scss/utils.scss
    - /web_enterprise/static/src/scss/primary_variables.scss
    - /web/static/src/scss/primary_variables.scss
    - /web_enterprise/static/src/core/notifications/notifications.variables.scss
    - /web_enterprise/static/src/webclient/home_menu/home_menu.variables.scss
    - /web_enterprise/static/src/webclient/navbar/navbar.variables.scss
    - /web/static/src/core/notifications/notification.variables.scss
    - /web/static/src/search/control_panel/control_panel.variables.scss
    - /web/static/src/search/search_panel/search_panel.variables.scss
    - /web/static/src/views/form/form.variables.scss
    - /web/static/src/views/kanban/kanban.variables.scss

....  [List continues...]

Additionally, the interface styling appears distorted.


Any guidance on resolving this issue would be appreciated.


Thank you.

अवतार
खारिज करें
अवतार
Dương Nguyễn
Best Answer

Probably because if your custom module contain datas and they might need to migrate into latest version (eg: in version 14 the data structure change a little bit and you need to modify those data in version 14 to adapt 16 one) then database will be corrupted.
But i looked back your error message and notice this think : $o-dms-inspector-bg is a variable of scss file, so probably you might troubleshot this and perhaps temporarily disable the scss file if needed

अवतार
खारिज करें
अवतार
Kahina
लेखक Best Answer

I did try both solutions, still having the same error unfortunately 

अवतार
खारिज करें
Dương Nguyễn

May i ask, how do you migrate from odoo 14 to odoo 16. You use openupgrade script or odoo upgrade service ?

Kahina
लेखक

I used Odoo upgrade service

Dương Nguyễn

Oh that's good, if you don't have any customer module, 3rd party apps then you can always asks Odoo about this, just contact with them for this error.
In case you have customer module or 3rd party apps, the error probably cause by those apps because they might not been upgrade into latest version yet.
if this answer help you, please up vote me or convert into best answer sir.

Kahina
लेखक

Thank you for your suggestion. Yes, indeed, there are several custom addons in our Odoo instance that could potentially be causing the error. However, identifying which one is responsible for the error can be a bit challenging. Could you kindly guide me on the steps I could use to pinpoint the addon causing the issue? Any advice would be greatly appreciated.

Dương Nguyễn

Ok, in case you can't contact with the provider who you have bought those apps, you can send me the list of 3rd apps via email daiduongnguyen2709@gmail.com, then i'll will check.
Here is the link to guild you what to do when you want to upgrade database that have custom addons
https://www.odoo.com/documentation/17.0/developer/howtos/upgrade_custom_db.html#

Kahina
लेखक

Thank you for your guidance and for offering to help. I followed all the steps mentioned in the provided link, including upgrading custom modules in an empty database to ensure compatibility with version 16. However, I skipped step 4 and directly launched the upgraded test database in my Odoo instance. Do you think that this could be the cause of the error?

Dương Nguyễn

Probably because if your custom module contain datas and they might need to migrate into latest version (eg: in version 14 the data structure change a little bit and you need to modify those data in version 14 to adapt 16 one) then database will be corrupted.
But i looked back your error message and notice this think : $o-dms-inspector-bg is a variable of scss file, so probably you might troubleshot this and perhaps temporarily disable the scss file if needed

Kahina
लेखक

Thanks for your suggestion! I found the file with the "$o-dms-inspector-bg" variable, deleted the associated asset from the database, regenerated the asset bundle, updated the module and now everything's working fine. Appreciate your help!

Dương Nguyễn

Good to hear , can you up vote my answer or mark the best answer

Related Posts Replies डेटा देखने का तरीका ऐक्टिविटी
Migration script for stock.production.lot to stock.lot
migration v14 v15 odoo16features
अवतार
अवतार
1
दिस॰ 24
7142
Migration script subscription fields to 16
migration subscription v14 odoo16features
अवतार
0
अप्रैल 23
3961
Missing assets when upgrading odoo 16 Solved
migration cache upgrade assets odoo16features
अवतार
1
फ़र॰ 24
7798
migrate custom module v14 to v16
migration update migrate v14 odoo16features
अवतार
अवतार
1
जुल॰ 23
4365
Field used in context is restricted to certain groups Solved
migration odoo16features
अवतार
अवतार
अवतार
3
जून 24
5468