Problem: The client is unable to find HTML elements for translation in the String Translations section of the Flatsome theme. Solution: 1. We recommend enabling the "Look for strings while pages are rendered" option in WPML > String Translation. After checking this option, visit the front-end page where the string appears, then return to WPML > String Translation to search for the string. 2. If the string is still not found, it may be registered as an admin text. Follow the instructions provided in our documentation to find and translate admin text strings: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
If these steps do not resolve the issue, 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 contact us on the WPML support forum: https://wpml.org/forums/forum/english-support/
Problem: The client was unable to display the French version of their logo in the header on their multilingual site. Although the menu was translated correctly and the logo link directed to the French homepage, the English logo persisted despite attempts to change the URL using the String Translator and translating the "main header" global header layout.
Solution: We resolved the issue by taking the following steps: 1. Accessed the WordPress backend, navigated to Divi > Theme Builder, and switched the language to French using the top bar. 2. Edited the global header and changed the logo, then saved the global header.
We asked the client to confirm if the French logo was displaying correctly on their French page.
If you're experiencing a similar issue with your logo not displaying correctly in different languages, we recommend trying the steps above. However, please note that this solution might be outdated or not applicable to your specific case. If the issue persists, we encourage you to check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If you still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client is experiencing an unresolved issue and is seeking live support due to the time zone difference with the assigned support person, which is causing delays in communication. Solution: We recommend closing the current ticket by marking it as resolved and then attempting to open a new request for a live chat session. We explained that the live chat system assigns requests to available slots with colleagues who are handling live chats. If no slots are available, the request automatically becomes a support ticket. If the client is unable to find a live chat session at a certain time, we suggest trying again at a different time of the day.
Please note that this solution might not be relevant if it's outdated or not applicable to your case. If so, we encourage you to open a new support ticket. We also highly recommend checking related 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 contact us through the WPML support forum.
Problem: The client is using Elementor templates and WPML for translating page content. They have a template (container template) translated by WPML, but on the translated page, the content of this template appears in the original language instead of the translated version. Solution: We have identified that the Envo Extra plugin has its own implementation for the
[elementor-template id="ID"]
shortcode, which is causing the issue with WPML. We recommend the following workaround: 1. Edit the
4. After making this change, clear the cache and make minor edits to the page. Then, try re-translating it to see if the issue is resolved. We also suggest asking the plugin/theme author to join our Go-Global program: https://wpml.org/documentation/support/go-global-program/
Please note that this solution might be outdated or not applicable to your case. If it doesn't help, 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: https://wpml.org/forums/forum/english-support/
Problem: The client has detected a problem with some tables in the database related to the WPML plugin, specifically with a string containing special characters (« and »). Solution: If you're experiencing a similar issue, we recommend trying to remove or substitute the special characters (« and ») in the string and checking if the problem persists. If this solution is not relevant to your case, or if it's outdated, we encourage you to open a new support ticket. We also highly recommend checking 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 need further assistance, please don't hesitate to contact us by opening a new ticket in the WPML support forum.
Problem: The client was unable to make changes to the English translation of the home page; changes were reverting to Greek after saving. Solution: We resolved the issue by deleting the existing English translation of the home page and redoing it using the Advanced Translation Editor (ATE). We asked the client to review if using ATE resolved the problem and if everything was functioning correctly.
If you're experiencing a similar issue with your home page translation not saving correctly, we recommend trying the following steps: 1. Delete the problematic translation of your home page. 2. Redo the translation using the Advanced Translation Editor.
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, 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 don't hesitate to open a new support ticket in the WPML support forum.
Problem: The client was experiencing an issue where all products were being skipped during an import from a Google Sheets file, even after replicating all import settings from the provided video and manual.
Solution: We investigated the issue and found that the problem persisted even when WPML (and/or WPML Export and Import) was deactivated. This indicated that the issue was unrelated to WPML. We suggested that the client should look into the WP All Import plugin or the import settings as the likely source of the problem.
If you're experiencing a similar issue with products being skipped during import, we recommend checking your WP All Import plugin and import settings. It's important to note that the solution provided here might be outdated or not applicable to your case. If the issue persists, we highly recommend checking 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 with us.
Problem: The client needed to apply a fix for the WooCommerce Stripe Payment Gateway to limit the Stripe SEPA method to EU countries only, but the provided code snippet did not work for multiple countries. Solution: We recommended using a modified code snippet that checks against a group of EU countries instead of using multiple if-else statements. Here is the code to use:
// Limit Stripe to a group of EU countries only.<br />add_filter( 'woocommerce_available_payment_gateways', function( $gateways ) {<br /> $country = WCML\MultiCurrency\Geolocation::getUserCountry();<br /> // List of EU country codes<br /> $eu_countries = array('AT', 'BE', 'BG', 'CY', 'CZ', 'DE', 'DK', 'EE', 'ES', 'FI', 'FR', 'GB', 'GR', 'HU', 'HR', 'IE', 'IT', 'LT', 'LU', 'LV', 'MT', 'NL', 'PL', 'PT', 'RO', 'SE', 'SI', 'SK');<br /> if ( $country ) {<br /> // Check if the country is not in the list of EU countries<br /> if ( !in_array($country, $eu_countries) ) {<br /> unset( $gateways['stripe'] );<br /> }<br /> }<br /><br /> return $gateways;<br />} );
We also noted that this code is a helpful adjustment and has not undergone official testing by our team, nor will it be supported by us. We advised the client to ensure they have a complete, working backup of their system before implementation.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If this is the case, we highly recommend checking 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.
Problem: The client was unable to see the translated image for one of the translated language on the live site. Solution: We found that the issue was related to the Redis Object Cache plugin. We recommend flushing the Redis Object Cache to resolve the problem. After performing this action, the translated image should appear correctly. If you're experiencing this issue, we suggest trying the following steps: 1. Go to the Redis Object Cache plugin settings in your WordPress dashboard. 2. Click on the 'Flush Cache' button to clear the cache. 3. Check your live site to see if the translated image is now displaying. Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If after trying these steps the issue persists, we highly recommend checking related 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 do not hesitate to open a new support ticket with us. You can reach the WPML support forum here.
Problem: The client reported that even though the slider was set up, it was not appearing in Romanian and Spanish. Additionally, the text and button associated with the slider were not showing up in any language. Solution: We informed the client that we were already assisting them with this issue in another support ticket. We recommended that the client should not open multiple tickets for the same problem and to continue the conversation in the existing ticket.
If you're experiencing similar issues with your slider not appearing in different languages or missing elements like text and buttons, we recommend checking the ongoing discussions in our support forum for similar cases. It's important to note that the solution provided here might be outdated or not applicable to your case. If after reviewing related known issues at https://wpml.org/known-issues/ and ensuring you have the latest versions of themes and plugins installed, you still face the problem, please do not hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client is experiencing an issue where additional strings are in English instead of French, possibly due to a language selector setting in the WP Cookie consent plugin, with the site's main language being French. Solution: We recommend changing the source language of the string before translating it. Please follow this guide to change the source language to English and then translate the string to French: How to change the source language of strings. After completing these steps, verify if the string displays correctly in French.
If this solution does not apply to your situation, or if it seems outdated, we encourage you to open a new support ticket. We also 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.
Problem: The client was experiencing an issue where ACF custom fields on pages as flexible content were translated in the backend but the page appeared empty on the second language frontend. The client had a template for these subpages and ACF was set to have the same fields across languages. The template used was translated, but the conditions applied to which subpages the template is applied to did not transfer.
Solution: We suggested that the client should try translating the parent page to ensure that the template conditions are correctly applied to the subpages in all languages. Additionally, we made some changes to the template to ensure that the ACF field references matched correctly.
If you're experiencing a similar issue, we recommend you: 1. Translate the parent page to the secondary language. 2. Check that the template conditions are correctly applied to the subpages in all languages. 3. Verify that the ACF field references in the template match correctly.
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, 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 with us.
Problem: The client was experiencing an issue where a product purchase form in the default language displayed two input fields, but in the second language, one field was missing.
Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML >> Settings >> Custom Fields Translation section. 2. Click on the “Show system fields” link. 3. Locate the “Enable From Name:” checkbox field
_woo_vou_enable_recipient_from_name
and set it to “Copy”. 4. Find the “Label:” field
_woo_vou_recipient_from_name_label
and set it to “Translate”. 5. Make a small change in the default language product to reload the translation, then add the translation of the label field.
This should solve the issue.
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 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.
Problem: The client is experiencing an issue where the filter values in the left column on their WooCommerce site are not translated into Greek, despite having translated them in String Translation. The filter headers are translated correctly, but the values (e.g., chains, charms) remain in English. The filters are from ACF fields and displayed on the frontend with the WBW Product Filter widget.
Solution: We first acknowledged that the WBW Product Filter plugin is not on our list of officially compatible plugins, which could lead to issues. We then suggested: 1. Checking if the ACF field format includes both a value and a label, as this might help in displaying the correct translations. 2. Considering the use of officially compatible plugins for filtering, which can be found on our compatible plugins list. 3. For attributes, we recommended possibly using WooCommerce global attributes instead of ACF and translating them accordingly. Helpful documentation can be found here:
4. We also advised contacting the plugin author for a potential solution and inviting them to join our GoGlobal program at GoGlobal, where we offer assistance to make plugins compatible.
If this solution is not relevant to your case, either because it's outdated or not applicable, 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 in our support forum.
Problema: El cliente tenía dos problemas: 1. Un problema de permisos con la carpeta de idiomas, a pesar de que los permisos estaban establecidos en 777. 2. Incapacidad para actualizar los plugins en un entorno de staging debido a la falta de una clave de sitio para registrar el sitio de staging.
Solución: Para el primer problema, recreamos la carpeta de idiomas utilizando el plugin de administración de archivos o FTP.
Para el segundo problema, proporcionamos los siguientes pasos: 1. Crear la licencia en la cuenta de WPML.org del cliente. 2. Añadir la clave de licencia al sitio de staging. Proporcionamos un enlace a la documentación relevante para guiar al cliente en el proceso: Documentación para registrar el sitio de staging Si la solución proporcionada no es relevante debido a que está desactualizada o no se aplica a su caso, le recomendamos abrir un nuevo ticket de soporte. También recomendamos revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que ha instalado las últimas versiones de temas y plugins.
Si necesita asistencia adicional, por favor, póngase en contacto con nosotros en el foro de soporte de WPML.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
