This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
This topic contains 1 reply, has 0 voices.
Last updated by Andreas W. 3 weeks, 1 day ago.
| Author | Posts |
|---|---|
| December 6, 2025 at 8:02 pm #17640865 | |
|
andreS-54 |
Ich habe folgenden Code für WPML eingefügt, um den Formbuilder von Divi Engine übersetzbar zu machen. Wie lautet der Code für für den Archive Loop von Divi Machine? <!-- alle Formfelder (Text, Textarea, Select, Checkbox etc.) --> de_fb_form_field <!-- Beschriftung & Placeholder --> <!-- gesamtes Formular: Submit‑Button, generische Placeholder etc. --> de_fb_form title |
| December 6, 2025 at 10:48 pm #17640928 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Hello, WPML by default supports all widgets that are shipped with Divi. Every Custom Divi Widget must have an XML configuration so that it can be translated using the WPML Translation Editor. It is the theme author's job to create such a configuration in a wpml-config.xml file in the root directory of the theme or plugin. We also provide the following plugin, which makes creating such a config easier, but we do not recommend using it in a production environment: If the author does not provide such a config, you can alternatively create one yourself. This config can be stored under WPML > Settings > Custom XML Configuration. In this case, the config likely would need to look like this:
<wpml-config>
<shortcodes>
<shortcode>
<tag>de_fb_form_field</tag>
<attributes>
<attribute>field_title</attribute>
<attribute>field_placeholder</attribute>
<attribute>description_text_text</attribute>
<attribute>select_placeholder_text</attribute>
<attribute>html_content_editor</attribute>
<attribute>select_options</attribute>
<attribute>checkbox_options</attribute>
<attribute>radio_options</attribute>
<attribute>required_message</attribute>
<attribute>forgot_password_text</attribute>
<attribute>email_message</attribute>
<attribute>step_prev_text</attribute>
<attribute>step_next_text</attribute>
</attributes>
</shortcode>
<shortcode>
<tag>de_fb_form</tag>
<attributes>
<attribute>title</attribute>
<attribute>submit_button_text</attribute>
<attribute type="link">redirect_url_after_submission</attribute>
<attribute>ajax_submit_button_text</attribute>
<attribute>success_message</attribute>
<attribute>error_message</attribute>
<attribute>processing_text</attribute>
</attributes>
</shortcode>
</shortcodes>
</wpml-config>
After saving the config, you will need to edit the affected widgets on the original content, then save the page and open the translation editor, which should now display the strings of those widgets. We can further offer a WPML test site on which we can recreate the issue, and we can assist you with a basic configuration for a couple of widgets, but if there are many affected widgets, it would be better to reach the author of those widgets. --- Alternative: Use the WordPress Editor as the translation method instead. Instructions for translating with the WordPress editor: Best regards |
The topic ‘[Closed] Translating the Divi Machine von Divi Engine’ is closed to new replies.