I am trying to: use a not translatable custom taxonomy for a custom post type Events. So I've created a new custom post type "Events" which is translatable (use translation if available or fallback to default language) and then a custom taxonomy "event_categories" assigned to this custom post type, and it is set as not translatable.
Created one event taxonomy "Webinars" which should be used for every language.
Link to a page where the issue can be seen: -- dashboard -- see screenshots
I expected to see: "Webinars" custom taxonomy only once (EN) and not translated. Discovered yesterday when I tried to add an event (webinar) and I got to choose between 5 "Webinars" custom taxonomies.
Instead, I got: As seen in the screenshot, the event custom taxonomy got translated (automatically!?) in all languages, which should not be happening!
BTW, this is the second time it happened, and to fix it, I got to manually remove the translated custom taxonomies But i would like not to happen again.
Thanks for contacting WPML forums support. I'll be glad to help you today.
First of all, sorry for the late reply due to a higher workload. Suppose this custom taxonomy was set to translatable before, and you translated one post. In that case, the taxonomy term will be translated, and the fix for this issue is to delete the translated terms manually after setting the taxonomy to "Not Translatable".
In order to test this, please create a new term named "WPML Test" and a test post named "WPML Test Post". After that, please translate the post and check if the "WPML Test" will be duplicated/translated.
Hi,
no, the custom taxonomy was never set to translatable before.
I've made that test and the custom taxonomy doesn't get translated, which is the right behaviour.
With that said, I still see sometimes that custom taxonomy magically translated and I don't really understand the reason.
Thanks for your update and for doing the test. I'm not sure how these taxonomies are duplicated because you said it was never set to be translatable.
Hence the test worked as expected; the workaround to fix this issue is to delete the duplicated taxonomies.
After deleting them, please check if the translated posts have the correct taxonomy. If they haven't the correct one, please update the post in the default language to check if the taxonomy is copied.
Thanks,
Osama
The topic ‘[Closed] Custom taxonomy got translated even if it's set as not translatable’ is closed to new replies.
