You are unable to finalize translations using the advanced editor, and the translation progress shows only 96% completion.
Solution:
First, ensure that you publish the translation if it is still in the review state. If the issue persists, follow these steps:
1) Open the Page for editing in the default language. 2) Make a minor change and update the Page to refresh the translation settings. 3) Go to WPML>>Translation Management Dashboard. 4) Select the Page you want to translate or update the existing translations. 5) Send it to the Translation Basket. 6) Navigate to WPML>>Translation Management>>Translation Basket. 7) Assign yourself as the translator and send it for translation. 8) Go to WPML>>Translations queue and translate the Page by clicking the Translate button.
If this solution does not resolve your issue, or if it 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client's website has a layout that should display in Italian for the Italian version of the site, but it was showing in English instead. Solution: We identified that this issue had occurred previously with another user and was related to the Woodmart theme. We recommend checking the following forum post for a similar issue: https://wpml.org/forums/topic/issue-with-layout-pages-translation-status-stuck-in-progress/. We applied a workaround by manually translating the layout, which resolved the problem.
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: You are using WPML to translate your products into 26 languages, resulting in 7500 products in your WordPress admin. However, only 750 product URLs are indexed by Google, and the XML sitemap does not contain more than 6500 product links. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Ensure all products are published. 2. Verify that all plugins and themes are up-to-date. 3. Install WPML SEO if it is not already installed. 4. Re-send the sitemap for indexing in the Google Search Console. Additionally, please provide the debug information of your site as described here: https://wpml.org/faq/provide-debug-information-faster-support/
Please note that this solution might be irrelevant if it is 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: You have added a new product and its translation in WooCommerce using WPML. Although the translation shows a 100% completion status and appears in the translation queue, it does not display on the webshop. This issue started after enabling WP Rocket Premium. Solution: We have applied a troubleshooting fix to your site, which now allows the translated products to display correctly in the webshop. Products that show a "pencil" icon are fully translated and should now be visible.
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. Additionally, please check the related known issues and ensure you have the latest versions of themes and plugins installed. For further assistance, you can also visit our support forum.
Problem: The client was unable to register their WordPress multisite site with a new production URL and remove the WPML development banner after changing the site URL. Solution: We resolved the issue by registering the site with the same site key, which removed the WPML development banner from the live site. If you're experiencing similar issues, we recommend checking if the site is correctly registered with the WPML plugin and that the site key is correctly applied.
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 problem persists, please open a new support ticket.
Problem: You are experiencing an issue where the WPML plugin cannot connect to wpml.org, which is necessary for checking new releases and security updates. The error suggests that network or security settings might be preventing this connection. Solution: If you're facing this problem, we recommend checking if it's a false positive caused by server caching. You can verify this by navigating to Plugins > Add New > Commercial in your WordPress dashboard, and clicking the Check for Updates button. If after refreshing the page, WPML still shows as registered, then the issue is likely just a false positive. This means that WPML is functioning correctly despite the error message, and the notification should disappear once the cache clears.
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 open a new support ticket at WPML support forum.
Problem: The client has a large multilingual site with posts in English and Spanish, consolidated from four older sites. They are facing issues with hardcoded links in Spanish content not correctly reflecting the new site structure. Solution: We recommend updating the hardcoded links via the database (DB). This approach will not affect the page content as these links are embedded in post meta. Therefore, updating them directly in the DB or by re-translating the pages and the links within them is necessary. For dynamic links, such as menu items, these should adjust automatically when you modify your WPML language settings.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket here.
Problem: The client added a WPML language switcher to their site, but changing the language was breaking the page design.
Solution: We identified that the issue was due to certain fields in the 'Page settings' section not being copied to the translations when editing the page in the default WP editor. We changed the configuration of the following fields in WPML -> Settings -> Custom Fields Translation to 'Copy' instead of 'Don't translate':
content_type
_header_disable
_title_disable
To resolve the issue, follow these steps: 1. Open the page or post in the default language for editing. 2. Make a small change, such as adding a word or dot. 3. Save the changes. 4. Update the translation. 5. Ensure that any Elementor template used on this page or post is also translated and published.
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.
Problem: The client reported that variable products translated into Spanish using WPML were showing as out of stock, despite previous solutions that involved updating products in the original language and then re-saving them after minor edits.
Solution: We recommended the following steps to address the issue: 1. Navigate to WooCommerce > WooCommerce Multilingual > Attributes tab. 2. Select the attribute from which the variations were created. 3. Click the button at the bottom to synchronize the attributes. 4. Go to the Status tab and click on Troubleshooting. 5. Select the options shown in this screenshot (https://prnt.sc/oKKMHMZPhIWT) and start the synchronization. 6. If the '_stock' field is set to 'not translatable' in WPML → Settings → Custom Fields Translation, change it to 'Copy'. 7. Clear site and browser caches.
If these steps do not resolve the issue, we suggested a deeper investigation which might require temporary admin access to the site for further troubleshooting.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to display translated regions, countries, and ports on their website using the Elementor Custom HTML widget. Solution: We recommended using the wpml_object_id filter hook to fetch translated post IDs in the current language. Detailed guidance on this hook is available at WPML documentation. For Ajax-loaded data, we advised passing the current language to the callback function. Instructions for handling Ajax requests can be found at WPML documentation. Additionally, we provided custom code examples to localize scripts and modify Ajax requests to ensure the correct language is used:
// Get the current WPML language
$current_language = apply_filters( 'wpml_current_language', null );
// Localize the script with the current language
wp_localize_script( 'common-js', 'wpmlData', array(
'currentLanguage' => $current_language,
));
lang: wpmlData.currentLanguage
These changes were implemented on the client's staging site. If further customization is needed, we recommended contacting a certified WPML contractor from this list.
Please note that the solution provided 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, please open a new support ticket.
Problem: You are working on a site under development and trying to translate the employer dashboard page using WPML. Additionally, you need help with editing footer translations, which aren't handled by the string editor. When attempting to translate the employer dashboard page, the entire content disappears. Solution: For a long-term solution and to prevent fixing issues one by one, we recommend contacting the plugin author and asking them to join our Go Global program. This program helps plugin authors make their products compatible with WPML, ensuring smoother translations across 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 open a new support ticket at WPML support forum.
Problem: You are trying to translate products using WPML, but instead of the pencil symbol for editing translations, you see a wheel symbol that persists for hours, indicating that the translation process is not completing. Solution: 1. Check for errors by navigating to WPML > Support > Advanced Translation Editor > Error Log. If there are any errors, copy them and share via a site like pastebin.com, then provide the link to us. 2. Consider if the issue occurs only with one specific language, which might help isolate the problem. 3. Assess if the slowdown could be due to a high number of plugins or custom blocks on your pages. 4. Note that very new PHP versions might not be fully supported by WPML or WordPress yet. Testing changes in a local or staging environment is recommended to avoid impacting your live site.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to remove websites from your list in WPML, specifically temporary websites, but cannot find any documentation on how to proceed. Solution: First, check if the websites have already been removed from your WPML account. You can do this by visiting http://wpml.org/account/sites. If the websites are still listed there and you wish to remove them, please follow the steps provided on that page.
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 WPML Support Forum.
Problem: The client is experiencing deprecated function warnings in their error logs after updating plugins. These warnings are related to the WPML CMS Navigation and Sticky Links plugins and appear due to the use of PHP version 8.2.7, which is not fully compatible with WPML or WordPress yet. Solution: We recommend disabling the debug mode in WordPress to prevent these warnings from being displayed to visitors. This can be done by editing the
wp-config.php
file and ensuring it contains the following line:
define('WP_DEBUG_DISPLAY', false);
For more information on compatibility and this issue, please visit the official WordPress site: WordPress 5.9 and PHP 8.0-8.1. These notices are expected to be resolved in future updates of the plugins.
If this solution does not apply to your case, or if the problem 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client wants the domain mamija24.pl to load in Polish and has set it as an alias of mamija.lt in the hosting settings. Despite setting up a multi-domain SSL certificate and configuring WPML for the Polish language on mamija24.pl, the client experiences a redirect to mamija.lt. Solution: We recommend verifying the domain setup to ensure that mamija24.pl displays the same content as mamija.lt without redirection. This setup is crucial for the domains to function correctly under WPML with different languages per domain. You can find detailed guidance on configuring domains with WPML here: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/. If you are unsure about these settings, contacting your hosting or domain provider for assistance is advisable, as we cannot access your domain settings directly.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. For further assistance, you can contact us through the WPML support forum here: 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
