peterJ-48

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.