Problem: The client was experiencing mixed content issues when translating the 'admin_texts_astra-settings' domain, where translations were replacing the original English text with Spanish on their website. Solution: The client resolved the issue before the WPML support team could provide a solution. However, if you're experiencing similar issues, we recommend setting up a staging website to test translations thoroughly before applying them to the live site. This approach helps identify and fix translation issues without affecting the live environment.
If this solution is outdated or does not apply 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: After duplicating products and importing translated content via WP All Export and Google Sheets, the products still display as duplicates in the admin area with a message indicating they are maintained by WPML. This could potentially overwrite the translations if the original product is edited. Solution: This behavior is expected because WP All Export does not modify the post status in the postmeta table, which means imported products remain marked as duplicates. To resolve this, you can manually set each product to 'translate independently' by clicking the respective button in the WPML interface. Alternatively, you can attempt to remove the
_icl_lang_duplicate_of
keys using WP All Import, which might change their status to independent translations. Detailed steps for this process can be found here. Ensure you back up your site before making these changes.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise 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.
Problem: The client is experiencing an issue where the 'Advanced translator' overrides manually edited product category names during the translation of products, leading to incorrect translations that do not consider the manually edited category names. Solution: We recommend using the WPML Glossary to manage specific translations and ensure that manually edited category names are considered in future translations. This approach helps in maintaining consistency and accuracy in translations by preventing the 'translation memory' from overriding manual edits.
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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client is facing two issues with their multilingual site using WPML and Funnel Kit. First, Elementor cannot load the editor for the French version of the checkout due to a cross-origin error. Second, the default English language checkout incorrectly loads the French version. Solution: 1. For the Elementor issue, it's likely related to the cross-origin policy. We recommend checking with your hosting provider to ensure that the cross-origin policy is disabled. If problems persist, contact your hosting support to disable the CORS policy. 2. Verify that you have added the correct page IDs in the code snippet to ensure that the correct language version loads. 3. Ensure that the French checkout page is created correctly. It should be manually edited and set up as in the English version, even when WPML is disabled. 4. Check the setup on a staging site where different domains per language are not used, as this might resolve the issue.
If these steps do not resolve your issues 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: The client is experiencing an issue where after updating the theme customizer, the content that should remain in English is instead showing in other languages. This problem is linked to the Query Monitor plugin blocking Ajax actions from WPML during the save process. Solution: We recommend disabling the Query Monitor plugin, especially when updating content or translations, as it is primarily a debugging tool and can impact performance on live sites. Disabling it should resolve the issue with saving content in the correct language. For more details on this conflict, you can visit the discussion on WordPress.org.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket at WPML Support Forum.
Problem: The client was unable to see multiple choices of size for a product on their multilingual website. The product variations were not displaying and weren't linked to any attributes. Solution: First, we addressed a redirection issue by changing the "Language URL format" in WPML > Languages > Language URL format. For the issue of missing attributes on the translated product page, we recommended running the WCML Troubleshooting options available at WCML > Status > Troubleshooting. This action resolved the problem with product variations not displaying correctly.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing 404 errors on translated pages and incorrect redirections from default to translated content across multiple websites. Some languages work correctly, while others either show a 404 error or redirect incorrectly. Solution: We have identified that this issue may be related to the Rank Math SEO plugin, specifically the 'Remove Parent Slugs' option. This setting can cause issues with the translation of category slugs, leading to 404 errors. We recommend checking our known issues page for more details: https://wpml.org/known-issues/ Please follow the workaround provided on the following errata page: https://wpml.org/errata/rank-math-seo-remove-parent-slugs-option-causes-category-slug-translation-error-404/ We are also working on a permanent fix that will be included in future versions.
If this solution does not resolve your issue or seems irrelevant, 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 at WPML support forum.
Problem: The client is experiencing a CORS policy error when accessing fonts from a different domain, which is causing issues with content mixing between translated and default language versions on their website. Solution: We recommend first disabling any caching on your site to see if this resolves the issue. If the problem persists, you should add the following code to your .htaccess file to adjust the CORS settings:
#BEGIN WPML CORS Policy fix<br /><ifmodule mod_headers.c><br /> Header set Access-Control-Allow-Origin "*"<br /> Header set Access-Control-Allow-Methods "GET, POST, OPTIONS"<br /> Header set Access-Control-Allow-Headers "Content-Type, Authorization, X-Requested-With"<br /></ifmodule><br />#END WPML CORS Policy fix
Additionally, consult with your hosting provider to ensure proper server configuration for CORS. You might find these resources helpful:
If issues with mixed content still occur after these adjustments, please revisit this support ticket for further assistance.
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 problem persists, do not hesitate to open a new support ticket here.
Problem: If you're experiencing issues where translating products using semi-automatic translation causes the original product to lose all its variations, this might be due to specific settings in WPML.
Solution: First, ensure that your WPML URL format is set to "Language name added as a parameter" as using different domains per language might not work reliably, especially in staging environments. Next, navigate to WooCommerce → WooCommerce Multilingual (WCML) → Status to check for any configuration warnings. It's crucial to ensure that the product_variation and other related custom types are set to “Translatable – only show translated items” under WPML → Settings → Post Types Translation.
Additionally, go to WPML → Settings → Custom Fields Translation, show system fields, and search for _variation_description. Change its setting from 'lock' to 'copy' or 'copy once' and save. This adjustment should also be applied to other relevant fields.
It's important to take a backup before making these changes as altering locked fields can lead to undesired effects. If these steps do not resolve the issue, or if the solution seems 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 do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing difficulties in matching translations to original posts using the WP All Import plugin. The process involves exporting, translating, and importing content, which requires simulating an import in the original language first. The client finds this process cumbersome and suggests a simplified method of directly defining original post IDs during import. Solution: We recommend using the WPML Export & Import plugin instead of the deprecated WPML All Import plugin. Here are the steps to follow: 1. Install the WPML Export & Import plugin on both sites. 2. Enable the export options at WPML > Export & Import before running the export. WPML will add additional columns to your file to connect the contents across sites. 3. Activate the import options at WPML > Export & Import before importing. 4. After completing the import, run the migration option at WPML > Export & Import. If these steps do not resolve the issue, we would appreciate it if you could send us the WPML debugging information. More information can be found here: WPML Debugging Information.
Please note that the solution provided might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket at WPML Support Forum.
