Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[13.0] [Website] Can't translate Customize Section item in Odoo Website Side #41974

Open
odoo-backend-dev opened this issue Dec 17, 2019 · 13 comments
Labels
13.0 Confirmed the bug was confirmed by testers Internationalization about translations Website

Comments

@odoo-backend-dev
Copy link

Can't translate Customize Section item in Odoo Website Side

Video/Screenshot link (optional):
Screenshot from 2019-12-17 11-25-29

@odoo-backend-dev odoo-backend-dev changed the title [13.0] [Website] [13.0] [Website] Can't translate Customize Section item in Odoo Website Side Dec 17, 2019
@Yenthe666
Copy link
Collaborator

Yeah that seems to be a real bug, I confirm this behaviour:

image

@Yenthe666 Yenthe666 added the Confirmed the bug was confirmed by testers label Dec 17, 2019
@Yenthe666
Copy link
Collaborator

@JKE-be for your team ;)

@JKE-be
Copy link
Contributor

JKE-be commented Dec 17, 2019

@mart-e ? any suggestion ?

Do we really want to make name of ir.ui.view translatable to make it workable ?

@mart-e
Copy link
Contributor

mart-e commented Dec 17, 2019

@JKE-be this is the name of the ir.ui.view ? This is a shame because I was hoping to be able to remove that field that is useless most of the time (but here we have a case where it is useful).
We do not want to make it translatable as it is technical most of the time...

Screenshot_2019-12-17 Views - Odoo

In master, we could move this information to another translatable field (e.g. turn the customize_show into a translatable char field) but for stable, I am not sure it is possible.

@JKE-be
Copy link
Contributor

JKE-be commented Dec 17, 2019

imo nothing to do in stable.

It is the case since v8.

Remove it ? how do you search a view in this case ?

@JKE-be
Copy link
Contributor

JKE-be commented Dec 17, 2019

Remark: This name is used too in the name of the page in your browser !

@Yenthe666
Copy link
Collaborator

Yeah we should absolutely do it for master :)

@JKE-be
Copy link
Contributor

JKE-be commented Dec 17, 2019

@Yenthe666
Did you follow the thread ? Are you ready to loose your default page name ?

It was just a poc, not a PR to merge ;)

@Yenthe666
Copy link
Collaborator

We can go with a new translatable field without issues right? :)

@MohammadSalek
Copy link

Hey @Yenthe666, any solutions for this issue yet?

@JKE-be
Copy link
Contributor

JKE-be commented Jul 12, 2021

No sorry, it is a limitation in the current version. We have no solution to improve it in stable version.

@MohammadSalek
Copy link

@JKE-be how about version 14? or the upcoming versions?

@JKE-be
Copy link
Contributor

JKE-be commented Jul 12, 2021

need to discuss with @mart-e who who would like to remove it vs website that would like to make it translatable ;)
I will try to see him asap to discuss about it... but in 99% not for v14 seems it is an improvement and I'm pretty sure that some dev (wrongly) make comparison on view name since it was not translated until now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
13.0 Confirmed the bug was confirmed by testers Internationalization about translations Website
Projects
None yet
Development

No branches or pull requests

5 participants