Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
hi
'save as tag': all terms assigned to a node get saved to the standard term_node table, which is managed by the taxonomy module. This means that you can use all contributed taxonomy modules like Tagadelic, ...
'save in cck': all terms get saved in a cck table, which gets automatically generated. this may be a bit faster, because of smaller tables (you have your own tables per content type or field), but prevents from using some other contributed taxonomy module.
and before I forget: make this decisions before you start creating nodes with content taxonomy fields assigned, because, switching afterwards, from cck saving to tag saving or the other way round, will cause data loss (it's possible to switch from 'both' to 'tag' or 'cck').
Ok, so if I understand well, if I want that content taxonomy do the job of the core taxonomy select list when I create a node, I should choose 'save as tag'. It will do the same job that if I select terms in the core taxonomy selection isn't it ?
the strange thing is that I try to understand why the i18n translation don't work with content taxonomy, and if the module do the same job that the core taxonomy when I choose "save as tag", the translation should work because it works with the core taxonomy selection.. ?
So I don't understand why the translation don't work with a "save as tag" content taxonomy field.
Comments
Comment #1
mh86 commentedhi
'save as tag': all terms assigned to a node get saved to the standard term_node table, which is managed by the taxonomy module. This means that you can use all contributed taxonomy modules like Tagadelic, ...
'save in cck': all terms get saved in a cck table, which gets automatically generated. this may be a bit faster, because of smaller tables (you have your own tables per content type or field), but prevents from using some other contributed taxonomy module.
and before I forget: make this decisions before you start creating nodes with content taxonomy fields assigned, because, switching afterwards, from cck saving to tag saving or the other way round, will cause data loss (it's possible to switch from 'both' to 'tag' or 'cck').
Comment #2
zmove commentedOk, so if I understand well, if I want that content taxonomy do the job of the core taxonomy select list when I create a node, I should choose 'save as tag'. It will do the same job that if I select terms in the core taxonomy selection isn't it ?
the strange thing is that I try to understand why the i18n translation don't work with content taxonomy, and if the module do the same job that the core taxonomy when I choose "save as tag", the translation should work because it works with the core taxonomy selection.. ?
So I don't understand why the translation don't work with a "save as tag" content taxonomy field.
Comment #3
(not verified) commented