Problem: You are trying to edit translations for a previously imported article using the advanced translation manager (ATE), but find that translations are not editable without redoing the entire translation. Solution: Unfortunately, it is not possible to edit imported translations directly in the ATE. You have two options: 1. Use the manual translation method. 2. Switch to the Classic translation editor. For detailed guidance, visit: Using different translation editors for different pages and Using the translation editor. Alternatively, to open translations in the WordPress editor instead of the ATE, follow these steps: 1. Open the default language post in the WordPress editor. 2. In the language meta box, switch the translation method to "WordPress editor". 3. A popup will appear, asking whether you want to set the WordPress editor as the default editor for this specific post, the entire post type, or the entire site. Select the option that suits your needs and save the changes.
This solution might be irrelevant if it's outdated or not applicable to your 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where manually translated content in Cornerstone was overwriting content on the secondary language.
Solution: We advised the client to update all outdated plugins and themes, especially WPML-related plugins. To update WPML plugins, the client needed to: 1. Go to the 'Commercial' tab in the 'Add New' section of the 'Plugins' menu. 2. Unregister WPML from the site if the registration key didn't match. 3. Remove the actual site from their WPML account. 4. Register the site again with the correct key. After updating the plugins, we asked the client to check if the issue persisted by creating a new test page. When the issue was still present, we requested authorization to run tests and eventually escalated the issue to our 2nd tier support team.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 necessary, please open a new support ticket for further assistance.
