[comp-4499] Elementor 4.2: make atomic form (e-form) Email 1 & Email 2 notification translatable#540
Merged
Merged
Conversation
…translatable The atomic form element (e-form) stores its email-action settings as Emails_Prop_Type object props (email, and email_2 enabled by Elementor Pro), each holding subject + message string sub-props. Only 'form-name' was registered, so the email subject/message were not offered for translation -- a regression versus the classic 'form' widget, which already exposes email_subject/email_content/email_subject_2/email_content_2. Register the nested paths so both notifications become translatable: email>value>subject>value, email>value>message>value, email_2>value>subject>value, email_2>value>message>value Verified on Elementor 4.2.0-beta2 + Pro: WPML string extraction for an e-form node goes from 0 to 4 strings with this change.
dgwatkins
approved these changes
Jul 16, 2026
Member
Author
|
Merged and deployed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The atomic form element (e-form) stores its email-action settings as Emails_Prop_Type object props (email, and email_2 enabled by Elementor Pro), each holding subject + message string sub-props. Only 'form-name' was registered, so the email subject/message were not offered for translation -- a regression versus the classic 'form' widget, which already exposes email_subject/email_content/email_subject_2/email_content_2.
Register the nested paths so both notifications become translatable:
email>value>subject>value, email>value>message>value,
email_2>value>subject>value, email_2>value>message>value
Verified on Elementor 4.2.0-beta2 + Pro: WPML string extraction for an e-form node goes from 0 to 4 strings with this change.
https://onthegosystems.myjetbrains.com/youtrack/issue/comp-4499