Problem: The client needed to manually edit a translated article that was broken.
Solution: We recommended that the client deactivate the WPML Translation Editor before manually editing the content to avoid issues with synchronization that could result in overwritten content. We provided a link to our documentation on how to use different translation editors for different pages: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, we encourage you to check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm 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 with us.
Problem: The client is using automatic translation for their website and is now entering a second phase where they want to add keywords to the original language posts and manually translate different keywords for the translated posts. They are concerned about updates in the original language overriding the manual translations in the translated posts. Additionally, they have an issue with a translated post not picking up changes from the original post. Solution: We recommend deactivating the WPML editor for the specific posts/pages or the full Custom Post Type (CPT) and activating the manual translation mode. This allows direct editing in the Block Editor or Page Builder. Detailed instructions can be found here: Using Different Translation Editors for Different Pages.
Problem: The client reported that WPML was loading many fields named 'field-obsah' containing text from previous versions of posts, which were not present in the current version of the post in the original language. These fields were unnecessarily consuming translation credits during automatic translation. Solution: We recommended the following steps: 1. Navigate to WPML > Settings > Custom Fields Translation. 2. Use the search input to locate the 'field-obsah' field. 3. Set it to 'Don't Translate'. 4. Edit the original post and make a small change. 5. Update the translation. For more detailed instructions, please refer to our guide on translating custom fields.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, 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 open a new support ticket in the WPML support forum.
Problem: The client was unable to create a Translation Manager because no users were appearing in the dropdown, and the search function was not finding any users, despite having at least 15 users with the Editor role. Solution: We recommended that the client add a first name and last name to the user profiles, as our tests showed that the search function requires these fields to locate users. After the client added these details, the issue was resolved. We acknowledged that this behavior seems to be a bug since the system should find users by login email, and we have reported it to our developers for further investigation.
If you're experiencing a similar issue, we recommend you try adding first and last names to your user profiles and then attempt to search for them again. However, please note that this solution might be outdated or not applicable to your case. If the problem 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 in the WPML support forum.
