Home›Support›English Support›[Escalated to WPML Developers team] A huge problem with the translating repeater field in classic editor (continued again)
[Escalated to WPML Developers team] A huge problem with the translating repeater field in classic editor (continued again)
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.
First of all, thank you very much for your effort. I really appreciate this.
I think that your developers must find a solution for this issue, it's not a small bug, to me it's affecting almost 3-4 sites. Repeater field is frequently used advanced custom field, especially for cases like mine. It gives me lots of headaches when I have to update something and then wok on the translations, I am loosing precious times for years.
I only don't understand, I have reported this bug in the past too, but only you have taken this seriously, I see lots of other reports in the forum, so is probably happening to many people. I hope that your developers will find the solution soon.
Thank you once again, if you can please keep me updated for any progress.
Thank you for the feedback. Our developers have been working on related cases for the last couple of months. But still looking for a proper fix. This bug is only happening when we are using WPML Classic Translation Editor for translating the posts.
We will get back to you soon when we have an update from our developers on this. Please wait. Thanks a lot for your kind support and patience.
The last answer about this is 10 months ago. I am still having huge problems with this and it's really disappointing for me that this issue hasn't been solved.
Since I am experienced with WPML for years, almost 10 years, I still find the classic editor better for my way of working. Please understand that this issue is very important for me & others to be solved. Do you have any kind of progress so far?
I’ve taken over your support ticket. I’m sorry that you ran into trouble with this.
I can confirm that the issue is already on our development team’s list. Although I don’t have an exact ETA for the fix, I’ll make sure to keep you updated here as soon as more information becomes available.
I’ve also left a comment for our team to let them know that you’ve contacted us regarding this issue.