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.
Problem/Motivation
Several places within ECA make sense to run through translation. Using dynamic variables passing to the translation method however is not recommended. We need to determine how we can support translation of text.
Steps to reproduce
Proposed resolution
One way could be to provide an action that runs explicit translation on a dynamic string. This way a user may have the control when and how a string shall be translated.
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork eca-3280069
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
mxhThis is a follow-up from #3276448: eca_form: Feature clarification
Comment #3
mxhComment #4
jurgenhaasWill not be part of 1.0RC and may be pushed into 1.1
Comment #5
mxhComment #6
mxhComment #8
mxhComment #10
jurgenhaasNicely done!
Comment #11
mxhI think it makes sense to move this action to the new
eca_render
module, once it's available.Comment #12
jurgenhaasReally? I would have thought, translating a string is well-placed as a base plugin because it could be useful for displaying messages, setting form buttons and certainly a lot more.