I’m Emanuela Grimaldi and I’m a Web Designer and Developer.
I’m working as a freelancer in Milan and I collaborate with various professionals and agencies.
Problem: The client is experiencing issues with translations not showing correctly in the Advanced Translation Editor (ATE) after updates in the primary language. They are concerned that the translated fields are blank instead of being highlighted as needing updates. Solution: We explained that the Classic Translation Editor (CTE) and ATE are not synchronized and use different methods. It's crucial to stick with one editor to avoid conflicts. We recommended continuing with ATE and noted that editing translations directly in the WordPress editor after using ATE can lead to loss of translations. To avoid this, if the client prefers to use the WordPress editor for specific pages or posts, they should disable ATE for those items by following the guide here: Using Different Translation Editors for Different Pages.
If this solution does not apply to your situation, or if it seems 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. If issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported issues with the Content Security Policy (CSP) affecting WPML, specifically involving directives like 'unsafe-inline', 'unsafe-eval', and 'https: URI' in default-src. These issues allow the execution of unsafe scripts and code. The client used a tool called Tenable Nessus to detect these issues and noticed errors such as 'Uncaught ReferenceError: wpml_cookies is not defined' from language-cookie.js. Solution: We asked the client to provide more details about the issues and to share the site debug information following our guide at https://wpml.org/faq/provide-debug-information-faster-support/. We also requested the URL or a screenshot of the errors and access credentials to the site for further investigation. We continued the conversation in a forum ticket to address the issue more securely.
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 at WPML support forum.
