Problem: You are using Elementor with WPML on your site and have encountered an issue where updating a custom field in one language affects the other language in an Elementor Loop Carousel. Specifically, when you update the custom field setting in the English version, it also changes the setting for the Polish version, due to shared widget configuration across languages. Solution: To resolve this issue, we recommend using a manual translation approach to prevent synchronization of the custom fields across different languages. You can find detailed instructions on how to implement this by visiting the following documentation: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, please check the 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 if you continue to experience issues.
The customer was unable to find and translate hardcoded text from their homepage using WPML’s String Translation feature, even after scanning the theme and plugins. They also experienced an issue where fonts were not loading correctly in the WPML admin panel, but they were advised to open a separate ticket for that.
Solution:
1. We first suggested enabling Auto Register in WPML > String Translation and refreshing the front end to check if the missing text appears for translation.
2. Then, we provided the correct method to make the hardcoded text translatable by wrapping it inside the "__()" or "_e()" functions in PHP, which registers the strings for WPML’s String Translation module.
3. The customer later asked how to make the FAQ section translatable. Mihai explained that:
- The FAQ title should be wrapped in "__()" or "_e()".
- The FAQ questions needed to be registered as translatable strings using "apply_filters('wpml_translate_single_string', $question, 'FAQ', 'FAQ Question ' . $count);"
- The FAQ answers should be registered the same way if they are stored dynamically.
4. We also advised scanning WPML > Theme and Plugin Localization if the strings still didn’t appear.
5. Finally, we noted that implementing these solutions requires custom work, which falls outside WPML’s support policy, but we provided guidance to help the customer move forward.
Problem: The client modified the English part of a string in their custom theme's PHP file and updated the translation in WPML, but the Polish tag archive pages still displayed the untranslated string 'Sorted articles by'. Solution: 1. Ensure that all WPML plugins are updated to the latest versions and check if the issue persists when all other plugins are disabled, using only WPML plugins. 2. Test the translation of the modified string on different pages and with the default WordPress theme, such as 2021, to see if the issue is specific to the custom theme. 3. Replace the variable in the gettext function with a literal string for the text domain in the PHP file:
4. Rescan the theme for strings in WPML under 'Theme and plugins localization' and then translate the strings again in 'String Translation'. For more details on enabling text translation for themes not compatible with WPML, visit https://wpml.org/documentation/support/enabling-text-translation-for-themes-not-compatible-with-wpml/. If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was unable to edit English posts with a user account that lacked proper language pair assignments in WPML's translation management. Solution: We advised the client to assign the user as a translator with the appropriate language pairs via WPML->Translation Management->Translators. Additionally, we addressed an issue where the Translation Management screen appeared blank. This was resolved by ensuring the user had administrator privileges and by refreshing the WPML license status. Steps included removing and re-adding the site in the WPML account to generate a new key, unregistering, and re-registering WPML in the Plugins section.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client was experiencing an issue where almost all pages had the correct breadcrumb translation, but one page displayed an English text in the breadcrumb instead of the expected language.
Solution: We found that the text in question was set manually for the default language within the theme options. To resolve this, we added the text for translation via the admin text option in WPML. This allowed the client to translate the breadcrumb text correctly. We provided documentation to help understand how to translate strings that don't appear on the String Translation page:
If you're experiencing a similar issue, we recommend you try adding the text for translation through the WPML admin text option and then translate it accordingly.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket in the WPML support forum.
Problem: The client was unable to update the site title and subtitle in different languages. Previously, they could change these in the settings under 'General' for each language, but now saving changes in one language caused the titles to revert to English.
Solution: 1. We clarified that the site title from WordPress settings is not the same as the page content/title. The client should add the title in the default language and then translate it using WPML String Translation.
2. We identified that the string the client mentioned is from an SEO plugin and appears in different parts of the website/code. We provided documentation on how to set SEO titles and descriptions:
4. We also addressed the client's concern about translations disappearing and suggested re-translating the strings or importing them back from an old backup if available.
In a follow-up, we reiterated that while it is possible to add translations for the site title in WP Settings in both languages, it is not the recommended approach. Instead, the client should use WPML String Translation, referencing the following sources:
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client encountered a warning popup when trying to edit a translation in the WordPress editor, despite never having used the WPML Translation Editor for translations. Solution: The warning appeared because the client was trying to manually edit translations while the WPML Translation Editor was still enabled. To resolve this, we advised the client to disable the WPML Translation Editor by following these steps: 1. Locate the Language meta box in the sidebar in default language page. 2. Choose the WordPress Editor to translate the page instead of the WPML Translation Editor. 3. In the pop-up dialog that appears, select the appropriate option (This page/All pages/etc.).
We also mentioned that failing to disable the WPML Translation Editor when manually editing translations could result in lost translations upon updating the default language. If the provided solution does not apply or is outdated, or if the client is still experiencing issues, we recommend opening a new support ticket. Additionally, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed.
Problem: The client was trying to enable the Polish translation for WooCommerce by following a guide and uploading the .mo file to the
/languages/woocommerce
directory, but the strings remained in English. Solution: We found that the translation should load automatically from WooCommerce. However, there is a known issue where translations do not load when using the block cart and block checkout if
WP_PLUGIN_DIR
and
WP_PLUGIN_URL
are defined in
wp-config.php
. To work around this problem, we recommend: 1. Using the
[woocommerce_cart]
shortcode on the cart page instead of blocks. 2. Removing the
WP_PLUGIN_DIR
and
WP_PLUGIN_URL
definitions from
wp-config.php
and using the standard plugins folder.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly 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 you still need assistance, please open a new support ticket.
