Problem: The client is using the directory for the default language, and the SEO Framework is incorrectly adding this default language directory to all sitemap links in robots.txt, resulting in invalid URLs. Solution: We recommend modifying the SEO Framework plugin code to correct the sitemap URLs: 1. Open the file located at
Please note this is a temporary workaround. We are awaiting a more comprehensive solution from the plugin author.
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.
Problem: If you're experiencing issues with product variations breaking down when adding groups to an attribute using WooCommerce Attribute Swatches by Iconic, you might notice that after editing an existing attribute and adding a group to it, each variation disappears for each translation from the product page. Additionally, the number of terms in the attribute may increase significantly. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML > Settings. 2. In the "Custom Term Meta Translation" section, set the translation preference for the "iconic_was_term_meta" field to "Copy" and save the changes. 3. From the "Taxonomies Translation" section, change the translation preference for the Attribute (e.g., Product color (pa_color)) to "Translate," allowing the Attribute and its variations to be translated. 4. Go to WooCommerce > WooCommerce Multilingual > Attributes. 5. Select the Attribute from which the variations were created. 6. At the bottom of this section, click on the button labeled "Synchronize attributes and update product variations." This action correctly displays the variations in the product but not in the Group. 7. To display them in the Group, go to Products > Attributes and open the Attribute from which the Variations had been created. 8. Click on 'Quick Edit' below the Term added to the Group and click on the update button without making any changes. This action copies the Groups to the translated term, and as a result, the variations start displaying correctly in the Group on the frontend.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to use a product tag as a display rule in GeneratePress, but WPML is not replacing the product tag ID from the default language to the translated language product tag ID during translation. This issue occurs because WPML is copying _generate_element_display_conditions 1:1 without replacing the product tag ID. Solution: To resolve this issue, you need to modify the GeneratePress conditions file to include a WPML filter that correctly translates the product tag ID. Here are the steps: 1. Open the
This modification should ensure that WPML correctly translates the product tag ID in _generate_element_display_conditions.
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 was unable to switch languages on their shop page; it kept redirecting to the English version. Solution: 1. We identified that the shop page had not been translated into other languages. 2. We translated the shop page into German. 3. We noticed that there was only one product which also had not been translated. 4. We translated the product into German. 5. After these translations, the German shop page became accessible at https://dagradev.kinsta.cloud/de/shop/. 6. We reminded the client that pages should be translated, and this process is usually automated if the WCML Setup Wizard is completed.
If you're experiencing a similar issue, we recommend ensuring that your shop page and products are translated into the desired languages. Also, make sure to complete the WCML Setup Wizard to automate the translation process. If the solution provided here is not relevant to your case, possibly because it's outdated or not applicable, please open a new support ticket. We also highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
If you need further assistance, please contact us in the WPML support forum.
