Custom Work

Problem:
If you're experiencing an issue where a string is not outputting in the Estonian language and instead shows in English, despite being translated in WPML String Translation, this might be due to the text domain settings. For instance, using

esc_html_e( 'Privacy settings', 'cookieconsent' )

might not work, but changing the text domain to your theme's text domain, like

__( 'Privacy settings', 'child-theme' )

, resolves the issue.

Solution:
We recommend keeping the function that outputs the string and then scanning your theme for strings. Here are the steps:
1. Keep the function:

function my_translated_string_output() {<br />    echo '<div class="translated-message">';<br />    esc_html_e( 'Privacy settings', 'cookieconsent' );<br />    echo '</div>';<br />}<br />add_action( 'wp_body_open', 'my_translated_string_output' );

2. Go to your WordPress Dashboard > WPML > Theme and plugins localization and select your theme to scan.
3. After the scan, navigate to WordPress Dashboard > WPML > String translation and search for the string in question.
4. Ensure the content of the string matches the flag next to it. If not, set the source language correctly by following this guide: How to change the source language of strings.
5. Complete the translation and check the front end.

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

Problem:
The client is unable to translate the words "Country" and "City" on their website, which is caused by custom JavaScript code added via the WPCode plugin.
Solution:
1. Temporarily disable the custom code added via WPCode and verify that translations work correctly.
2. Contact the developer who created the custom script and ask them to make the JavaScript strings translatable using WordPress localization functions. For guidance on how to localize scripts, visit the WordPress documentation: https://developer.wordpress.org/reference/functions/wp_localize_script/
Since custom JavaScript implementation is outside our support scope, the developer of the code will be the best person to adjust it.

If this solution does not resolve your issue or seems outdated, we 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. Should you need further assistance, please open a new support ticket at WPML support forum.

Problem:
The client is trying to prioritize the display of translated content on their multilingual site, but is unsure how to configure WPML to achieve this specific behavior.
Solution:
We explained that with the current features available in WPML, it is not possible to customize the content display to prioritize translated content as the client desires. The client can either:
1. Display only translated content.
2. Enable the fallback mode to show untranslated content as well.
Both options will result in the content being displayed in the same manner as it currently appears on the site.

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