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.
The client reported a bug in the WPML advanced editor where a space was being deleted after a bold tag and before the following text. This issue occurred when editing the bold tag in one field while the following text was in another field. Additionally, the client mentioned a new problem where WPML added a br tag before the following text after some links.
Solution:
1. We noticed the client was using an outdated version of WPML. We recommended updating to the latest version and also updating any other outdated plugins to see if the issue would be resolved.
2. We also advised the client to increase the WordPress memory limit to at least 128 MB, as per WPML's minimum requirements.
3. Lastly, we asked the client to clear the cache of the website, including server-side, and to deactivate the Autoptimize plugin temporarily to check if the issue still persisted.
If the solution provided is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly suggest 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 further assistance is needed, please contact us through the WPML support forum: https://wpml.org/forums/forum/english-support/.
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.
Problem: The client is unsure how to publish a post after adding a translation using the automatic translation feature with the setting 'Let me review it before it gets published' enabled. The translated post does not appear in the Translations menu, and the client is questioning whether the only way to publish is through the classic editor and how updates to the original post affect the translation.
Solution: First, ensure that automatic translation is activated by following our documentation: Automatic Translation Setup. If you're using the 'Translate What You Choose' option in WPML > Settings > Translation Mode, note that the 'Let me review it before it gets published' setting will not apply. By default, translated posts are published automatically once the original post is published. This can be configured in WPML > Settings > Translated documents options. If you have selected 'Save the translated post as a draft', then you must manually publish the post. To publish a draft, switch to the secondary language and click on the 'publish' button in the backend editor of the translated page.
Problem: The client is trying to use automatic translation credits on their website after a site migration, but WPML indicates there are not enough credits, despite there being sufficient credits in their WPML.org account.
Solution: 1. We recommend checking the Automatic Translation Usage Report by navigating to WPML > Translation Management > Tools tab to see the used credits on the site. 2. If the credits are not displayed, assign more credits from the WPML.org account to the site by following the documentation: How to assign automatic translation credits to your sites. 3. If the issue persists, it may be related to the sitekey not working correctly after the migration. In this case, follow these steps: - Visit the Registered sites page on your WPML.org account and delete the sitekey for https://msg-life.sk/. - In the WordPress admin area, go to Plugins > Add new > Commercial tab, unregister the site, and then re-register with a new sitekey. - Assign the credits to the site again. Refer to the documentation for unregistering and registering the site: Unregister WPML and Register WPML.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
