Problem: The client was unable to change the 'read more' and search placeholder texts in the Dutch language using the Kadence Builder, despite the strings being translated in WPML's String Translation section.
Solution: We discovered that the issue was related to how Kadence Builder's custom fields were registered with WPML. To resolve this, our team created a custom XML configuration to ensure these fields are recognized and translatable by WPML. Here are the steps we followed:
1. We examined the content inside the database of the main query post type to understand how the blocks were structured.
2. We created a custom XML configuration and added it to WPML > Settings > XML config tab. The XML code used was:
3. After saving the XML configuration, we made a small edit and saved the default language edit page, then updated the translated version with the correct placeholder text.
This solution allowed the 'read more' and search placeholder texts to display correctly in both languages on their respective pages.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client created a variable product in WooCommerce and needs to translate the name of the default variation. After translating, the product appears empty in the frontend. Solution: 1. Ensure the WooCommerce Multilingual & Multi Currency plugin is installed and activated. You can download it from here. 2. Edit the variable product in the default language ensuring that the "WPML Translation Editor" is enabled. 3. Translate the secondary language product using the WPML Translation Editor. For detailed steps, refer to this documentation. 4. If the variation still does not show in the frontend, follow these troubleshooting steps: - Clear the cache in WPML. - Synchronize posts taxonomies. - Remove ghost entries from the translation tables. - More steps can be found in the WPML Support Troubleshooting page. 5. Consider creating global attributes and translate them either during the product translation or via WooCommerce >> WooCommerce Multilingual & Multicurrency > Attributes tab.
If these steps do not resolve the issue, we 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.
Problem: The client was unable to open the Elementor editor for a translated page/template, resulting in a 403 Forbidden error and an uncaught TypeError. Solution: The client said he had found a folder named /he/ on the server. Removing this folder solved the problem. If this solution is 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 issues persist, please open a new support ticket at WPML support forum.
Problem: You are adding new tours to your website and translating them using WPML. Although the translations are visible in the WordPress admin panel, they do not appear on the site. On the Spanish page, some tours are listed in English, and clicking on them results in a 'The page is not found' error. Solution: We recommend following these steps to resolve the issue: 1. Check the documentation on .htaccess issues with WPML. 2. Disable all non-WPML plugins and switch to one of the default themes to see if the issue still persists. 3. Ensure you create a backup of your site (both files and the database) before making any updates or changes.
If these steps do not resolve your issue, or if the 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. If the problem persists, please open a new support ticket.
Problem: You are trying to translate WooCommerce products and pages, but it results in duplicates and re-assigns the default pages. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to Dashboard->Pages. 2. Quick edit the page without the translations and set the slug to something else and set it as draft. 3. Quick edit the correct page and set the slug to the correct one. 4. Open the correct page and try to make some changes to see if the pages duplicate again.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: You are unable to update the WPML plugins and receive an ERROR message. This issue typically occurs when the site URL and the registered site URL do not match (e.g., with or without 'www'). Solution: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key. 3. Log in to your WordPress site, go to Dashboard >> Plugins >> Add new plugin > Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link. 5. Click the Get a key for this site link and follow the instructions to generate a new key. 6. Copy the new key, paste it into the input box on your site, and press the Register button. 7. Take a backup of your site. 8. Attempt to update the WPML plugins again.
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 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 the problem persists, please open a new support ticket.
