Problem: You want to translate the cookie consent message using WPML but are unable to find the string in the default language settings. Solution: 1. Navigate to Appearance > Customize and make a small change to the cookie content. 2. Go to WPML > String Translation and click on "Translate texts in admin area". 3. Search for the cookie content and add it to String Translation. Note that if you are using a child theme, the string domain will differ, in this case, it is "admin_texts_theme_mods_lmx". 4. Return to String Translation and change the source language of the string to Bulgarian, as the default source language of options is English. 5. Translate the string. For more detailed guidance, check the following documentation:
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, ensure you have the latest versions of themes and plugins installed, and check related known issues at https://wpml.org/known-issues/. For further assistance, please visit our support forum.
Problem: You have set up WPML and translated a page, but the translated German page appears empty. Solution: First, ensure that you have completely translated the page. If the issue persists, we recommend enabling the debug mode to identify any underlying issues. Here’s how you can enable it: 1. Open your
wp-config.php
file. 2. Locate the line
define('WP_DEBUG', false);
and change it to:
define('WP_DEBUG', true);
3. To log the errors to a file, add:
define('WP_DEBUG_LOG', true);
This will save the errors to a debug.log file inside the /wp-content/ directory. For more detailed instructions, visit https://wpml.org/documentation/support/debugging-wpml/. After enabling debug mode, check the debug.log to see what might be causing the page to be empty.
The issue was solved by deactivating the non-WPML plugins to find out what plugin caused the problem.
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 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 directly at the WPML support forum.
Problem: The client needed to modify the hreflang links for dynamic pages that exist only in the main language (FR) and wanted to know if there is a hook to filter or remove these links. Solution: We recommended using the
wpml_hreflangs
hook to change or remove the alternate hreflang links. We provided examples of how to implement this filter with links to relevant documentation:
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, you can contact us directly at WPML support forum.
Problem: The client was experiencing an issue where translated post categories were displaying incorrectly on the latest post on their blog. They attempted to use a previous troubleshooting solution that had worked before, but it was unsuccessful this time. Solution: We initially suggested revisiting the troubleshooting steps from a previous ticket. The client tried the suggested solution again, and after a day, it resolved the issue, and the categories displayed correctly. Therefore, no further action was required, and the ticket was closed.
If you're experiencing a similar issue, we recommend revisiting previous troubleshooting steps that may have worked before. It's important to 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 at WPML support forum for further assistance.
Problem: The client is trying to edit custom CSS for a page in English using the Divi Page Builder, but the changes are not being saved after exiting the builder. WPML does not recognize these CSS strings. Solution: First, ensure that you are editing the page in English directly using the Divi Page Builder and save the changes by clicking the green button in the widget editor. After saving, clear your website's cache, including server-side cache, to see if the translations appear correctly.
If the issue persists, check the WPML settings for custom fields. Go to WPML->Settings->Custom Fields, enable "Show 'Multilingual Content Setup' meta box on post edit screen." Then, in the post editor, scroll to the bottom and click to show hidden system fields. Look for the CSS field, which might be set to 'copy' by default. If found, change its setting to 'copy once' or 'translate'.
If the CSS field is locked (as indicated by a lock icon), it might be restricted by the theme developers. In such a case, go back to WPML->Settings->Custom Fields, search for the CSS field, unlock it by clicking on the lock icon, and set it to 'copy once'. This adjustment should allow you to manually edit the CSS.
If these steps do not resolve your issue, or if the solution becomes outdated, 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client reported a redirect issue with image attachments when WPML is enabled, which was negatively impacting SEO. The issue was isolated to WPML after disabling all other plugins. Solution: We analyzed the situation and found that the redirects were due to the way WPML handles media translations. Each translated media item gets a new URL, and when the language prefix is not present in the URL, WordPress redirects to the correct URL. This behavior is expected and is managed by WordPress's default redirection mechanism. To address the client's concern about SEO and ensure proper URL handling, we recommended enabling the "Redirect Attachment URLs to Attachment Parent" feature in the All in One SEO plugin. This setting redirects attachment URLs to the parent post URL, which is the default WordPress behavior.
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 the problem persists, please open a new support ticket.
Problem: The client experienced an issue where 40,000+ duplicate images were created due to a hiccup, and after removing unused media, including media from translations, all media on translated pages went missing. The client is looking for a way to 'recycle' or 'retranslate' the media so that it works on the translated pages as it does on the non-translated pages. Solution: We recommend the following steps to address the issue: 1. If you have a backup from before these database changes were made, utilize it to restore the missing entries. 2. If no backup is available, follow these steps:
1. Create a full website backup.<br />2. Complete all translations marked as "update needed" in the Translation Editor by clicking "Complete." This will restore the missing images.<br />3. For pages/products created in secondary languages, manually restore the images in the page editor.
We always advise having a backup before making any changes to prevent such issues.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported significant slow performance with the WPML plugin activated, particularly when the String Translation plugin is enabled. The issue persisted despite switching themes and disabling third-party plugins. Profiling indicated that the slowdown was related to the ACF Multilingual plugin, specifically with the handling of WYSIWYG fields in custom post types (CPTs). Solution: We identified a specific code snippet causing the issue in the ACF Multilingual plugin. We recommended modifying the code in the
This change prevents unnecessary processing unless the field contains a link, which should mitigate the performance issue. We are also working on a more permanent solution to be included in future WPML releases.
If this solution does not resolve your issue, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at WPML support forum.
Problem: You are experiencing an issue with the multi-currency option in WooCommerce when using the Variation Swatches Pro plugin. The currency conversion works correctly for the main product prices, but when changing an attribute variant that affects the price (e.g., color), the additional cost is not converted correctly and adds the same numeric value in a different currency. Solution: Step 1: Verify Plugin Compatibility Ensure that you are using the latest versions of both WPML, WooCommerce, and the Variation Swatches Pro plugin. Compatibility issues often arise from outdated versions. Step 2: Check WPML Multicurrency Settings 1. Go to WPML > WooCommerce Multilingual & Multicurrency > Multicurrency. 2. Ensure that the conversion rates are set correctly for all currencies. 3. Verify that the settings for rounding and display are appropriate for your needs. Step 3: Verify Attribute Pricing 1. Go to Products > Attributes in the WordPress admin panel. 2. Ensure that the attribute prices are set correctly in the primary currency (PLN). Step 4: Custom Code Adjustment Sometimes, custom code is required to ensure compatibility between different plugins. You might need to add a custom filter to handle the price conversion for attribute variants correctly. Here is an example code snippet that you can add to your theme's `functions.php` file:
Step 5: Contact Plugin Support Since "Variation Swatches Pro" is not listed in our directory of compatible plugins, we recommend reaching out to their support team. They may have specific solutions or patches for this known issue.
If this solution does not resolve your issue or seems irrelevant, 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 at WPML support forum.
Problem: The client reported that the language switcher in the menu was not displaying language options on all pages except the default English page. Solution: This issue was linked to DNS settings affected by Cloudflare, which interfered with WPML's functionality.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client's website uses Romanian as the default language and English as the secondary language. They are experiencing an issue where, after using the language switcher, the button in the main menu changes its name correctly from Romanian to English, but the link still opens the page in Romanian instead of English. Solution: We recommend the following steps to address this issue: 1. Ensure you have a full backup of your website. 2. Navigate to WPML > Settings and click on Translate Link Targets. Test the button to see if the issue is resolved. 3. If the problem persists, go to WPML > String Translation and search for the specific part of the link (e.g., "charmhotel.ro/rezervari") and translate it. Additionally, please provide your debug information to help us better understand your website settings. You can find instructions on how to do this here: https://wpml.org/faq/provide-debug-information-faster-support/
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 want to translate a single page automatically using WPML and are unsure how to proceed. Solution: To translate a page automatically, follow these steps: 1. Navigate to WPML-> Translation Management. 2. Select the page you wish to translate. 3. Choose Automatic Translation. 4. Send the page to the translation. Additionally, we recommend that you provide your Debug information to help us better understand your site configuration. You can find detailed instructions on how to do this here.
If this solution does not apply to your case, or if it seems outdated, please check the 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. Should you need further assistance, feel free to open a new support ticket here.
Problem: You are trying to translate a string in the WooCommerce Product Addon plugin using WPML, but WPML does not detect the translatable string 'validate_msg' => __( 'is a required field', 'woocommerce-product-addon'). Solution: We recommend enabling the "Auto-register strings" option in WPML. After enabling, visit the page that contains this string on the front end. Then, search for the string in the WPML String Translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues where some string translations are not displayed in Armenian on their development site, despite following previous support suggestions. Solution: We recommend increasing the memory limit of your site to meet the minimum requirements of WPML and also the requirements for Elementor. Insufficient memory can prevent translated strings from displaying correctly.
If you're experiencing this issue on other sites, such as issues related to product categories and attributes on an online shop, please open a new support ticket for each site, providing detailed information.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: If you're checking the translation for the Post "Mand" and notice that the link field is missing in a custom Gutenberg block inside a custom field, this might be due to the way links are handled. Solution: We recommend you first make a full backup of your website. Then, you need to modify the PHP code that registers the strings for ACF blocks. Specifically, edit the file
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive