Granular Translation Method settings for the Link field type #16502
-
|
The Link field is a powerful field, we enjoy using. However, the current Translation Method setting applies globally to all subfields, which can be limiting in some use cases. We have encountered a scenario where we want the entry relation or URL to remain non-translatable, while allowing the label to be translatable per site. This granular control over the translation settings for each subfield would significantly enhance the flexibility of the Link field and accommodate a broader range of use cases. For instance, a typical scenario might involve:
We are maintaining a multi-language site with seven languages. If there is a change in the related entry, the content team will need to update the relation on all sites then. We are afraid, that this will eventually lead to errors. We propose introducing separate Translation Method settings for:
Thank you for considering this feature request! Please let me know if you’d like further clarification or details. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
Also would like to add a +1 to this. Having to maintain linked entries separately in multiple languages is a pretty big burden on content entry all just so that the label field (in our case) can be translated. I would also like to add that our normal use case is that 95% of the time, we want linked entries to be maintained across different languages. For linked assets, its probably more like 60%, because often times there will be a language-specific PDF download or something. For external links, it's probably around 70% - often the link is the same but sometimes the external site has a language-specific version of the content. I almost think the ideal translation setting for the Link field would be to have the label be translateable, have the link itself default to being consistent across languages but have the option to opt-out and set a language-specific link in specific instances where it makes sense. |
Beta Was this translation helpful? Give feedback.
-
|
I am assuming that with the latest Craft release we are supposed to create a custom Content Block and build our own Link field. So I guess this feature idea may be of the table … |
Beta Was this translation helpful? Give feedback.
Not off the table, but the idea isn’t really achievable at the moment in the first place. We don’t have a mechanism for partially translatable fields right now.