I am trying to:
On a site with English and French, in a custom post type "Project" we have a Repeater field that has a Taxonomy field, both set to Copy. I create a Project post, save the first time then use duplicate to create the initial translation and set it to translate independently. Until here it works properly, if a term was selected in English the French post will have the corresponding French term selected. But then if I modify the post French post, update just the title for example, or select a different term in the English post and save, when I check the French translation it will now also have the English term saved instead.
I expected to see: Modifying a post with a taxonomy in a repeater should copy to the other languages using the associated languages' term.
Instead, I got: Modifying a post with a taxonomy in a repeater sets all translations to use the "Main" languages' term
Also, I tried the same taxonomy in a field outside of a repeater and it copied correctly to the other language. And tried all this on the base "Post" type as well so it does not seem to be because it was a custom post type.
Thank you for contacting WPML support, I'd be happy to help you with this issue.
On my demo site, I see the subfield taxonomy value in a repeater is not copied to the translation post if I duplicate and translate the post independently. I think it is an expected behavior.
If you duplicate and translate the post independently, that means you are using the WordPress editor and you should use the field preference "Copy Once" then you can manually select the term when editing the post in French.
I have read your comments and the documentation you linked but it does not quite seem to resolve my issue.
The problem is that a Taxonomy field gets copied differently depending on if it is in a repeater field or not.
I tested using the "+" to add a translation, used the WPML Translation Editor and not duplicating, for a post that just had a title, taxonomy field, and repeater with a taxonomy field. I went into the WPML editor and added a title translation, the rest of the fields were set to copy. When I checked the resulting data the title was good, the taxonomy field on it's own had the En term id stored in the En post and the Fr term id stored in the Fr post but the taxonomy field in the repeater had the En term id in both the En and Fr posts.
So this is the same issue using the WPML Translation Editor as well as the WordPress editor.
Clearly a taxonomy field on it's own will be copied to the translation using the appropriate translated term when the post is being translated independently and I would expect it to handle the copy of a taxonomy field in a repeater the same way but for some reason in repeaters it just copies the "main" language term id into all the other languages.
I feel like the way the taxonomy field on it's own is being copied is the correct way it should be handled but are you saying that the taxonomy field on it's own is being copied wrong and it should only ever copy the main language id to the other languages?
It seems the Fr post has the Fr term ids when the post is still marked as a duplicate but then I cannot add a translation for the rest of the fields so I do not think this is a solution. If I try to add a translation it will force me to set it to translate independently.
Does this give you a better idea of what my issue is?
Checking the database, I see the subfield taxonomy value in a repeater field is copied exactly to the translation post (raw value) without adjusting with the translation term ID. I'm asking our 2nd tier support about this issue and update you here when I have something to share.
This issue has been escalated to our developer team. I will update you here once I have any information. Meantime, please set the field preference to "Copy Once" or "Translate" and select the taxonomy manually when editing the translation post.
Hi, I just wanted to check in since it has been more than a week since I last heard anything on this issue.
It would be great to hear if any progress has been made on this issue.
Our development team is checking the issue and currently, there isn't a solution to fix it. Please use the workaround I suggested above: set the field preference to "Copy Once" or "Translate" and select the taxonomy manually when editing the translation post.
I will get back to you when I have any information. Thanks.
So just checking in again after another couple weeks of no news.
I just want to confirm, 2 weeks ago you said that currently there isn't a solution and that the development team is checking the issue. Does that mean that a solution is being worked on and we can expect a fix eventually? And if so is there any idea of when it might be available?
We are working around the issue but it is quite inconvenient so a fix would be appreciated.
It has been more than 2 months since we opened this issue and more than a month without any update. I just want to confirm has your development team taken a look and the issue and at least said when they are going to fix this bug?
