Problem: If you're experiencing issues with a pure HTML block that contains a contact form, such as
<div id="form-acm_55342"></div>
, not being detected in the Advanced Translation Editor (ATE) screen, we can help. Solution: We recommend using the custom XML configuration code below to inform WPML about the elements that need to be translated within your custom HTML code:
After adding this code to WPML > Settings > Custom XML Configuration, the form ID "form-acm_55342" should be available in ATE for translation. For more details, please visit our documentation on how to make custom Gutenberg blocks translatable.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to translate the components of the 'Thank you' page in WooCommerce using the NextMove plugin into other languages. Despite following outdated documentation and attempting translations through String Translation and direct page translation, the components still appear in the original language, Russian. Solution: We recommend the following steps to resolve the issue: 1. Ensure each translation of the 'Thank you' page uses a unique slug. 2. After setting the unique slugs, re-save the permalinks for each language you are translating. This action should help the components of the page to display correctly in the intended language.
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 problems persist, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
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 the site logo is not appearing in the translated header and footer on their multilingual website. Solution: If you're facing a similar issue, we recommend following these steps: 1. Ensure you have a backup of your site. 2. Install and activate the WPML Media Translation plugin. You can install it via your WP dashboard under Plugins >> Add New Plugin > Commercial tab, or download it from here. 3. Navigate to WPML >> Media Translation. 4. Search for 'logo' and press the Filter button. 5. Click on the Plus (+) icon, add the logo name in the Name field to enable the save button, and then press the “Save media translation” button. 6. Clear all sorts of site/server/CDN cache. If the logo still does not appear, you might consider deactivating and deleting the WPML Media Translation plugin as it should continue to work. Alternatively, check the suggestions in this thread: WPML forum thread.
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 issue persists, please open a new support ticket.
Problem: The client is experiencing a critical error when activating WPML, which states that the WordPress REST API must be enabled for WPML to function correctly. The REST API stops working upon WPML activation, and the site becomes slow. The issue was narrowed down to three custom code snippets affecting the REST API functionality. Solution: We recommend consulting with your developer to address the issues caused by the custom snippets that interfere with the REST API when WPML is activated. If your developer needs further guidance or has specific questions, we are here to assist, although we do not provide support for debugging or writing custom code.
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: After switching from Elementor to Gutenberg, all old Elementor strings still appear in the WPML translation editor, causing an increase in translation page length and unnecessary use of translation credits. Solution: 1. Disable Elementor and Elementor Pro, then edit the original content in Gutenberg and save the page again. This should remove the old strings from the translation editor. 2. Clear your site's cache. 3. Check WPML > Packages for any remaining Elementor string packages and delete them. 4. Note that WPML's Advanced Translation Editor has a translation memory feature, which prevents charging for the same translation segments twice. More details can be found here: https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/ 5. If issues persist, consider providing temporary admin access for further investigation.
Please be aware 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 continues, please open a new support ticket at WPML support forum.
