Problem: The client was unable to save a translated page using WPML; the process was stuck at 96%. An error message 'Save all sentences before finishing' appeared, despite all text fields being filled and marked in blue. Solution: We identified that one of the texts was not available for translation in the WPML Translation Editor, which caused the translation process to halt. Switching to the previous version of the Advanced Translation Editor (ATE) resolved the issue, allowing the missing text to appear for translation. This problem is related to a known issue, which can be reviewed here: HTML attributes not available for translation in Advanced Translation Editor.
If you're experiencing similar issues, we recommend trying to switch back to a previous version of the ATE to complete your translations. However, this solution might be temporary or 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client needed to override custom CSS to show the Polish language switcher on a specific page, despite it being hidden on other pages. Solution: We recommended finding a CSS selector for the specific page where the Polish language switcher should be visible. This selector can then be used in the custom CSS to override the default behavior. We provided a step-by-step guide: 1. Identify the unique CSS selector for the page where the switcher should appear. 2. Use this selector to apply the custom CSS rule. For example:
