Problem: The client is experiencing issues with their website's design falling apart and not translating correctly after using WPML to translate from Japanese to English. Solution: We recommended performing a WPML reset to revert the site to its state before the WPML installation. This process involves deleting languages and plugin data. For detailed instructions on how to perform a WPML reset, please follow this guide: Deleting Languages and Plugin Data by Doing a WPML Reset on Your Site.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the translated archive of the Modern Events Calendar (MEC) on a WordPress site using WPML. The main archive in French displays correctly, but the English translated archive shows only the archive title without the MEC calendar/archive output. The archive title is also incorrectly displayed in French.
Solution: We found that there were two different event archive pages on the site: the default archive page generated by the MEC plugin and a custom page that was manually created but not translated. To resolve the issue, the custom page needs translation so the English version can display correctly. Additionally, we adjusted the WPML settings to set the shortcodes on the page to "Do not translate" and advised not to translate the default slug of the Events post type generated by the MEC plugin. Both pages are now functioning correctly.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was facing issues with translating the footer and header in the Divi theme. Specifically, the footer translation location was unclear, and the header displayed differently in the Polish version, missing a shop page and categories not appearing in a dropdown. Solution: For the header issue, we edited the Divi Body Template in the Divi editor, saved the changes, and then reverted them. We then accessed the template translation from the WPML Translation Dashboard or directly from the editing page. This resolved the display issues with the shop content. For translating the footer, you should locate the appropriate Divi template (Divi layouts, Divi templates, Divi footer, etc.) in your translation panel. If you're experiencing similar issues, we recommend checking the specific template where the footer is designed and translating it directly from there.
Please note that this solution might be 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: Some media isn't showing even though it's already translated. Solution: If you're experiencing issues with media not displaying correctly, even though it's translated, the problem might be due to the image being displayed not being the category Thumbnail, but the Featured Image that comes from the theme options for the category. We recommend you try the following steps: 1. Go to the translated category. 2. Upload the same image to the Featured Image field for that translated category. Once the Featured Image is set for the translation, the correct image should appear on the frontend.
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 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.
Problem: You are experiencing an issue where a single block template created in the Site Editor, when translated, receives a different slug, causing the front end page not to recognize the template. Solution: We recommend following the workaround described in our errata to address the slug mismatch issue. Please visit the following link for detailed steps: https://wpml.org/errata/template-is-not-applied-to-translated-page/ If the problem persists after implementing these steps, we encourage you to open a new support ticket for further assistance. 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 need further assistance, please contact us through our support forum: WPML Support Forum
If you're experiencing a fatal error with a message about 'Maximum call stack size' and suspect it might be due to infinite recursion in the WPML plugin, particularly when using Advanced Custom Fields (ACF).
If you're experiencing a fatal error with a message about 'Maximum call stack size' and suspect it might be due to infinite recursion in the WPML plugin, particularly when using Advanced Custom Fields (ACF).
Problem: The client de-authenticated Skrivanek and deleted the connection, but all translation jobs are still pending and cannot be canceled, showing the error: 'This action does not apply to any of the selected translation jobs'. Solution: If you're experiencing this issue, we recommend you try the following steps: First, check if the translation job can be canceled: 1. Go to WPML → Translation Management → Jobs. 2. Check whether the translation jobs are listed there and see if you can cancel them. If you are unable to cancel the job from there: 1. Go to WPML → Translation Management. 2. Select the page for which you want to cancel the translation job. 3. Send it again for translation. 4. Choose Translate myself, and you should then be able to translate it manually from WPML → Translations.
If this solution does not apply to your case, or if it seems outdated, 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 WPML Support Forum.
Problem: When selecting the Korean language, the entire site crashes due to a fatal error. This issue recurs despite previous attempts to resolve it by rolling back the Presto Player version. Additionally, the Korean .po file lacks translations for this plugin. Solution: We resolved the issue by taking the following steps: - Navigate to WPML → Themes and Plugin Localization and scan the Presto Player plugin to register all translatable strings. - Proceed to WPML → String Translations, search for the problematic strings 'Rewind %1ss' and 'Forward %1ss', and update their translations. We recommend you replicate these steps on your live site to resolve the issue.
If this solution does not apply because it might be outdated or not suitable for your specific case, please 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. For further assistance, you can contact us through the WPML support forum.
Problem: The client is facing an issue where unique HubSpot forms added to contact pages in different languages are overwritten by WPML each time translations are updated. Solution: We recommend using the WordPress Editor to manage the content of the pages where unique forms are required, as the WPML Editor and the WordPress Editor are independent. Content created with one cannot be edited with the other. You should set the WordPress Editor on a page/post level basis, for a post type, or for the entire website, specifically for pages that need different designs or custom HTML per language. It is crucial to have a backup before testing any settings.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: Text in some checkout fields regarding shipping options and payment options are not translated. Solution: If you're experiencing untranslated text in checkout fields, we recommend you first change the language of the current strings to Latvian and then translate them to English to see if this resolves the issue. Additionally, you can change the source language of the whole domain for current and future strings via WPML->String Translations->Set the original language of themes and plugins. For further assistance, please provide us with your debug information by following the detailed instructions at http://wpml.org/faq/provide-debug-information-faster-support/.
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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client inherited a website where translated custom post types were not displaying correctly. Despite the fields being marked as 'translation complete', only the titles and URLs were correctly translated when switching languages, while the main content did not appear. Solution: We identified two main issues affecting the display of translated content: 1. The ACF post types were incorrectly set as translatable in WPML. We recommended setting these to 'Not translatable' as only the content should be translated, not the ACF structure itself. 2. The Elementor template used for the products was saved as 'Draft' instead of 'Published'. Publishing the template resolved the display issues. We advised the client to delete any duplicate translated ACF post types and ensure that only the original remains. Additionally, it's important to switch the admin language to the desired language (Catalan in this case) to confirm that the relevant template is published.
Please note that this solution might be outdated or not applicable to your specific 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 at WPML support forum for further assistance.
Problem: If you're experiencing issues where your site defaults to English and does not switch back from Arabic correctly, the problem might be related to your site's configuration. Solution: We recommend checking your
Please remove these lines and see if that resolves the issue. This adjustment should help in correctly switching the languages on your site.
Keep in mind 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 problem persists, please open a new support ticket.
Problem: You are experiencing an issue where, despite having fully translated your pages/posts in the Advanced Translation Editor and completing the process, the translation status icon remains a red exclamation mark (or "needs update" sign) instead of changing to the green checkmark. Solution: We recommend checking if there is obsolete content data in your posts. You can do this by selecting a problematic post, editing it, and simply clicking on 'Update' to save the current content to the database. After updating, try sending the post to automatic translation again. If the status correctly displays green checkmarks (completed), the issue is resolved. For other posts or pages, you can use the bulk edit option on the listings page to update them without making any changes, and then send them to automatic translation on the Translation Dashboard.
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, if you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to translate the answer texts to multiple-choice questions and section body texts in quizzes and courses using LearnPress with the WPML plugin. Despite following the available guides and documentation, these specific strings do not appear in the WPML String Translation interface.
Solution: We recommend translating the quizzes and courses directly in the WordPress editor after running them through the WPML translation process. This method allows for manual translation of all content, including the problematic strings that do not show up in the WPML String Translation interface. For detailed steps on using different translation editors, please refer to our documentation: Using Different Translation Editors for Different Pages.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
