Problem: The client reported an issue where Widget Group titles were not displaying in the translated language on their multilingual site, despite the content within the Widget Group blocks being correctly translated. The REST API was initially reported as disabled by WPML but later appeared as enabled.
Solution: We resolved this issue in the latest version of WPML (4.9.0). To address this, we recommend updating to WPML 4.9.0 along with the latest versions of Strings Translation (3.5.0), Media Translation (3.1.0), and WCML (5.5.4). Here are the steps to update: 1. Navigate to Plugins → Add New Plugin in your site’s admin panel. 2. Click the Commercial tab. 3. Press the Check for updates button. 4. Select WPML 4.9 from the list and click Install. Please ensure to back up your site fully (both files and database) before proceeding with the update. More details about WPML 4.9.0 can be found here.
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: WPML Media Translation marked as 'Not Installed' on the Support page. Solution: We resolved this issue in the latest version of WPML (4.9.0). To address this, please follow these steps: 1. Go to your site’s admin area. 2. Navigate to Plugins → Add New Plugin and select the Commercial tab. 3. Click the 'Check for updates' button. 4. Find WPML 4.9 in the list and click 'Install'. Before proceeding, ensure you make a full site backup (files and DB). For more details on WPML 4.9.0, visit this link.
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: You've noticed that since the last update, an image that's translated in the Media Translation, when used on a page and then translated in the CTE, isn't translated anymore. Instead, the original image is served on the translated page. Solution: We've resolved this issue in the latest version of WPML (4.9.0). Please also update to the new versions of Strings Translation (3.5.0) and Media Translation (3.1.0). If you don't see these new versions on your site, follow these steps: 1. In your site’s admin, go to Plugins → Add New Plugin and click the Commercial tab. 2. Click the Check for updates button. 3. Select WPML 4.9 from the list and click Install. Before updating our plugins, we strongly recommend making a full site backup (files and DB). Learn more about WPML 4.9.0 in our post: WPML 4.9.0 Changelog
If this solution does not apply to your case because it might be outdated or not relevant, 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 issues persist, please open a new support ticket.
Problem: The client reported a fatal error related to Elementor's Global Widgets when WPML is active. The error message indicated a problem with calling a function on a null object within the Elementor Pro plugin. This issue was causing the client's website to break on specific pages. Solution: We resolved the issue by updating to the latest version of WPML (4.9.0) and the Strings Translation plugin (3.5.0). We advised the client to check for updates at your-domain.com/wp-admin/plugin-install.php?tab=commercial and click the 'Check for updates' button. It is crucial to make a full backup of the site before proceeding with the update.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 contact us directly at the WPML support forum.
Problem: WCML - Default Form Value is not selected if the attributes were created in the scondery language. Solution: We recommend updating to the latest version of WCML (5.5.4), along with WPML (4.9.0) and Strings Translation (3.5.0). Before updating, ensure to back up your site fully, including files and the database. You can check for updates by visiting your-domain.com/wp-admin/plugin-install.php?tab=commercialyour plugin installation page and clicking the 'Check for updates' button.
If this solution does not apply to your case because it might be outdated, or if you encounter further issues, 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. Please feel free to open a new support ticket with us for additional assistance.
Problem: You are unable to find the option to use DeepL as a translation service for the Spanish (Mexico) language variant. Solution: We recommend verifying the list of supported languages by DeepL and other translation engines here. For Mexican Spanish, you should use WPML’s Professional Translation Cloud (PTC), which is the default engine for WPML Automatic Translation and supports dialect-specific language variants, including Spanish (Mexico). Ensure that Automatic Translation is enabled and that WPML is set to use the PTC engine. If you need to translate content, you can either use the Advanced Translation Editor by clicking the plus icon or send the page for automatic translation via WPML → Translation Dashboard. Select the page, choose the target language, and send it for automatic translation.
If this solution does not apply to your case, 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: In Elementor, on a multilingual site, the padding at the bottom section of the page appears to be double in the secondary language compared to the primary language. This issue does not affect other sections of the page. Solution: We suspect that this might be a caching issue. We recommend clearing all types of cache on your site to see if this resolves the problem. If you're experiencing this issue, try clearing your browser cache, server cache, and any other caching mechanisms that might be affecting the display of your pages.
If the solution provided here is outdated or does not apply 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: If you're experiencing issues with the styling of your custom language switcher, specifically with the "Hover" settings for "Other language font color" and "Other language background color" not working as expected on the frontend, this might be due to a CSS conflict or misconfiguration. The hover effect might be incorrectly applied to the current language instead of the available translation links. Solution: We recommend applying custom CSS to correct this issue. You can add the necessary CSS by navigating to WP > Appearance > Customize > Additional CSS in your WordPress dashboard.
.wpml-ls-statics-shortcode_actions a, .wpml-ls-statics-shortcode_actions .wpml-ls-sub-menu a, .wpml-ls-statics-shortcode_actions .wpml-ls-sub-menu a:link, .wpml-ls-statics-shortcode_actions li:not(.wpml-ls-current-language) .wpml-ls-link, .wpml-ls-statics-shortcode_actions li:not(.wpml-ls-current-language) .wpml-ls-link:link {
color: #000000;
background-color: #ffb536;
}
If this solution does not resolve your issue or seems irrelevant because it 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 at WPML support forum for further assistance.
Problem: The client reported that their website is very slow, affecting page loading and saving times. They have already increased memory allocation in the config file to 512M, deactivated all plugins except WPML, updated all software, cleared cache, and disabled unnecessary WPML features, but the issue persists. Solution: We asked the client to check if the website's performance has improved after running the "Database Tables Optimization" troubleshooting step, which fixed the issue.
If this solution does not apply or is outdated, or if the problem persists, 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: The client manually translated content in WPML Editor. Dropdowns are visible in the Admin area, but on the live site, clicking the dropdown shows only the current language with a 'Down-Arrow' and no further action occurs. Additionally, clicking on elements in the Footer also shows no response. Solution: For the issue with the navigation link leading to the incorrect language version of the 'Blog', it can be adjusted in Kadence → Navigations. Here are the steps to correct it: 1. Choose the correct language. 2. Edit the navigation. 3. Add the correct link for the blog. For adding a Spanish header, follow these steps: 1. Translate the navigation to Spanish. (Note: The translation editor was disabled, and it seems it was done with the WordPress editor.) 2. Translate the header to Spanish. 3. Assign it in Appearance → Editor and then Patterns → Header.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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 an issue where you, as a translation admin, are unable to translate an element because the dropdown search returns no item for your username, Solution: We recommend using the following workaround: https://wpml.org/errata/cannot-add-translation-manager-in-some-scenarios/
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, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported losing all content created with Bricks PageBuilder and encountering issues with endpoints switching to English and adding unwanted suffixes in a multilingual WooCommerce setup. The default language was set to Dutch, but endpoints were incorrectly resetting. Solution: We advised the client to perform a full backup and provided assistance by resetting the WordPress endpoints to their original state and ensuring the default language remained in Dutch. We also recommended translating the endpoints back to the required languages using the String Translation feature of WPML. To address the issue with the URLs, we suggested keeping the English endpoints on the WooCommerce settings page and translating them as needed. We also resolved an issue where the Dutch default was missing the '/nl' URL part by reactivating the directory option for URLs.
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: The client reported two issues: firstly, the English flag button was not redirecting to the English version of the site but instead was redirecting back to the Italian homepage. Secondly, the site encountered a critical error upon refreshing, which only occurred when WPML plugins were active. Solution: We first addressed the redirection issue by identifying that some English pages were not correctly linked as translations of the Italian pages. We recommended deleting unnecessary English pages and correctly linking the remaining ones to their respective Italian versions. For the critical error, we suggested updating all themes and plugins to their latest versions to rule out conflicts with outdated software. After updates, we performed additional fixes to the database, which resolved the issues.
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 is experiencing issues with translating 'before' and 'after' strings of dynamic components in Elementor using custom XML. The provided XML did not function as expected. Solution: We recommend using the Multilingual Tools plugin to automatically generate the correct XML configuration for Elementor's dynamic tags. Here's a step-by-step guide: 1. Download and Install Multilingual Tools: Visit the OnTheGoSystems GitHub page, download the plugin, and install it on your WordPress site. 2. Prepare Your Elementor Page: Ensure the 'before' and 'after' strings are filled in the Elementor editor and the page is updated. 3. Generate the Custom XML: On the WordPress edit screen, find the 'WPML: Elementor Widgets' section to copy the automatically generated XML. 4. Apply the Generated XML: Paste this XML in the 'Custom XML Configuration' tab under 'WPML → Settings' and save. 5. Update and Translate: Make a minor edit to the page and use the WPML Advanced Translation Editor to translate the newly available strings.
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. If problems persist, please open a new support ticket.
Problem: In the Slovenian translation, when navigating to certain product categories, all product links and menu links lose the language name parameter (/?lang=sl). Deleting and recreating the translated product category did not resolve the issue. Solution: We recommend using WPML → Taxonomy Translation for translating taxonomies. If Yoast displays a warning about creating a redirect when editing a translated term, you can click “Undo” to remove the redirect. If a redirect has already been created, you can manually remove it from Yoast → Redirects.
Option 1: No changes to Yoast Premium (recommended) Add the following snippet to your functions.php file:
add_filter( 'Yoast\\WP\\SEO\\term_redirect_slug_change', function( $create_redirect ) {
// Only act in admin term edit contexts.
if ( ! is_admin() ) {
return $create_redirect;
}
$taxonomy = $_POST['taxonomy'] ?? '';
if ( ! $taxonomy || ! taxonomy_exists( $taxonomy ) ) {
return $create_redirect; // not editing a taxonomy term
}
if ( class_exists('Sitepress') ) {
$current_lang = apply_filters( 'wpml_current_language', null );
$default_lang = apply_filters( 'wpml_default_language', null );
if ( $current_lang !== $default_lang ) {
return true; // prevent Yoast redirect creation
}
}
return $create_redirect;
}, 10 );
This prevents Yoast from automatically creating redirects for taxonomy terms in secondary languages.
Option 2: Modify Yoast Premium code This involves editing core plugin files and is not recommended due to potential issues with future updates.
We plan to notify Yoast about this behavior. However, if this solution does not apply to your case or 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. If the issue 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
