[5.x]: Allow translation method to be set on the field instance #14607
Replies: 2 comments
-
|
On the surface this seems fine, but it’s a little problematic since each field type gets to choose which translation methods it actually supports (including none, like for Matrix and relational fields). So it would be a little confusing if you set the translation method override in a field layout, then change the field’s type to one that doesn’t support the same translation method. At least that’s clear from the field’s edit screen, but you wouldn’t have any visibility into how all the field layouts are being affected. (Not a deal breaker – there’s a similar bit of awkwardness when switching from a multi-instance-supporting field type to a single-instance one. Just worth considering it.) |
Beta Was this translation helpful? Give feedback.
-
|
I just stumbled upon this limitation. For example I have very universal Table field called For now I will just create separate field like Unrelated: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Craft 5's field instances are an incredible leap forward in content modeling, this will allow us to greatly reduce the number of custom fields we have to configure!
Right now a field instance can override the field's Label, handle and instructions (as well as conditions). These all make sense because the context of the field's instance, i.e. the entry type it lives in, matters.
We are wondering if the same override could be extended to a field's translation method? The translation needs of a field are, at least in our instances, also always tied to the entry type it lives in.
🤞
Beta Was this translation helpful? Give feedback.
All reactions