Interface filter in translation field #21546
Valdri
started this conversation in
Feature Requests
Replies: 1 comment
-
Hey.
(My actual use case has a few more layers: users are part of teams, teams manage projects, languages are associated to projects...) With the m2m field it seems we are able to filter (and with m2o as well). As I understand, the translation field is based on a m2m relation so it seems reasonable to think filtering should not be an issue. I am willing to explore creating an extension for this. I'd really appreciate some pointers from the team before diving in. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Interface filter in the translation field with the ability to filter the languages available for translation
Basic Example
No response
Motivation
I have a product with 2 translation fields containing the product description, one for amazon the other for woocommerce
translations_amazon
translations_shop
They use the languages data model as a list of languages
in languages I have 3 entries
de (German), cz (Czech), fr (French)
Now amazon has no Czech version and in the list of languages available for translation I would like to leave only de and fr
Detailed Design
Interface filter in the translation field with the ability to filter the languages available for translation
Requirements List
Interface filter in the translation field with the ability to filter the languages available for translation
Drawbacks
I can't think of any drawback, it will be a new option in the interface
Alternatives
duplication of the language data model for each translation field
languages_amazon -> translations_amazon
languages_shop -> translations_shop
Adoption Strategy
This is not a breaking change
Unresolved Questions
No response
Beta Was this translation helpful? Give feedback.
All reactions