I did the change on the live site was I did it on the staging site suggested solution. BUT, there have been other changes "pending" (or whatever caused the edit-icon not to appear), I did not see 3 edit icons, when I started.
About the "expected" behaviour. For example, let's assume this case:
I have 3 edit icons shown. Then the user enters FR translation and chooses "back" to return to the WP pages overview page. Even this causes a change and the edit-icon is gone. If even this workflow causes issues in the translation flow, how can this ever be correct when you think about a multi editor user scenario where people do not take too much care about this things? My point of view would be that WPML has to consider and handle these cases, because edits are allowed and if this scenario is causing that much troubles.... It can't be a solution of a user does not see the 3 icons, that he/she has to fix this first, without knowing how to fix this. And going to the main language and update all the 3 translations again, that is not a real live scenario to my understading.
...and for now, sorry, but I would like to see these cases work on the staging site, without issues and not allow access to the live client site.
Just to make sure we stay on track, could you please confirm if the main issue with the ampersand is now resolved on the live site after applying the steps, or if it is still occurring?
Regarding your second point, I understand your concern. However, I’m not fully sure I’m following the exact workflow you described, especially around the edit icons and what is disappearing. It sounds like there might be a misunderstanding or a specific scenario we need to look at more closely.
To keep things clear and efficient, I would suggest we first confirm and fully resolve the main issue to keep things clear. After that, we can continue in a a new ticket with the workflow concerns as a separate point and go through it step by step. Once I clearly understand the exact steps and expected behavior, I’ll be able to explain or escalate if needed.
Live site: still no ampersand shown on the frontend, but there in the translation interface. Still the same problem, tried the suggested workflow with no luck.
I checked again, and everything looks correct from our side. Since it’s working properly on the staging site but not on the live site, it’s could be that something else in the live environment is also causing the issue.
I’ll check with our team again to see if they can take another look from our side.
I will update you soon.
Sorry for the inconvenience, and thank you for your patience.
