Problem: The client is unable to see the translated string "month" in secondary languages on their website, despite using JavaScript to append this string and the
wp_localize_script
function for localization.
Solution: 1. Ensure all strings are registered: - Navigate to WPML > Theme and plugins localization and scan your themes and plugins. 2. Re-register and translate strings: - Go to WPML > String Translation, delete all occurrences of the problematic strings, enable the "Look for strings when rendering pages" option, visit the frontend, and then add translations. 3. Check database charset configuration: - Ensure the database charset in
wp-config.php
is set to
utf8mb4
. 4. Regenerate .mo files: - Use the troubleshooting section under WPML > Support to regenerate .mo files.
If these steps do not resolve the issue, it may be necessary to use custom CSS for translation or further debug the JavaScript implementation. Custom programming, however, falls outside our support policy. For more complex issues or custom implementations, consider hiring a WPML contractor from https://wpml.org/contractors/.
Please note that this solution might be outdated or not applicable to your specific case. 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 at https://wpml.org/forums/forum/english-support/.
Problem: After auto-translating a product, it remains unpublished and appears as a draft in the 'yoast_indexable' table. Solution: If you're experiencing this issue, we recommend that you publish the translated products manually. You can do this by navigating to Products, switching to the desired language using the language switcher at the top bar, and then selecting the products to publish in bulk. This action should update the post status in the 'yoast_indexable' table to reflect the published state.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue where a secondary language string appears in the base language (English) within the Yoast SEO settings. When attempting to save the secondary language string as an English string, the string remains in the secondary language. Solution: We recommend checking the language assigned to the strings in WPML > String Translation. If the language is incorrect, change it by using the "change language for the selected strings" button. For detailed instructions, please refer to our documentation on how to change the source language of strings.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please do not hesitate to open a new support ticket. You can reach our support forum here.
Problem: If you're experiencing a white screen when trying to access the WPML translation editor after updating WPML Multilingual CMS to version 4.6.6 and String Translation to version 3.2.8, this could be due to an issue with special characters and Regex that our team is aware of. Solution: We have identified that the issue occurs when accessing the translation editor for an automatic translation of a product or from a product page. Our development team has been working on a fix for this problem. A patch has been released that should resolve the issue, and you should now be able to use the translation editor as expected. If you're still encountering problems, please ensure that you have updated to the latest version of our plugins.
If this solution doesn't look relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client is experiencing duplicate entries of existing glossary items in WPML's Translation Management Tools Glossary. Solution: 1. Ensure that all WPML plugins are updated to the latest version. For example, update to WPML 4.6.6 and WPML String Translation 3.2.8. Before updating, make sure to save a backup of the site and database. 2. If updating does not resolve the issue, we are ready to investigate further and would require temporary access to the client's test site's wp-admin and FTP. The client should ensure that a backup is in place before providing access. 3. Our development team is aware of the Glossary Duplicate Entries issue and is planning to implement a fix in the next version of our Automatic Translation Editor. This update is expected to be released in a couple of days, and we will confirm back once it is done.
