Problem: You are unable to use Avada's Live Editor on translation pages when the WPML plugin is activated. Deactivating WPML allows you to edit the page in the live editor, but reactivating it makes it impossible again. Solution: We recommend using the WPML translation editor as the default method for translating Avada layouts/pages. You can find more information here: Using WPML with the Avada Theme. If you prefer to use the Avada builder on the translated content, this requires a manual approach. You will need to disable the WPML translation editor for the pages you wish to translate/edit via the Avada builder. Detailed steps can be found here: Using Different Translation Editors for Different Pages.
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 open a new support ticket at WPML Support Forum.
Problem: If you're experiencing issues with changing the style and typography for different languages while using the WPBakery page builder, we can help. Solution: Unfortunately, there isn't a direct option in the WPBakery page builder's user interface to customize styles per language. However, you can achieve this by adding custom CSS. Here's a step-by-step guide: 1. Create custom CSS specific to the language. For example, to change the style for Hebrew, you can use:
2. Replace "he-IL" with the appropriate language code for the language you are targeting. 3. Replace "Alef" with the desired font family name. 4. Add this CSS code to the "Custom CSS" section found under "Appearance" > "Customizer" in your WordPress dashboard, or any other area where custom CSS is allowed.
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. If you still need help, please open a new support ticket.
Problem: You are experiencing issues with link translations on your Divi site, where links on the Japanese and English pages are incorrectly pointing to the Dutch pages. Solution: We recommend taking the following steps to resolve the issue: 1. Ensure you have a full backup of your website. 2. Delete all String Translations that originate from posts or pages, as these should not be used for link translations. You can do this by selecting the string and clicking on "Delete selected Strings". 3. Remove any unused pages from your site. 4. Publish or delete any draft pages. 5. Empty the trash can in all languages to ensure there are no residual files causing issues. 6. Carefully review your pages, posts, and Global Elements to verify that all links have the correct URLs. 7. Check your translations to ensure all information is accurate and correctly linked. After completing these steps, if the issue persists, it might be easier to identify the underlying cause. Please check our related known issues and confirm that you have the latest versions of themes and plugins installed. If the problem still exists, we highly recommend opening a new support ticket for further assistance. You can do so at our support forum.
Problem: The client is experiencing site crashes when attempting to complete translations. This issue has occurred previously and is suspected to be related to a plugin conflict, potentially with WordFence, as indicated by the error message from the file
. Solution: 1. Temporarily disable the WPEngine cache to check if it resolves the issue. 2. Put the website in maintenance mode and deactivate as many plugins as possible to identify if a specific plugin is causing the translation issue. Reactivate them one by one to pinpoint the problematic plugin. 3. Verify that WordFence is configured correctly as it is compatible with WPML. Consider trying another security plugin recommended by WPML if the issue persists. You can find a list of recommended security plugins here: https://wpml.org/plugin-functionality/security/.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 at WPML support forum.
Problem: The client is experiencing an issue where an extra menu appears briefly in mobile view during a speed test and then disappears. Solution: We recommend temporarily disabling optimization settings such as preloading, lazy loading, and deferred JavaScript execution in your optimization plugin to see if the issue persists. If the problem continues, disable all plugins except for WPML, String Translation, and Elementor, and test the site from a different browser or an incognito window. If this resolves the issue, reactivate the plugins one by one, testing after each activation to identify any conflicts with WPML.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 at WPML support forum for further assistance.
Problem: If you're experiencing issues with the WooCommerce shopping cart not adding more than 2 products or forgetting products when the WooCommerce Multilingual & Multicurrency plugin is enabled, this might be due to a plugin conflict. Solution: We recommend following the steps outlined in the WPML support forum to resolve this issue. You can find the detailed steps here: WPML support forum thread.
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 these steps not resolve your issue, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client is trying to translate a page from English to German using the WPML editor, but is encounter issues where some translations disappear after saving, and also cannot apply bold formatting or insert links in the translations. Solution: We recommend checking the following and it helps to resolve the issue: 1) Ensure that HTML formatting is correctly applied in your text translations. 2) Always click on the Complete Translation button before refreshing the page to save your translations effectively.
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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
, instead of the name of the layout, causing your code to break after translating your site with WPML, this might be due to missing custom fields in the translation. Solution: We recommend checking if the custom field settings were configured after the page was translated. If so, you can trigger the translation by modifying the original page, updating it, and then saving the translation again. This should ensure that
get_row_layout()
returns the correct layout names. Remember to update the page translations if there are other pages affected.
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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client needs assistance with setting up translation-related plugins after installing WPML and is looking for video tutorials and live chat support options. Solution: We recommend starting with our Getting Started Guide. Additionally, you can find helpful video tutorials on our YouTube channel at WPML video tutorials. If you prefer live chat support, please mark this ticket as resolved and then visit our support forum, select "Report a new issue." If there are available slots for live chat, you will be offered this option. If not, your request will automatically be converted into a support ticket. Please note that live chat has the highest availability from Monday to Friday during the European time zone, and availability may be reduced on weekends.
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. If you still need assistance, please open a new support ticket.
Problem: The client reported significant slowdowns on their staging site after installing WPML, with page load times increasing to 6-10 seconds. This issue was not present on a similarly configured site without WPML. The client tried various optimizations, including disabling WPML SEO and WPML String Translation modules, which improved load times.
Solution: We recommended migrating the site to our Cloudways testing environment to isolate the problem. The client used the Cloudways WordPress Migrator plugin for this purpose. After migration, we discovered that the combination of Admin Columns Pro, ACF, and ACFML plugins significantly impacted performance. We provided a temporary workaround by modifying the
translateField
method in the ACFML plugin to prevent certain processes from executing in the admin area, which improved backend performance. We also advised on general performance enhancements such as using PHP 8, enabling caching, and optimizing database indexes.
Please note that this solution might not be relevant if it's 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.
Problem: The client experienced a fatal error: 'Uncaught Error: Call to a member function get_language_codes() on bool' in the WPML String Translation plugin, which led to disabling the plugin to keep the website operational. Solution: We provided a custom search URL to help the client find existing support tickets related to the same issue: Google search for similar issues. If the client prefers live support, they should mark this ticket as resolved and then visit WPML support forum to report a new issue. Availability for live chat is higher from Monday to Friday in the European time zone.
If this solution is 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 using the Flatsome theme with WooCommerce, and you've added 'Top Content' and 'Bottom Content' using Flatsome UX Blocks on your product pages. These blocks display correctly in the default language but are missing on the translated pages. Solution: We manually inserted the UX Blocks for the translated product category pages. Please verify if the blocks now appear as expected on your translated pages. If the blocks are still not displaying correctly, this might be due to a configuration issue or a compatibility problem between the theme and WPML.
This solution might be outdated or not applicable to your specific case. 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.
Problem: You are working on a DIVI-based site with WPML in two languages (EN and FR). The global header is set through the DIVI theme builder, and the language flags are set through the widget '[wpml_language_selector_widget]'. On the mobile version of the site, the language flags are not clickable, although they work fine on the PC version. Solution: The issue is due to the z-index settings in your DIVI theme. The main row has a z-index of 3, while the columns have a lower z-index, causing the column with the language switcher to be positioned behind the row. To make the language flags clickable on mobile, assign a higher z-index (greater than 3) to the column that contains the language switcher from the Divi editor. Adjusting the CSS as highlighted can also make the language switcher clickable.
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 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 WPML support forum.
Problem: If you're experiencing issues where the post format and structure break after translating into a right-to-left (RTL) language, it might be due to missing CSS files in the RTL stylesheet. Solution: We recommend checking if your theme's RTL CSS file (style-rtl.css) includes all necessary CSS files. In a case we investigated, adding the following imports to the style-rtl.css resolved the issue:
Please ensure to back up your site before making these changes. Additionally, it would be beneficial to contact the theme author to include these CSS files in the theme's RTL stylesheet to prevent similar issues.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported an issue where the translation status incorrectly showed as pending, even though there were no pending translations. Solution: Initially, we suggested following the instructions in our guide to resolve issues where the translation process is stuck. This guide can be found here: https://wpml.org/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/ When the problem persisted, we identified that 25 translation jobs were stuck in the database with a status of '2' . We resolved this by executing the following SQL command to manually change their status to '9':
update
`icl_translation_status`
set status = 9
where status = 2
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/.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
