Problem: The client was unable to send a Global Header with base64 encoded fields for translation using WPML. Attempts to configure custom XML to handle the encoding were unsuccessful, resulting in errors and the removal of content from the translation job. Solution: We recommended updating the XML configuration in WPML settings to properly handle base64 encoded fields. Here is the correct XML configuration:
This configuration should be added under WPML->Settings->Custom XML Configuration. Additionally, we provided links to relevant documentation and known issues:
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to save changes when trying to use personalized flags for different languages on their WPML settings page. Despite attempting to save, the page did not respond, and no confirmation of 'Changes Saved' appeared. The issue persisted even after deactivating cache and security plugins. Solution: We identified that the problem was not related to the flags themselves but was due to a JavaScript error on the language edit page. Here are the steps we recommend: 1) Navigate to WPML > Settings > Translation Mode and change it to 'Translate What You Choose'. 2) Return to the language settings and attempt to add the image and save again. If these steps do not resolve the issue, it might be because the solution is outdated or not applicable to your specific 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.
