Problem: The client is trying to translate the hover text of some buttons and call to action elements on a DIVI website from Italian to German and English, but the field to insert the translation does not appear in the WPML translation editor.
Solution: First, we asked the client to confirm how they were translating the content and whether the hover text appeared in the WPML translation editor. Since the fields were not compatible, we requested access to the site to make them compatible and to send the case to our team for updating the compatibility file. We suspected that the field might be new or recent, which is why it wasn't compatible yet.
We then provided the client with a code snippet to add to the WPML configuration file to allow HTML in certain fields of the DIVI 'call to action' module. The client was instructed to add the module that wasn't translating correctly to a draft page and send it for translation again through WPML > Translation Management after applying the code.
If the solution provided here is not relevant to your case, because it might be 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 the issue persists, please open a new support ticket with us.
Problem: The client was experiencing an issue where manually translated content in Cornerstone was overwriting content on the secondary language.
Solution: We advised the client to update all outdated plugins and themes, especially WPML-related plugins. To update WPML plugins, the client needed to: 1. Go to the 'Commercial' tab in the 'Add New' section of the 'Plugins' menu. 2. Unregister WPML from the site if the registration key didn't match. 3. Remove the actual site from their WPML account. 4. Register the site again with the correct key. After updating the plugins, we asked the client to check if the issue persisted by creating a new test page. When the issue was still present, we requested authorization to run tests and eventually escalated the issue to our 2nd tier support team.
Please note that this solution might be 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 necessary, please open a new support ticket for further assistance.
Problem: The client is new to WPML and is facing an issue where right sidebar widgets are appearing on the homepage of the Chinese translation, and they are unsure how to suppress this. Solution: We recommend checking the widget settings in the WordPress admin area. There might be an option that controls the display of widgets on translated pages. We provided a screenshot to the client showing where this option can be found in the admin area.
If this solution does not apply to your case, or if it seems outdated, we encourage you to open a new support ticket. We also 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 need further assistance, please visit our support forum.
Problem: The client was unable to translate the Divi theme's Global Header and Global Footer using WPML. When attempting to add these items to the Translation queue, the queue remained empty with the Classic Translation Editor, and a critical error occurred with the Advanced Translation Editor. Solution: We checked the issue and discovered that some WPML tables in the database were missing keys, such as
wp_icl_translate
and
wp_icl_translate_job
. We manually created the missing keys for the client. We then asked the client to try translating the templates again to see if the problem was resolved.
If you're experiencing similar issues with translating Divi's Global Header and Global Footer, we recommend checking your database for missing keys in WPML tables and creating them if necessary. However, 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.
Problema: El cliente no pudo sincronizar su menú existente y también encontró que la plantilla de su tema no estaba traducida. Solución: Primero, revisamos el menú del cliente y descubrimos que el problema se debía a que se habían incluido enlaces personalizados para las Categorías en el Menú, en lugar de agregar directamente las Categorías de Productos. Para resolver esto, insertamos las Categorías de Productos en el Menú y sincronizamos el menú. Esto actualizó correctamente las Categorías en el menú en otros idiomas de acuerdo con sus traducciones. Si estás experimentando este problema, te recomendamos que intentes agregar las Categorías de Productos directamente en tu menú y luego sincronizar el menú para asegurarte de que se actualicen en todos los idiomas.
Es posible que esta solución no sea relevante para tu caso si es que está desactualizada o simplemente no se aplica a tu situación. Si es así, te sugerimos abrir un nuevo ticket de soporte. También te recomendamos encarecidamente que revises los problemas conocidos, verifiques la versión de la solución permanente y confirmes que has instalado las últimas versiones de temas y plugins.
Problem: The client expected the website to automatically display in German after selecting the language on the homepage, but the language did not change as expected. Solution: We recommend checking the language switcher options. The name of the language that appears in the language switcher is configurable. You can set the desired language by following the instructions on how to edit WPML's language table and adding your own languages using WPML's GUI. For detailed steps, please refer to the documentation: Editing WPML's Languages Table.
Please note that the solution provided 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 do not hesitate to open a new support ticket with us.
We noticed that the language flags were not displaying consistently across pages, which could be due to pages not being translated into all languages. If a page is not translated into a certain language, the flag for that language will not appear.
We also observed that the WP memory limit was below the minimum requirements for WPML, which is 128MB. We provided instructions to increase the memory limit.
If the solution provided is outdated or not applicable to the client's case, we suggest opening a new support ticket for further assistance. For additional support, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: If you're using The Events Calendar plugin and have translated the events slug in WPML, but the language switcher doesn't show the other languages unless you access the page directly via link (e.g., /it/events), where the switcher then displays normally. Solution: First, ensure that you have translated the Events into the respective languages. If the Events are not translated, they will not appear in the language switcher. For example, if the Event archive displayed only French in the language switcher, it indicates that Events are only available in French. Once you translate an Event into another language, such as English, the language switcher will start to include that language as an option.
If you want to show the default Events (in French) for other languages when translations are not available, you can adjust the WPML settings. Go to WPML > Settings > Post Type Translation and set the translation preference for the "Events" post type to "Translatable - use translation if available or fallback to default language". This setting will allow the default language events to be displayed in the language switcher even if they are not translated into other languages.
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's footer padding disappeared after translating it into German, and the 'container-fluid' class was missing on the translated page. Solution: We checked the translated footer template and found that the 'Wrap as Container' value was not set correctly. We selected the correct value, which resolved the issue. If you're experiencing a similar problem, we recommend checking the 'Wrap as Container' value in your translated footer template and ensuring it is set correctly.
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 open a new support ticket.
Problem: The client is trying to translate dropdown fields in a form created with the Contact Form 7 plugin but sees the original strings instead of the translations. Solution: We recommend searching for the field values in the search input box in Advance Translation Editor as shown in the provided screenshot. We have replicated the issue on a fresh WP site and confirmed that the translation is working correctly.
For more details, please refer to the following documentation:
If this does not resolve your issue or you need further assistance, please do not hesitate 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.
If you require additional help, please contact us in the WPML support forum: WPML support forum.
Problem: If you're on a pay-as-you-go plan and receive a message stating 'You don't have enough credits to translate automatically!' during translations, this is not an issue but a matter of understanding how the system works.
Solution: We have determined that since you've set your translation mode to 'Translate What You Choose' in WPML -> Settings, and automatic translation by default is turned off, you won't see a link on the Translation Management Dashboard even if you reach the 195K limit. However, you can still automatically translate from within the Advanced Translation Editor (ATE). If you need more credits than the available limit, follow these steps: 1. Go to your pages or posts and select one with substantial content that requires translation. 2. Click the '+' to add the translation. 3. In ATE, you will see the 'not enough credits' message with a 'Get more credits' link. 4. Click 'Get more credits' to proceed to the payment option.
If the solution provided here does not apply to your situation, or if it seems outdated, 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 open a new support ticket.
Problem: The client was experiencing issues with automatic translation not functioning properly on their website. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML > Settings. 2. Under Translation Mode, switch to 'Translate What You Choose'. 3. In the Translation Editor section, select 'Editor for new translations: Classic Translation Editor', then save and reload the page. 4. Switch back to 'Advanced Translation Editor' and set Translation Mode to 'Translate Everything Automatically'. After performing these steps, changes to the page content should be translated automatically.
Please note that this solution might not be relevant 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 reported that WPML was loading many fields named 'field-obsah' containing text from previous versions of posts, which were not present in the current version of the post in the original language. These fields were unnecessarily consuming translation credits during automatic translation. Solution: We recommended the following steps: 1. Navigate to WPML > Settings > Custom Fields Translation. 2. Use the search input to locate the 'field-obsah' field. 3. Set it to 'Don't Translate'. 4. Edit the original post and make a small change. 5. Update the translation. For more detailed instructions, please refer to our guide on translating custom fields.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, 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 the WPML support forum.
Problem: The client is unable to translate strings from English to Latvian for a new gift card plugin. Despite translating the string "You Print & Give To Recipient" to Latvian, it still appears in English on the frontend. The client has already increased the memory limit, deleted and re-translated the string, but the issue persists. Solution: We recommend checking for duplicate strings that may not have been translated. Here are the steps to follow: 1. Navigate to WPML > String Translation and at the bottom of the page, enable the checkbox "Look for strings while pages are rendered". Then, visit the frontend page where the string should appear and return to WPML > String Translation to search for the string. 2. If the string is not found in WPML > String Translation, it might be registered as admin text. Follow the process outlined 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/
Please note that the solution provided might be 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 necessary, please open a new support ticket for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
