Available Solutions

To perform forum search or open new support ticket Go to the support page

Topic	Voices	Posts	Freshness
Elementor Header footer broken after installing WPML plugin 1 2 Started by: gerardR-3 in: English Support Quick solution available Problem: The client experienced a noticeable slowdown and layout issues with Elementor after installing WPML. Elements such as headers and footers disappeared or appeared broken, and styles like text colors were affected. The issues were resolved upon deactivating WPML. Solution: We initially suggested a WPML reset and reinstallation, which did not resolve the issue. After further investigation, we identified the problem was related to the PHP settings on the hosting environment, specifically the pcre.backtrack_limit configuration. We applied a workaround by adding the following code to the wp-config.php file: ini_set("pcre.backtrack_limit", 10000000); ini_set("pcre.jit", 1); This code increases the pcre.backtrack_limit and enables pcre.jit , which resolved the issue. More information about pcre.backtrack_limit can be found here. Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, we highly recommend checking related known issues at WPML 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 in the WPML support forum.	2	18	1 year, 4 months ago Long Nguyen
Split: When using Advanced Translation Editor I am getting 404 error when translating page Started by: janneR-5 in: English Support Quick solution available Problem: The client is experiencing a 404 error when trying to use the Advanced Translation Editor with BeTheme, even though the documentation states that the theme is fully compatible with WPML. Solution: We recommend the following steps to resolve the issue: 1. Verify that the Site URL and WordPress URL in "Settings > General" match the actual domain you see in the browser's URL bar. If these fields are not editable, update the URL from the database or by following this article. 2. Ensure that the REST API is enabled on your site, as it is necessary for WPML's API to function correctly. If your site is in Maintenance mode, please disable it before proceeding. 3. If the 404 error persists, contact your hosting provider to check if the REST API access to your site is blocked. If so, request them to unblock it and then clear the caches from your site and browser before trying again. If these steps do not resolve the issue or if the solution 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. Should you need further assistance, please do not hesitate to open a new support ticket in our support forum.	2	9	1 year, 4 months ago Prosenjit Barman
Split: Issues with the slider Started by: anikaN-2 in: English Support Quick solution available Problem: The client was experiencing an issue where the "Image Slider Block" plugin stopped working on the English section of their hotel categories (Europe, Asia, Middle East). The images were not displayed as a slider but just in a row underneath each other. The problem was only present in the English version, while the German version worked fine. Solution: First, we identified that the issue was related to the HTML structure of the block, where the data settings value was being HTML encoded and then decoded incorrectly after translation with WPML's translation editor. We initially suggested translating the page using the WordPress editor and adding the slider manually on the translation page, following the documentation at https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/. Later, we resolved the issue on the Europe hotel page by removing the problematic block and adding the following custom XML code to WPML > Settings > Custom XML Configuration tab, to exclude the "Image Slider Block" content from translation: <wpml-config> <gutenberg-blocks> <gutenberg-block type="slider-block/slider-block" translate="0"> </gutenberg-block> </gutenberg-blocks> </wpml-config> This allowed the client to translate the Europe hotel page with the Advanced Translation Editor as well. For more information, refer to the documentation at https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/. Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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. If the problem persists, please open a new support ticket with us.	2	4	1 year, 4 months ago Long Nguyen
Products reviews get deleted after adding new language and duplicating product to it Started by: sebastiaanV-11 in: English Support Quick solution available Problem: The client reported that each time they duplicated a single product to another language for manual translation, all product reviews were deleted. Solution: We recommended two workarounds: 1. Navigate to WooCommerce > WooCommerce Multilingual & Multicurrency > Settings and disable the option "By default, show reviews in all languages". 2. Alternatively, edit the file wp-content/plugins/woocommerce-multilingual/inc/class-wcml-comments.php . Around line 209, replace the code if ( $this->is_reviews_in_all_languages( $obj->query_vars['post_id'] ) ) { with the following code if ( $this->is_reviews_in_all_languages( $obj->query_vars['post_id'] ) && !isset( $_REQUEST["action"] ) ) { We emphasized the importance of backing up the database and website before making any changes. If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.	3	11	1 year, 4 months ago Long Nguyen
Salient theme – Nectar slider: Internal links not pointing to translated content Started by: bradC-7 in: English Support Quick solution available Problem: The client was experiencing an issue where the URLs in the Nectar Slider were not being translated correctly and were always pointing back to the English version. Solution: We provided a workaround to address the issue with the Nectar Slider post type. Before proceeding, we emphasized the importance of backing up the database and website. 1. Edit the file /wp-content/plugins/salient-nectar-slider/includes/frontend/helpers.php 2. Around line 814, replace the existing code for button 1 URL with the following custom code: if ( ! empty( $button_1_text ) ) { // WPML Workaround for compsupp-7240 if (class_exists('Sitepress') && ! empty( $button_1_link ) ) { $current_lang = apply_filters( 'wpml_current_language', NULL ); $button_1_link = apply_filters( 'wpml_permalink', $button_1_link, $current_lang, true ); } $button_1_link = ! empty( $button_1_link ) ? $button_1_link : '#'; } 3. Apply the same workaround for button 2 URL around line 845 with similar custom code. 4. After creating and translating a Nectar Slider post, edit a page, add the Nectar Slider element, select the slider location, save, and translate the page. The internal URL will then be adjusted in the frontend. Please note that this solution might be outdated or not applicable to your case. If it doesn't resolve your issue, 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.	2	9	1 year, 4 months ago Long Nguyen
Can't translate generateblocks dynamic text Started by: robinB-8 in: English Support Quick solution available Problem: Client was unable to find the "Last update" string in the string translation to translate it to Vietnamese. This string is from "dynamic text" from the generateblocks plugin. Solution: We provided an XML code to include the texts for translation. We instructed the client to navigate to WPML -> Settings -> Custom XML Configuration and add the following code: <wpml-config> <gutenberg-blocks> <gutenberg-block type="generateblocks/headline" translate="1"> <key name="gpDynamicTextBefore"></key> <key name="gpDynamicUpdatedDateBefore"></key> </gutenberg-block> </gutenberg-blocks> </wpml-config> After adding the code, the client should make a minor modification to the element containing the 'Last Update:' text, save it, and update its translation. The texts will then be available for translation and should be visible on the front end. If you're experiencing this issue, we recommend you try the provided solution. However, 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 problem persists, please open a new support ticket with us.	2	9	1 year, 4 months ago Mateus Getulio
English/Norwegian Languages Started by: astridG-6 in: English Support Quick solution available Problem: The client is translating their site into Norwegian using WPML and wishes to make Norwegian the default language. They are seeking best practices for adding or changing content using Divi / Visual Builder, and whether they should always add content in English first. Additionally, they encountered issues with links directing to the wrong language pages and needed guidance on how to proceed. Solution: 1. It is acceptable to set Norwegian as the main language at the end of the translation process. However, it is generally recommended to set the final default language from the beginning. Before changing the default language, always ensure to back up the website fully. 2. When making changes to the website, it is best to use the same editor that was used initially. If manual translation was used with Divi Builder, continue using Divi Builder for both languages. If automatic translation with the Automatic Translation Editor (ATE) was used, continue using ATE for translations and Divi Builder only for the main/default language. More information on the manual translation method can be found in our documentation: Using Different Translation Editors for Different Pages. 3. For the specific issues with links directing to the wrong language pages, we ask the client to open a new support ticket for each issue to allow our team to focus and investigate each problem individually. Please note that the solution provided might be outdated or not applicable to your case. If the solution does not resolve your issue, we highly recommend checking related known issues at WPML 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 in the WPML support forum.	2	6	1 year, 4 months ago Mihai Apetrei
Bug within filter made with WPML/ACF and WP grid builder Started by: athinaK-2 in: English Support Quick solution available Problem: The client is experiencing an issue with a grid built using WP Grid Builder and ACF on their website. A taxonomy term labeled 'optional', which is a Translation Priority taxonomy term, is showing up under the title of each accommodation post type. Solution: We recommend customizing the Gridbuilder query to exclude the 'optional' taxonomy term from displaying on the frontend. This involves adjusting the query to only include the selected taxonomy terms that the client wishes to show. Please note that the solution provided might be irrelevant if it's outdated or not applicable to the client's specific case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the issue persists, the client should not hesitate to open a new support ticket for personalized assistance. Here is the link to the WPML support forum.	2	5	1 year, 4 months ago Noman
Logo image does not adapt to English site Started by: Rosevita Warda in: English Support Quick solution available Problem: The client's multilingual website was not displaying the correct logo for the English version when using the X-Theme. Solution: 1. We identified the media ID of the current logo image (ID: 19663). 2. We navigated to WPML > String Translation and used the 'Translate texts in admin screens' option at the bottom of the page. 3. We searched for the logo's ID number, checked the box on the left, and selected "Add to String Translation". 4. Once the string was added to the list, we clicked the "+" icon to add a translation for the English language. 5. We entered the media ID of the English logo (ID: 16028) and appended ":full" to specify the image size as required by the theme. If you're experiencing a similar issue with your logo not switching for different languages, we recommend following these steps to add the correct logo to the String Translation and specify the appropriate media ID for each language. 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.	2	9	1 year, 4 months ago Mihai Apetrei
Internal server error 500 Started by: jureD-3 in: English Support Quick solution available Problem: The client's website encounters an Internal Server Error 500 when trying to access different pages from the menu in the English version. Solution: We recommend taking the following steps to resolve the issue: 1. Ensure you have a backup of your site. 2. Add the following code to the functions.php file of your theme: add_filter('mod_rewrite_rules', 'fix_rewritebase'); function fix_rewritebase($rules){ $home_root = parse_url(home_url()); if ( isset( $home_root['path'] ) ) { $home_root = trailingslashit($home_root['path']); } else { $home_root = '/'; } $wpml_root = parse_url(get_option('home')); if ( isset( $wpml_root['path'] ) ) { $wpml_root = trailingslashit($wpml_root['path']); } else { $wpml_root = '/'; } $rules = str_replace("RewriteBase $home_root", "RewriteBase $wpml_root", $rules); $rules = str_replace("RewriteRule . $home_root", "RewriteRule . $wpml_root", $rules); return $rules; } 3. Re-save the permalinks from the Settings >> Permalinks page by pressing the Save Changes button. 4. Clear all types of caches including site/server cache, plugin cache, CDN cache, and browser cache. For more details, please refer to our documentation: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/ If the solution provided here is not relevant due to being outdated or not applicable to your case, 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. If further assistance is needed, please contact us in the WPML support forum.	2	2	1 year, 4 months ago Noman
problems with credits Started by: benK-12 in: English Support Quick solution available Problem: The client was unable to use their purchased automatic translation credits for translating content from Dutch to English, despite having all plugins updated. They received a message prompting them to 'Get more credits' even though they had bought 104,000 credits. Solution: We discovered that the credits were associated with a different automatic translation account, likely due to a reinstallation or reset of WPML or WordPress. We reassigned the credits to the client's current account. To verify the credits, we advised the client to navigate to WPML > Translation Management > Tools and check the top-left area of the backend of their site. If you're experiencing a similar issue with your automatic translation credits, we recommend checking your WPML account to ensure the credits are properly assigned. If the problem persists, please visit our known issues page (https://wpml.org/known-issues/) and confirm that you have the latest versions of themes and plugins installed. If the solution provided here is outdated or not applicable to your case, we encourage you to open a new support ticket for personalized assistance. You can do so by visiting the WPML support forum.	2	3	1 year, 4 months ago Mihai Apetrei
Translations show up in site default language Started by: erenK in: English Support Quick solution available Problem: The client imported languages to a new site using WPML but encountered an issue where updating content in English caused all pages to display in English, despite having translations in other languages. Solution: We identified that the German content for the "Hair Transplant" page was showing up in English. This was because the translation in the WPML Translation Editor was incomplete, showing 0% completion. To resolve this, the client needs to complete the translation to 100% in the WPML Translation Editor for the changes to be reflected on the front end. Additionally, we noted that importing content from one site to another does not include the translation memory from the Advanced Translation Editor. The translation memory is stored within the WPML account and does not migrate with the WPML Export & Import feature. If the client wishes to merge the translation memories from multiple sites, we provided a link to the relevant documentation: https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/ Please be aware that this solution might not apply to your case if it's outdated or not relevant to your specific situation. If this is the case, 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. If further assistance is needed, please contact us through the WPML support forum.	2	8	1 year, 4 months ago Andreas W.
Add 1 more license Started by: sergueiM in: English Support Quick solution available Problem: The client is using WPML on one website and wants to obtain another license for a second website. Solution: We explained that the client is currently using an End-user (one-site) license, which is limited to one site and cannot be transferred or changed. To register more sites, the client needs to purchase an additional license. We provided two steps: 1. Visit the Transferring account renewals to your clients page for more information. 2. Purchase a new license from the WPML purchase page. If the system does not allow purchasing from the same account, the client should create a new WPML account. We also mentioned that if this solution is not relevant due to being outdated or not applicable to the client's case, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the issue persists, the client should open a new support ticket. For further assistance, visit the WPML support forum.	2	2	1 year, 4 months ago Mihai Apetrei
missing product category to translate Started by: nataliaD in: English Support Quick solution available Problem: The client was unable to find one specific product category ('Bags') in the list for translation using WPML. Solution: We recommended the client to first make a full backup of their site. Then, navigate to WPML -> Support -> Troubleshooting. Once there, the client should click on the items listed in the provided screenshot to sync the products term count. This action might help in making the missing category appear for translation. If this solution does not apply to your situation, or if it's outdated, we suggest opening 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.	2	3	1 year, 4 months ago Mateus Getulio
Mobile is not showing in english version Started by: CaghanY in: English Support Quick solution available Problem: The client is experiencing an issue where the mobile menu is not displaying on the English version of their site, which is the default language. The English homepage is using a different header template ("Header 1 en") than the one set in the theme options ("Header 1 – Transparent Black - English"), and the "Header 1 en" template does not include a mobile menu. Solution: We recommend checking the header templates in use. The English homepage should use the "Header 1 – Transparent Black - English" template that includes the mobile menu. If the site is using "Header 1 en" instead, adjusting the template to include a mobile menu may resolve the issue. Additionally, since the client is using Elementor, we advise installing the WPML String Translation add-on, which is not included in the WPML Blog subscription. It is also important to update all outdated plugins to ensure compatibility and functionality. Please note that the solution provided 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.	2	9	1 year, 4 months ago Andreas W.

This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive