Elementor Custom Widgets

Problem:
Wenn Sie versuchen, Änderungen an der primären Sprache Ihrer Website vorzunehmen, die automatisch auf die übersetzten Sprachen übertragen werden sollen, und feststellen, dass diese Änderungen nicht übernommen werden, obwohl die automatische Übersetzungsfunktion aktiviert ist, könnte dies an der Kompatibilität Ihres Themes liegen.
Solution:
Das Houzez Theme ist derzeit als nicht kompatibel mit WPML gelistet. Sie können die bekannten Probleme und Lösungsvorschläge hier einsehen:

• https://wpml.org/errata/houzez-theme-comment-form-button-grid-builder-urls-and-contact-form-cannot-be-translated/
• https://wpml.org/errata/houzez-translated-agent-is-not-assigned-to-translated-properties/
• https://wpml.org/errata/houzez-property-media-images-not-showing-translated-alt-text/

Wir empfehlen, den Theme-Autor zu informieren, dass das Houzez Theme von unserem Compatibility Team als nicht kompatibel eingestuft wurde. Der Theme-Autor sollte sich mit unserem Compatibility-Team in Verbindung setzen, möglicherweise über unser Go Global Programm.

Falls diese Lösung für Ihr Problem irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen Ihnen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.

Problem:
The client was unable to see the translated texts of the Apifon form on the front end of their website after using WPML to translate them.
Solution:
We first verified that the form was correctly translated on the English version of the site. To resolve the issue, we added a custom XML configuration to WPML > Settings > Custom XML Configuration. This configuration ensures that the specific fields of the Apifon Elementor Form Widget are translatable. Here is the XML code we used:

<wpml-config>
  <elementor-widgets>
    <widget name="apifon-form-elementor-widget">
      <fields>
        <field>headline</field>
        <field>placeholder</field>
        <field>button_text</field>
        <field>confirmation_text</field>
        <field>email_required_text</field>
        <field>privacy_required_text</field>
        <field>default_error_text</field>
        <field>privacy</field>
        <field>submit_form</field>
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

If this solution does not resolve your issue, or if it seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.

Problem:
If you're experiencing issues with translating the Accordion Element content in Elementor using WPML, and you need an XML snippet to include in your translations.
Solution:
We recommend you follow these steps:
1. Add the following XML in WPML >> Settings > Custom XML Configuration section:

<wpml-config>
  <elementor-widgets>
    <widget name="rkit_advanced_heading">
      <fields>
        <field>text</field>
      </fields>
    </widget>
    <widget name="rkit-accordion">
      <fields-in-item items_of="list_items">
        <field>accordion_title</field>
        <field>item_description</field>
      </fields-in-item>
    </widget>
  </elementor-widgets>
</wpml-config>

2. Open the default language page in Edit mode.
3. Make a small change, such as adding a space or a '+' sign in the page title where you are facing issues.
4. Save the page.
5. Remove the small change made in step 3.
6. Update the page again.
7. Try to translate the page using WPML Translation Editor and check if you can now translate the Accordion Element content.
For more details, visit our documentation on registering custom Elementor widgets for translation.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.

Problem:
You are unable to translate the content of the Search Placeholder and Generic Text in JetEngine using WPML.
Solution:
We recommend adding the following XML code to WPML > Settings > Custom XML Code (tab):

<wpml-config><elementor-widgets><widget name="jet-smart-filters-checkboxes"><fields><field>apply_button_text</field><field>search_placeholder</field><field>dropdown_placeholder</field></fields></widget></elementor-widgets></wpml-config>

After adding the code, please follow these steps:
1. Go to your Dashboard > Pages.
2. Open the edit screen of the original page and make a small change, such as adding an extra blank space at the end of a sentence or paragraph.
3. Save the changes. You should now see a circular arrow beside the second language links, indicating that an update is required.
4. Edit the translation again and ensure it is saved up to 100% translated.
You should now be able to see the translated placeholders.

If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.