Okay, I found the issue with our sandbox site is that the version of WPML AI is not the same. I'm creating a new fresh install on our cloudways server where we will be able to use the latest version of WPML AI which should include Greek to English automatic translation. As soon as I have that set up, I'll set up WPML and use only the WPML AI translation service and try to reproduce this issue.
I can see that if I insert the content in the post type "Post", the & shows as expected in the translation.
How are you displaying the ACF fields on the frontend - are you inserting custom code in a template, in a custom function, etc? I would like to test the ACF fields on the Post type and compare it to the custom post type that you have set up. hidden link
It doesn't matter if I display the acf fields or not. As you can see in the post I recreated the bug in your setup, I don't show the fields on the front end, but the bug still happens in the post content.
It is just a simple custom post type with custom fields from ACF, no custom coding at all. I think that the WYSIWYG editors might have something to do, but you should debug it.
Did you do any tests at all on ACF? Or did you just create a normal post type?
I understand that you might have a lot of tickets. But getting back to me after 6 days, while I have clearly recreated the bug, to only tell me that you tried it with on something else (not on what I showed) and "it worked", doesn't seem acceptable at all.
I would kindly request from someone else from the WPML team to join. It has been over a month, and to be honest I feel like I've done all the debugging by myself without any significant help. On past tickets, WPML supporters have been quite helpful in the process, but this time I'm quite disappointed.
My apologies for the late last response, we had most of the team off over the holiday weekend. I should have explained better why I am asking about the frontend. I had added the ACF fields to the regular Post type as well. While I can see on the example you provided that the & does not display in English, I am testing on a other post types to try and isolate if the issue is post type related, ACF field related, or something else. You mentioned that you think the issue is ACF related, which is why I was asking about displaying the fields, so that we can test WYSIWYG editor content and find if the issue is there as well.
I continued testing with different custom post types and am able to see the issue there. I also test a few solutions (string translation, glossary terms, etc) but none have solved it so I have escalated this to our 2nd tier support team and will update here as soon as we have more informatin.
THis issue has been escalated to our ATE team and for now, the suggested workaround is to use a backup translation engine since the issue with & is not happening there. Once we have it resolved for WPML AI, I will update you here.
