i18n allows under "Content Type"->"edit" and in the "Synchronize translations" box to check the "Taxonomy terms" for synchronizing taxonomy terms. This is active even if "Taxonomy translation" module is disabled. If "Taxonomy translation" is disabled, when clicking "add translation" for a node under the "Translation" panel, the upcoming form is already filled in with the source node data but the taxonomy terms are not filled in, i.e. synchronisation does not take place.

The problem is resolved once the "Taxonomy translation" is enabled and the vocabulary is set to "None. No multilingual options for this vocabulary.".

The checkbox for synchronising taxonomy terms should not be enabled until the taxonomy translation module is enabled. Or the taxonomy translation module should be pre-requisite for taxonomy synchronisation.

Comments

sp3boy’s picture

sp3boy commented

For what it's worth, I'm finding a similar problem: I want to translate into Italian an English node of a custom content type that has imagefield images, CCK text fields and taxonomy vocabularies.

When I invoke the translation input form, the CCK fields are pre-filled with the values from the English original. As I understand it, as I have not enabled synchronization on any CCK fields of my content type (and Taxonomy translation is disabled), I expect that if I save my Italian node and then re-edit either node and change a CCK fields or image, that change will not be reflected in the node of the other language.

Fair enough. However when I do invoke the translation input form, the taxonomy field is unset. I can manually pick the English node's term from the dropdown list but I don't understand why it's not already the default.

Reading the original post, it looks like setting the synchronization option for the taxonomy won't resolve this unless I install Taxonomy Translation, which I don't actually need.

I am wondering though whether the functionality that should (?) be populating the taxonomy selection is in the internationalization module or the Content Translation module?

cyberwolf’s picture

cyberwolf commented

I fully agree with natuk, the checkbox for synchronising taxonomy terms should not be enabled until the taxonomy translation module is enabled. It's a requirement admins can easily forget about and it's currently not obvious at all from the user interface.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (won't fix)

Cleaning up the issue tracker. Closing all issues that haven't got any follow up for the last year.