Hello!
I've configured my site with WPML plugins and ACF for custom fields. Site default language is Italian.
I don't want my custom taxonomies to be syncronized at all; I've disabled it under WPML > Settings by deactivating "Copy taxonomy to translations" but it doens't work.
Maybe because I preaviously enabled it and I need to clear WPML cache?
Now it works in this way:
- I create the single custom post type object and associate it with my custom taxonomy in Italian
- I create the English translation of the post type: WordPress classic or advanced editor needs the taxonomy association: if I copied from Italian, the taxonomy is created in English but I don't need it; if I manually add the name of the taxnomy, WPML duplicates it (it doesn't recognize I've already created it and doesn't make the association).
Can you help me to solve this issue?
Thanks,
Emanuela
This is not the expected behaviour in my opinion and may be a bug.
I am double-checking this with some senior colleagues and will let you know if I need to escalate this issue.
Thanks for your patience
Ps. The expected behaviour is the following:
- If the category is pre-existing and pre-translated, then creating a new post, assigning a cateogy and translating the post should NOT result in a new translated post with translated category assignment.
The category in this case will NOT appear in the Tranlsation Editor.
- If the cateogry is created at the same time as the post, then when translating the newly created post and category will result the Translation Editor asking you to translate the new cateogry but I would NOT expect it to assign the new translated post to the newly translated category.
This si MY expectation and I am verifying its correctness with development.
Hi Yvette,
thanks for your reply.
This is my test in 2 different situations. Italian is my primary language.
Test 1: product with translated categories
- I create the custom taxonomy and translate it in English
- I create the custom content type in Italian and associate it with the Italian taxonomy
- when I'm in translation editor WPML autocompletes the English translation of the taxonomy
- I publish both content types and it all works fine
Test 2: product with untranslated categories or not synchronized categories
- I create the custom taxonomy, I don't translate it in English: I create a new category for the English version
- I create the custom content type in Italian and associate it with the Italian taxonomy (not translated in English)
when I'm in translation editor WPML want me to add a taxonomy: If I copy the Italian taxonomy, the new taxonomy is created for the English version but I don't need it. If I enter the English category name I really want, WPML creates a duplicated taxonomy!
I attached some screeshots of my tests.
Let me know if you need other information.
Thanks,
Emanuela
Yes this was my finding as well. I can only get my "expected" behaviour that I described earlier by using manual translation (e.g. NOT using the Tranlastion Editor).
I still don´t have the confirmation that this is a bug...but I´m going to go ahead and classify it as such because the documentation is leading both of us to expect the behaviour that is not happening.
I´ll update this ticket once I have word from our developers about this issue.
Yes I do and thank you for proactively writing in.
Apparently, the purpose of this option was to copy the terms when translating and creating new terms when duplicating *manually*. This is still working as we confirmed with the native editor before escalating.
It therefore has no "meaning" when using any of the Translation Editors.
The ticket in 2nd tier support is still "open" as our management is taking a 2nd look at this. But as far as your issue is concerned...I guess the feature/option is only valid/effective when doing manual translations with the native editor.
Perhaps in a future release, the option will be disabled if/when the Tranlsation Editor is enabled
Hello,
it would be great if you can disable this feature: when using Translation Editor category should not be required, so you can associate it with the default editor later, otherwise extra categories will be created (as duplicated categories).
Thanks a lot,
Emanuela
