sreckoA

Problem:
The client was experiencing issues with translated pages, posts, and portfolios losing styles and not displaying like the original. Additionally, some content was not appearing in the translation editor, and there were problems with untranslated strings in Elementor widgets and custom fields.
Solution:
1. We registered the necessary Elementor widgets for translation by adding custom XML configuration in WPML->Settings->Custom XML tab. Here is the code used:

<wpml-config><br />  <elementor-widgets><br />    <widget name="gva-heading-block"><br />      <fields><br />        <field>title_text</field><br />        <field>description_text</field><br />        <field>button_text</field><br />        <field>sub_title</field><br />      </fields><br />    </widget><br />    <widget name="gva-image-content"><br />      <fields><br />        <field>title_text</field><br />        <field>link_text</field><br />        <field>link>url</field><br />      </fields><br />    </widget><br />  </elementor-widgets><br /></wpml-config>

2. We set the translation preferences for custom fields in the Meta Options.
3. We advised the client to update the pages in the default language and their translations to apply the changes.
4. For untranslated strings and widgets, we provided guides on how to handle translations:
- Registering Custom Elementor Widgets for Translation
- Translating MailChimp Forms
- Translating Widgets

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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 the problem persists, please open a new support ticket.

Problem:
The client was unable to locate specific strings for translation within their WordPress site. They had tried searching through various categories and using exact matches but were unsure of the source of these strings, whether from a theme or a plugin. One string was in English, and another was automatically translated to Serbian with incorrect pluralization upon switching the WordPress language setting.

Solution:
We recommended two methods to locate and translate the strings:
1. Navigate to WPML > String Translation and enable the option "Look for strings while pages are rendered" at the bottom of the page. Then, visit the front end where the string appears, return to WPML > String Translation, and search for the string.
2. If the string is not found in the WPML > String Translation, it might be categorized as an admin text string. For detailed steps on how to find and translate admin text strings, visit this documentation.

If these methods do not resolve the issue, or if the solution 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.