Problem: The client was experiencing a warning when trying to translate their homepage into English, indicating an encoding issue with fields sent in translation. The client attempted to resolve the issue by following a tutorial and accessing the 'custom XML configuration' in WPML settings, but found it empty and was unable to make changes.
Solution: We recommended confirming if the client had followed the documentation on how to fix the encoding of fields. It is expected to have an empty XML file initially, as the problematic fields need to be identified and added to the XML file before their encoding can be edited. We suggested duplicating the page that was stuck and removing elements one by one while trying to send it to translation to identify the field causing the error. Additionally, we asked the client to enable debug information to provide us with more insights into the issue, with instructions available at how to provide debug information.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us.
