Problem: The client is experiencing an issue where Swedish product category URLs on their WooCommerce site are incorrectly using the English category base '/collections/' instead of the Swedish '/product-category/' base after updating the WooCommerce Shop page. This resulted in 404 errors for Swedish URLs while English URLs under '/en/collections/' were unaffected. Solution: We recommended that the client updates their WPML Multilingual CMS to the latest version along with all its add-ons, particularly WPML Multilingual & Multicurrency for WooCommerce, and also update WooCommerce itself. This can be done via the WPML admin panel by navigating to wp-admin/plugin-install.php?tab=commercial, clicking on "Check for updates", and following the update prompts. After updating, the client should remove any .htaccess workarounds, resave permalinks, and clear the site cache to see if the issue persists.
If this solution does not resolve the 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 the problem continues, please open a new support ticket at our support forum.
Problem: The client is experiencing issues with product tag pages on their WordPress site, which are either redirecting to images or showing 404 error pages after the site went live. The URLs for these tags, when translated to Swedish, are not retaining the desired slug but revert to the default 'produktetikett'. The client is also concerned about the SEO impact of these errors and is considering changing the URL structure or setting tags to 'No follow'.
Solution: 1. To address the issue of the tag slug reverting to its default Swedish value, we recommend updating the slug from WPML → Settings. After updating, verify the accuracy in WPML → String Translation. 2. For updating the product category slugs to maintain 'product-category' for the Swedish version and change it for the English version, you can adjust these settings in Settings → Permalinks, and then translate them in WPML → Settings.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing 404 errors on the English version of your product category pages even after updating the permalink and saving the slug via the 'Taxonomy Translation' option. Solution: We recommend resaving the permalinks to address this issue. You can do this by navigating to Settings → Permalinks in your WordPress dashboard and simply clicking 'Save Changes'. This action often resolves issues with 404 errors following permalink or translation adjustments.
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 do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: You are working on a multi-language site using WPML and need to know how to preserve translations when creating a new staging version with live data. Solution: Currently, there is no direct method to push WPML translations from staging to live. However, you can merge the sites to share the same translation memory, glossary, and translation credits for automatic translation. This allows translations made on the staging site to be accessible on the live site through the Advanced Translation Editor. For detailed steps on how to merge sites, visit https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/.
After migrating the site to a new URL, complete the migration banner that appears in WPML and use a unique new site key for each site URL or server change.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with WooCommerce products in their WPML setup. Specifically, products with variations are not displaying variation prices in translated versions. Additionally, there are concerns about translation credits being deducted without successful translations. Solution: For the issue with product variations not showing prices, we recommend opening one of the affected products, making a small change, and then updating its translations to see if this resolves the problem.
Regarding the translation credits, since WPML’s automatic translation feature uses translation memory, it will prevent credits from being charged for content that has already been translated.
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. We highly recommend opening a new support ticket if further assistance is needed. You can do so at WPML support forum.
Problem: You are trying to activate the sitepress-multilingual-cms.4.7.1 plugin, but it causes a fatal error and breaks your site. The error message indicates an issue with an undefined method call in the WPML language switcher component. Solution: 1. Ensure you create a full backup of your site. 2. Access your site's database and open the
wp_options
table. 3. Locate and remove the key
wpml_language_switcher
from the table. This step should resolve the fatal error you are encountering.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. Additionally, please check the related known issues and verify that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum.
