Problem: You are experiencing issues with ATE translations not completing, and those that do complete take many hours. The error log indicates an 'AMS Server Communication Api error missing resource: No sitekey found for this website.' Additionally, there is a concern about a base64-encoded data URI within an image source attribute that might not be intentional. Solution: First, ensure that your site is correctly registered with WPML and that your subscription for automatic translation credits is active, as these are prerequisites for the Advanced Translation Editor to function properly. If these are in order, the next step is to investigate the specific content causing the issue. In your case, there is an unusually large base64-encoded image URL within the content, which might be affecting the translation process. We recommend removing or replacing this image to see if it resolves the translation delays and errors. If the problem persists or if the solution provided here becomes outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: The client is experiencing an issue where deleted glossary entries in Portuguese reappear and do not trigger a retranslation to the default language. Additionally, the slug remains unchanged, maintaining the original translation. This issue persists even after adding a new language (Turkish), where the glossary automatically filled itself with translations using the original term as the translated term. Solution: We have addressed the issue by deleting the problematic glossary entry completely and then re-adding it with only the Dutch value. This approach seems to prevent the Portuguese term from reappearing. We recommend checking if this solution holds by monitoring the glossary entries. If the issue persists or if similar problems occur, especially after activating ATE or adding new languages, we suggest opening a new support ticket for further investigation. Additionally, it's important to ensure that all themes and plugins are updated to their latest versions.
Please note that this solution might become irrelevant due to updates or specific circumstances not covered here. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix. If the problem persists, do not hesitate to open a new support ticket at WPML support forum for personalized assistance.
