Problem: The client is experiencing issues with product attributes not being available for selection on the product page in different language versions after translation. The attributes appear correctly in the original language but not in the translations. Solution: 1. Ensure that global attributes are created in the site's default language and avoid duplicating attributes under different names in different languages. This can be managed under WPML > Taxonomy Translation. 2. If changes are made to the original product's attributes or variations, save the variations again to sync these changes across translations. There is no need to re-translate the products if only attributes or variations are changed. 3. For issues related to caching, especially with WP Rocket, ensure that the cache is cleared after updates to products. This can be automated by setting up 'Always purge URLs' in WP Rocket settings to include:
/shop/*
4. If these steps do not resolve the issue, it may be helpful to deactivate unrelated plugins and switch to a default theme like Twenty Twenty-One to identify if the issue is related to specific plugins or themes.
If the problem persists or if this 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: You are managing translations for tags using the WPML 'taxonomy translation' tool and have encountered an issue where the Ukrainian translation of a tag separated from its Russian version. This separation resulted in a 301 redirect, and the Russian version created a duplicate Ukrainian translation with the same name. Solution: The issue arises from a mismatch in the database collation settings. Your database's wp_terms table uses the utf8mb3_general_ci collation, which does not fully support non-Latin characters like Cyrillic, while your WordPress configuration is set to use utf8mb4. To resolve this, we recommend updating the collation of your core database tables, particularly wp_terms, to utf8mb4. This update will support a broader range of characters and should prevent similar issues in the future.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues 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 for further assistance.
Problem: In Classic Editor, when entering a tag name, the AJAX request (ajax-tag-search) does not return some tags in Ukrainian, even though they exist in the database and are correctly translated in WPML. This issue does not occur in Gutenberg. Solution: If you're experiencing this issue, we recommend you go to WPML -> Languages and check the box for
Adjust IDs for multilingual functionality
. This adjustment should resolve the issue by ensuring that the AJAX requests in Classic Editor correctly recognize the language settings.
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.
