Background of the issue:
I am trying to continue the previous support ticket regarding a huge problem with the translating repeater field in the classic editor. The previous ticket can be found here: https://wpml.org/forums/topic/a-huge-problem-with-the-translating-repeater-field-in-classic-editor-continued/. I was on vacation, and the ticket was closed in the meantime. I was getting support from Bigul, who asked me for access to the website to check on a duplicated website.
Symptoms:
The issue is related to the translating repeater field in the classic editor. I expected everything to be explained in the link provided, and Bigul can ask me for the secure form again.
I restarted this ticket because this is also happening on another site, where I have team members in the repeater field. I was supposed to delete one member and then to add two new rows with 2 new 2 members in the middle of the repeater field.
I want to report what happened. When I deleted the member, it was on the last row, I saved the page and then I went to check the translation in Albanian and Macedonian, English is here the default language. Then when I added 2 new rows in the middle and wanted to translate the page it was the same story, that repeater fields were messed up like on the previous website, the completed translations were deselected and almost the whole repeater field with wrong translations, only the first 2 rows were not affected. What is interesting is that there were still translations of the row that I deleted in the first place. Why were they there when that row was deleted already, the page was saved before without I added 2 new rows.
There is a bug for sure, what is also interesting is that the repeater was set to Copy, not Copy Once, that was the solution you suggested before, setting the repeater field to Copy, not Copy once.
I am really sorry that I am bothering you with this but it's really bothering me for years, when I have to add / delete some rows, the translation process for me is a nightmare, I have to manually move the translations to the old state manually and that is taking me a very long time.
Thank you for contacting WPML support. Sorry for the late reply; it was due to a higher workload.
Before your ticket is assigned to one of my colleagues, please allow me to walk you through some initial debugging steps. This will help speed up the support process.
Please log in to this hidden link">sandbox site and replicate the issue. If it is reproducible, please let us know how to reproduce it.
Thanks for the reply. The thing is that I cannot reproduce this issue on the sandbox site because on mine website I have a complex repeater field entry. I was having a good talk with Bigul and he understands the issue well, why he cannot assist me further. Before the ticket was closed he was sending me request for secure font where I will add my credentials so he can check the problem. Can I contact him?
Thank you for the updates. Please fill in the private details fields after a full site backup{mandatory}. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information-sharing policies.
Also, please allow me to make a copy of your site using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server. So we can troubleshoot the bug without affecting your live site.
Thank you for the details and login information. I am creating a copy of the site now. But is taking more than the expected time. Please check the attached images for more details. We will get back to you soon.
Thank you for the updates. Sorry, we cannot access the site now. It shows a 502 Bad Gateway and Database Connection errors. Please check with your hosting support.
The issue exists on my local copy after the initial checks. So consulting with our team for an expert opinion. We will get back to you as soon as possible. Please wait. Sorry for the delay because of a long weekend.
The ticket is forwarded to our second-tier team for further checking. Becuase the bug exists after primary troubleshooting procedures. We will get back to you as soon as possible. Please wait.
