Custom Work

Problem:
If you're experiencing issues where internal links added to images in Elementor are not translatable or editable in the WPML side-by-side editor, preventing the creation of fully functional translated pages.
Solution:
1. **Search for the links in the Advanced Translation Editor**
Open the page translation in the Advanced Translation Editor and use the search bar to locate common link elements. This might reveal the image URLs that were not immediately obvious.

2. **Update the WPML configuration**
If the links are still not editable, you might need to update your WPML configuration. Add the following XML configuration to your site:

<wpml-config>
  <elementor-widgets>
    <widget name="image">
      <fields>
        <field type="Image URL" editor_type="LINK">link>url</field>
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

For more details on registering page builder widgets for translation, visit https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/.

If this solution does not resolve your issue, or if it seems outdated or not applicable 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 needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/ for further assistance.

Problem:
You want to translate the JavaScript and PHP files on your website.
Solution:
To make text in these files translatable, you need to register the strings with WordPress' localization functions. Here's how:

For PHP files:
Wrap any user-facing text in WordPress i18n functions such as

__()

or

_e()

with your theme or plugin text domain. For example:

echo __( 'Your text here', 'theme-textdomain' );

For JavaScript files:
Text hardcoded in JavaScript files cannot be translated automatically. Instead, pass strings from PHP to JavaScript using functions like

wp_localize_script()

or

wp_set_script_translations()

. For example:

wp_localize_script( 'my-script', 'myStrings', [ 'welcome' => __( 'Welcome message', 'theme-textdomain' ) ]);

After registering, you can find these strings in WPML → String Translation, where you can provide translations for each language.

If you need further assistance or if this solution does not apply 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 the issue persists, please open a new support ticket.

Problem:
The client is experiencing an issue where after switching from the Linguise language plugin to WPML, the URL slug for Portuguese changed from 'pt' to 'pt-pt', and they want to revert it back to the original 'pt' slug.
Solution:
If you're experiencing this issue, we recommend creating a custom language in WPML where you can specify the desired language code. Here's how you can do it:
1. Go to WPML > Languages.
2. Under 'Edit Languages', click on 'Add languages'.
3. Enter the language name, code (in this case, 'pt'), and other details.
4. Save your changes.
This should help you set the URL slug to your preferred format.

Please note that this solution might be irrelevant if it's outdated or not applicable 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
You've created custom Gutenberg blocks and are facing issues with the translation of the title field in your 'Text Image Item' block. While the title translates correctly in the editor, it does not translate on the frontend and remains in German.
Solution:
We recommend updating your WPML configuration for the custom blocks. Here is the correct XML code you should use:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="palllm/text-image" translate="1"></gutenberg-block>
    <gutenberg-block type="palllm/text-image-item" translate="1">
      <xpath>//h2</xpath>
    </gutenberg-block>
    <gutenberg-block type="core/paragraph" translate="1">
      <xpath>//p</xpath>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

Add this code in WPML -> Settings -> Custom XML Configuration by replacing the current code for this Text Image block that does not work.
Additionally, consider using our Multilingual Tools plugin to generate WPML configurations. For more information, please visit https://wpml.org/documentation/support/multilingual-tools/.

If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at https://wpml.org/forums/forum/english-support/.