Problem: The client is trying to translate a text widget in Elementor using the Classic Translation Editor (CTE) and is concerned about the support and compatibility of CTE with the Advanced Translation Editor (ATE). The client noticed that translating with CTE adds an HTML paragraph to the text and is unsure if this behavior is expected. Solution: We confirmed that when translating with CTE, it is expected behavior for an HTML paragraph tag to be added by Elementor, as this tag usually already exists on the original content. We have confirmed this on a test site running only Elementor. We also clarified that CTE and ATE are not fully compatible because they function differently. Translations done in CTE cannot be migrated to ATE due to different system architectures, including translation memory. However, clients can switch back from ATE to CTE and continue using their translations. If switching from CTE to ATE, translations need to be redone because ATE has its own translation memory. For more details, visit how WPML keeps track of your translations and switching from classic to advanced translation editor.
If this solution does not resolve your issue or seems outdated, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: If you're experiencing an issue where clicking the "Save & Close" button while translating a page results in endless loading and doesn't return you to the Pages list, even though the translations are saved correctly, you might notice errors in the console log related to React or a 500 Internal Server Error for admin-ajax.php. Solution: We recommend you try the following steps: 1. Edit the page in the default language. 2. Copy the page ID from the URL browser bar. 3. Navigate to WPML -> Packages. 4. Search for the ID. 5. Delete the package. 6. Update the page in the default language. 7. Re-translate the page.
Please ensure to back up your database before performing these steps.
Problem:
When I select all strings for context toolset-forms-32761, and click the button "Delete selected strings" I expect all those strings to be deleted.
Instead, I got:
Clicking the button "Delete selected strings" has no effect. Solution:
Updating the plugins solved the problem. It's a bit weird, since I have deleted many strings in the past. But as long as it's working, I'm fine with that!
