Known issue

Problem:

You are trying to update translations in a secondary language using WPML, but after translating, the gear icon still appears instead of the pencil icon. You are wondering why the gear icon appears after translating and how to ensure the pencil icon appears after translation.

Solution:

We recommend following the steps outlined in the WPML errata to address this issue. Please visit the following link for detailed instructions: https://wpml.org/errata/elementor-php-fatal-error-call-to-a-member-function-get_main_id-on-null/

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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.

Problem:
You are trying to complete the translation of your forms using WPML, but you are encountering an issue with Font Awesome glyph icons in HTML. Strings with glyph icons are not saved, and the translation is not 100% completed, leaving some English text on translated pages/forms.
Solution:
1. Increase the PHP memory limit to at least 512M. You can do this by adding the following code to your

wp-config.php

file just above the line that says '/* That's all, stop editing! Happy blogging. */':

/** Memory Limit */<br />define('WP_MEMORY_LIMIT', '512M');<br />define('WP_MAX_MEMORY_LIMIT', '512M');

2. Enable the previous version of the Advanced translation editor. Go to the advanced translation editor, click the gear icon on the top right to access settings, enable the 'Previous version' option, provide feedback, and submit to reload the page.
3. Apply the fix for a known issue with Gravity Forms by following the steps outlined here: https://wpml.org/errata/gravity-forms-merge-tags-are-available-for-translation/

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 at WPML support forum.

Problem:
The client's website is set up in multiple languages, and they are using the Events Calendar with WPML for translations. The main issues were that events were only showing in the Spanish version and not in other languages like Catalan, and some strings from the Events Calendar were not appearing translated on the event pages despite being translated in WPML.

Solution:
1. To ensure events appear in all languages, we advised setting the translation preference for the 'tribe_events' post type to 'Translatable - use translation if available or fallback to default language' in WPML > Settings > Post Type Translation.
2. For the untranslated strings, we recommended rescanning the Events Calendar plugin for strings via WPML > Theme and Plugins Localization, then translating them in WPML > String Translation. If strings still did not appear translated, generating MO files through WPML > Support > Troubleshooting was suggested.
3. We also addressed a specific issue with the string 'Calendar' appearing twice by removing the duplicate translation in WPML > String Translation.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, visit our support forum at https://wpml.org/forums/forum/english-support/.

Problem:
If you're experiencing issues after updating the WPML String Translation plugin to version 3.2.16 or 3.2.17, it might be due to a specific function causing the website to break if the domain contains the string 'mo'.
Solution:
We recommend checking out the temporary workaround provided on our forum. You can find more information here: WPML support forum topic.

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

Problème :
Si vous activez WPML String Translation et que cela entraîne une erreur critique sur votre site, avec des erreurs PHP telles que 'Function _load_textdomain_just_in_time was called incorrectly' et 'PHP Fatal error: Uncaught TypeError: strlen(): Argument #1 ($string) must be of type string, array given', voici les étapes à suivre pour résoudre le problème.
Solution :
1. Nous avons identifié que ce problème est déjà connu et documenté ici : https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
2. Pour le 'Fatal error: Uncaught TypeError: strlen()', bien que le rapport d'erreur complet ne soit pas visible, des cas similaires ont été observés avec des versions de PHP supérieures à 8.2. Plus d'informations ici : https://wpml.org/forums/topic/string-translation-incompatible-with-php-8-2/
3. Essayez de rétrograder votre version de PHP à 8.0 pour voir si cela résout l'erreur.
4. Si le problème persiste, désactivez tous les plugins sauf WPML CMS et changez temporairement pour un thème WordPress par défaut comme Twenty Twenty-one. Réactivez ensuite les plugins un par un pour identifier le plugin problématique.
5. Pour la fonction '_load_textdomain_just_in_time', une mise à jour est attendue de WordPress. En attendant, vous pouvez télécharger la version 3.2.17 de String Translation qui résout de nombreux problèmes liés à cet avis ici : https://wpml.org/fr/account/downloads/
6. Vous pouvez également masquer ces avis depuis le front-end en ajoutant les lignes suivantes dans votre fichier wp-config.php :

define('WP_DEBUG_DISPLAY', false);<br />@ini_set('display_errors',0);

Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.