I have a content type which has various content taxonomy fields, the widgets which I'm using are checkboxes and a select list. Now when I depublish content which has been published before, all vocabulary selections disappear and they have to be re-entered. I'm able to reproduce this issue using all my content types. Is anyone else experiencing this?
Comments
Comment #1
mh86 commentedHi!
I cannot reproduce it yet, but this is maybe connected to a small error in the updating hook, which has been fixed today.
Comment #2
mjlassila commentedThis problem persists, taxonomy selections are gone when node is first published and then de-published. They don't show up when doing print_r of node contents. Is there something I could do to hunt down this bug?
Comment #3
dnbsecrets commentedthe problem appears with reverting version of node. i think the reason is the same.
that's very critical bug, making this module useless in some cases.
Comment #4
grafixfarm commentedI subscribe to this thread.
When editing a node with taxonomy - it does not remember values initially selected on creation of node.
Example, Hierarchical Select for dropdown select. When editing the node, the select values initially select do not automatically appear as default selections in Hierarchical Select (HS) dropdown.
Could this be specific to HS or is it related to taxonomy. I suspect taxonomy may be culprit.
Any help would be appreciated.
Comment #5
abhaga commentedI have the same problem when using workflow module. On changing workflow state from the workflow tab, all the values in CCK Taxonomy field are lost.
I think the basic reason is that CCK Taxonomy doesn't play well with node_save. Workflow tab calls node_save and that messes things up.
Comment #6
geek-merlinsubscribing
Comment #7
bcn commentedsubscribing
Comment #8
renata-1 commentedAnyone has found a solution for this issue?
I don´t wanna disable the function Revert....
Comment #9
magnus commentedCleanup of old issues. According to maintainer: "active development is only done for the 6.x branch! 5.x is not supported any more".
Open a new issue if problem still exist.