Problem: The client is experiencing issues with translating the base of the permalink structure in a multilingual WordPress site using WPML. They have set up a custom permalink structure as /wiedza/%category%/%postname% and translated it to /knowledge/%category%/%postname% for English. However, the posts in English still show the original structure with /wiedza/ instead of /knowledge/. Solution: We explained that this issue arises due to a known limitation with WordPress and multilingual plugins like WPML, where WordPress treats parts of the permalink structure as static strings. While WPML can translate slugs for categories and posts, it struggles with dynamic translation of the base part of the URL (like /wiedza/) when it's part of a complex custom structure. Unfortunately, there is no direct solution within WPML to dynamically change the base of the URL based on the language setting.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where your translated WooCommerce product URLs are not reflecting the correct language (e.g., a French product still shows /produkt/ instead of /produit/), follow these steps to resolve the issue. Solution: 1. Check the translation in WPML → String Translation: - Go to WPML → String Translation. - Search for the product slug string. - Ensure it has the correct French translation and is not empty or incorrectly translated. 2. If the issue persists, try deleting the slug in WPML → String Translation, then: - Go to Settings → Permalinks. - Resave the permalinks. - Try again to translate from the Store URLs section in WCML.
If these steps do not resolve your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is facing an issue where there is no Translation Group ID in the export file, making it difficult to manage translations for a large number of products. Solution: We recommend using WPML’s automatic translation feature to directly translate products without the need for manual export or import. For more details on this feature, visit WPML Automatic Translation, Automatic Translation Pricing, and Changing Automatic Translation Engines. If you still need to use WP All Import for translations, follow these steps: 1. Export your default language content using WP All Export. 2. Add a column for the unique identifier in the newly created CSV. 3. Delete the original content from the site. 4. Import the default language CSV file with the unique identifier column as New items using WPML All Import. After importing the default language file, proceed with your secondary language file as previously explained in Importing Secondary Language File. Note: If you see a DEBUG message indicating that WCML is not installed while it is, please disregard this as a GUI issue that will be addressed in future updates.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
