search

Tecnativa / doodba

Base image for making the creation of customized Odoo environments a piece of cake
Apache License 2.0
423 stars 303 forks source link

Translation problem in dooba odoo generated image #469

Closed ceballos59 closed 2 years ago

ceballos59 commented 2 years ago

Describe the bug

After generation, some elements are translated and some are not. Image is attached. Those not translated are not two or three but many. Attached example image

With the same odoo in a normal installation outside of doodba all the labels are translated

To Reproduce

one sample: Odoo / Purchase / Request for quotation

Affected versions: odoo 12 CE spanish translation

Expected behavior All elements need to be translated

Additional context Docker version 4.3.0 Window 10 pro WSL 2 Debian

Sample capture

2022-01-12 14_22_40-PO00002 - Odoo
HviorForgeFlow commented 2 years ago

I guess you are running it on devel, remember by default you are using some --dev flags, I'm not 100% sure but I think the xml one as it makes to load views from files it is producing this error. image Try to remove --dev command to see if error persist Thanks!

joao-p-marques commented 2 years ago

Thanks for the reply @HviorForgeFlow. Indeed, that seems to be your issue @ceballos59 so I am closing this. Hope it helps!

ceballos59 commented 2 years ago

Indeed, that seems to be your issue

I removed the --dev line in devel.yalm as as suggested @HviorForgeFlow and re-generate a database devel, but the problem persisted: many tags are left without translation...

2022-01-12 16_08_43-__wsl$_Debian_home_admin_doodba-projects_vertical-slaughter_devel yaml
joao-p-marques commented 2 years ago

Ok, first of all, you would need to recreate the containers for this change to take effect (docker-compose up -d) should do it. Are you sure it got recreated?

Also, are you sure you are loading the translation correctly? Make sure you override the current terms when loading it…

pedrobaeza commented 2 years ago

Maybe a down is needed before, or simply the terms are not translated yet, but this is not a Doodba problem.

ceballos59 commented 2 years ago

😊😊😊 I´m sorry.You are totally right, thank you very much, after docker-compose up all the translated tags appeared. Thanks a lot.

El jue., 13 ene. 2022 8:34, João Marques @.***> escribió:

Ok, first of all, you would need to recreate the containers for this change to take effect (docker-compose up -d) should do it. Are you sure it got recreated?

Also, are you sure you are loading the translation correctly? Make sure you override the current terms when loading it…

— Reply to this email directly, view it on GitHub https://github.com/Tecnativa/doodba/issues/469#issuecomment-1011911929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFP5QRWPNQL6LPHHARGTFLUV2FC3ANCNFSM5LZFDDNQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

macagua commented 2 years ago

I have the same issue for Odoo 13 Community Edition, and fixed this changed

from this config - --dev=reload,qweb,werkzeug,xml

to this config - --dev=reload,qweb,werkzeug

as the following example:

command_yml

pedrobaeza commented 2 years ago

@macagua that option is explicitly put in dev environment to reload XML files each time you refresh. That's a development option to ease it for not having to update your module. But you have to sacrifice in such case the translations.