Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
follow-up from #1422996: localization and i18n integration:
We should enhance the data-selection widget to have its own language setting included optionally. For that we need to improve the import/export structures and array structures in a BC way.
Work-a-round:
In the meanwhile the "Select a translated value" action provided by the "Rules translation" module can be used to get the translated value as a separate variable which then can be selected in the target action.
Comments
Comment #1
guy_schneerson CreditAttribution: guy_schneerson commentedRules translation works for me, i used it on Stock V2 to translate the "out of stock" message Translating "Out of stock" and other messages set in Rules
However is there a reason why the module should not be pathing the text set by the action through t() providing localization out of the box?
Comment #2
geek-merlinCrosslinking a related bug: #2209607: "Provided" text variables are always sanitized
Comment #3
hosais CreditAttribution: hosais commentedI would like to use rules to send translated Email message. I supposed I can use "Select a translated value" action to have the langauge content saved in message type. I make the following rule but it does not work. Anyone can tell me what is the problem? Thanks.