Problem: You are unable to save translations in WPML because the HTML entity is required in French for spacing before colons, but not in English, causing issues when translating and saving content. Solution: We acknowledge that WPML currently expects translations to maintain the same HTML markers across languages. We have noted your feedback for a feature request to change this behavior. In the meantime, we recommend two workarounds: 1. Use CSS to hide the entity in the English version of your content. This approach allows you to maintain the entity in French while visually omitting it in English. 2. Consider using a manual translation method for pages where this issue persists. You can find more information on using different translation editors here: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it becomes outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client is experiencing issues with the synchronization of 'locked' fields between languages in their Options Page CPT. The fields are not syncing as expected when switching between the WPML translation editor and the standard WordPress editor. Solution: We recommend consistently using the WPML translation editor for making updates to ensure that translations are not lost when switching back to the WordPress standard editor. If the field is set to 'Translate', update the choice in the original language, and then translate it in the WPML editor. Avoid editing the translation using the WordPress standard editor after setting it in the WPML editor to prevent losing the translation. The 'Copy Once' setting copies the field value only the first time; if the original language value is updated later, it will not update in the translation. Conversely, 'Translate' does not copy the value, allowing you to set the translation value manually.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 the problem persists, please open a new support ticket.
