Problem: The client was unable to view the Spanish version of a product page despite translating it. In the backend, a plus icon indicated the need for translation, which persisted even after translating. On the frontend, switching to Spanish would reload the page in the default language.
Solution: We identified that caching plugins might have caused the issue. We deactivated the caching plugins and switched to the 2024 theme. After editing the page and adding a Spanish translation, the issue was resolved, and the Spanish page displayed correctly both in the backend (showing a pencil icon) and on the frontend.
If this solution does not resolve your issue or seems irrelevant due to being 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where a notice appears stating that a message must be translated manually because the field groups associated with it use different translation options. As a result, the translation editor cannot be used. Solution: We recommend checking the Advanced Custom Fields (ACF) field groups by navigating to the ACF field groups section in the WordPress admin. Look for the field group named "Productinformatie" and switch it to "Expert" mode. Before making this change, ensure to create a backup of your site. This action may resolve the issue with the translation editor.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket with us.
