This thread is resolved. Here is a description of the problem and solution.
Problem:
If you're experiencing issues with custom fields not inheriting values automatically across translations and encountering an error popup when trying to translate content using the Plugin, this might be due to encoding issues.
Solution:
We recommend updating your WPML to the latest version as a first step, as this issue might have been resolved in recent updates. If the problem persists, we can address this by implementing a custom XML configuration. For guidance on setting up custom XML configurations, please refer to the related errata thread: https://wpml.org/errata/wpml-cannot-send-base64-encoded-content-to-translation/.
Please note that this solution might be 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 you still need assistance, please open a new support ticket at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
This topic contains 3 replies, has 1 voice.
Last updated by 1 month, 3 weeks ago.
Assisted by: Paola Mendiburu.
|
Dear Support Team, We implemented the setup as suggested, with the behaviour "Copy" for all fields. However, as shown in the attached screenshot, the following pop-up appeared after trying to translate content with the Plugin. Also the content piece was not processed for translation after clicking on "OK". Could you please support us in investigating this issue? Thanks in advance!  |
|
