Problem: The client reported issues with automatic translations not detecting HTML fields in product category descriptions and some descriptions not being translated at all. Additionally, there were problems with the HTML structure not being respected in translations, which is crucial for SEO, and issues with Yoast SEO term meta not appearing translated in the frontend.
Solution: 1. To address the HTML tags issue in product category descriptions: - Edit the file
- In WPML settings, disable the option "Don't show translated taxonomies in Translation Editor" to allow translation of category descriptions directly in the Advanced Translation Editor and retranslate the products. 2. Alternatively, translate the product category manually via WPML > Taxonomy Translation. 3. For translating Yoast SEO term meta, ensure to send the term meta for translation from WPML > Translation Dashboard as detailed in our documentation here. 4. To resolve issues with the same slug across languages, enable the option "Adjust IDs for multilingual functionality" in WPML > Languages > Section Make themes work multilingual.
If these solutions do not resolve your issue or seem 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: The client is experiencing an issue where after switching from the Linguise language plugin to WPML, the URL slug for Portuguese changed from 'pt' to 'pt-pt', and they want to revert it back to the original 'pt' slug. Solution: If you're experiencing this issue, we recommend creating a custom language in WPML where you can specify the desired language code. Here's how you can do it: 1. Go to WPML > Languages. 2. Under 'Edit Languages', click on 'Add languages'. 3. Enter the language name, code (in this case, 'pt'), and other details. 4. Save your changes. This should help you set the URL slug to your preferred format.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You have a custom taxonomy called 'fitment' assigned to WooCommerce products, set as Not Translatable in WPML. Terms are created in Polish and work correctly in Polish products, but in the English product edit screen, the taxonomy is visible without any terms to select. You want the same taxonomy terms to be shared across all languages without needing translations.
Solution: The issue might be related to the
meta_box_cb => 'post_categories_meta_box'
in your custom code. This meta box forces WordPress to render the classic Categories-style checklist metabox for this taxonomy, which relies on wp_terms_checklist() → get_terms(), and WPML filters get_terms() in wp-admin to the current admin language. If your Fitment terms are created only in the default language and don’t have term translations, the checklist in the secondary language can appear empty. To resolve this: 1. Remove the
meta_box_cb => 'post_categories_meta_box'
from your custom code to test if the terms show in the translation without it. 2. Register the taxonomy on init with priority 0 to avoid issues with it being registered too late.
If these steps do not resolve the issue, or if the solution becomes 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.
