annikaN-2

Problem:
The client makes a change in the original content and when opening the Advanced Translation Editor the content for that segment is empty.

Solution:
This is expected if you don't have automatic translation enabled.
When automatic translation is enabled, any change made to the original content is automatically populated in the editor.

If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, please check the related known issues and verify that you have installed the latest versions of themes and plugins. For further assistance, you can always contact us through the WPML support forum.

Problem:
If you're editing text in the original language on your site and then attempt to correct the text in another language using WPML's Advanced Translation Editor, you might find that the translation in the second language disappears. This issue occurs when the system detects changes in a segment, requiring you to retranslate and review it.
Solution:
When you add new text in the primary language and save changes, ensure you use the "Complete Translation" button in the Advanced Translation Editor. This process should help in retaining the translations based on the translation memory. If the translation still does not appear, it might be necessary to manually re-enter and retranslate the affected segments. For more details on how translation memory works and can assist in this process, you can read here: https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, we recommend opening a new support ticket. Additionally, we highly advise 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.

Problem:
The client was experiencing issues with the Advanced Translation Editor (ATE) in WPML where list items were not translating correctly and were appearing in a single line instead of individually. Additionally, certain custom checkbox fields were not being picked up for translation.

Solution:
1. We made a minor edit to the original post and saved it, prompting WPML to recognize that the translation needed an update.
2. We switched to an older version of ATE and saved the changes.
3. We purged the cache to ensure the changes took effect.
4. For the custom checkbox fields not translating, we instructed the client to:
- Use the WordPress Editor to edit a record containing the items.
- Navigate to 'Multilingual content setup' and click on 'Show system fields'.
- Set the fields like _custom-checkbox-2, _custom-checkbox-32, and _custom-checkbox-4 to 'Translate'.
- Make a minor edit to the original post/listing and save it.
- Update/add the translation to see the fields available for translation.
5. For fields related to open hours, we set them to 'copy' to ensure they correctly reflect across translations.

If these steps do not resolve the issue or if the solution seems outdated, we 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:
You want to disable Automatic Translation for some users on your site but find that the buttons to disable this feature do not work.
Solution:
To disable Automatic Translation for users with the role of Editor or lower, navigate to the Tools tab and select 'Who can use Automatic Translation'. Note that this setting cannot be applied to administrators, as they have full permission to use Automatic Translation. If the users you are trying to restrict have different roles or if you encounter any issues, please provide us with the role of the user and a screenshot of the 'Who can use Automatic Translation' tab for further assistance.

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 persists, do not hesitate to open a new support ticket at WPML support forum.