Content Taxonomy is not saved when "cck" or "both" are specified

you have to execute node_submit before node_save because in node_submit the terms get added to the field array

seems there is a problem when trying to save the nodes manually.
the problem only occurs when saving the field in the cck way (or both).
I took a quick look into to code an tried to fix it. I attached the patch. Try it out, but I'm not absolutely sure if this can have any other sideeffects.

I was having the exact same problem. Neither node_submit nor this patch seemed to make a difference. For now, just switching to tag saving works for me.

I am having the same issue. It is very frustrating. I am going to test out this patch.

Chris

Same problem for me (saving both, freetagging).

Trying to add a content in my content-taxononmy-fields (three different textfields for three different vocabluarys): only the content of the first field is added to my vocabluary an printed out in the node. The second and third field seems not to work. However this occurs after around 15 or 20 nodes. Everything works fine before.
And it works when the tag has already been added in the vocabulary! Unfortunately there a many new terms to add publishing new nodes.

And all my added tags disappear (at least they are not shown in the node) after changing some fields or workflows for this content type.

Is there somebody who knows why this error occurs and how to fix this? Step by step for a noob like me, please?

I have this issue too. And this patch is not work.

I found that structure of content_taxonomy from node_load is differ when you insert it back.

If you want to insert this

[field_issues] => Array
        (
            [0] => Array
                (
                    [14] => stdClass Object
                        (
                            [tid] => 14
                            [vid] => 3
                            [name] => Family
                            [description] => 
                            [weight] => 0
                        )

                )

        )

just use this

[field_issues] => Array
        (
            [14] => Array
                (
                    [value] => 14
                )

        )

I'm having similar problem, patch in #5 not works for me. :(

Subscribing

Subscribing.

Nobody has a working patch for this problem? Thank you.

Unfortunately Drupal 5 is not supported anymore, so this will probably not get fixed unless someone who is using the module in D5 themselves comes up with a fix and shares it.

Similar issue, but the other way around: #150117: neither in TAG neither in CCK Table.

Other issues related to saving nodes programmatically rather than through the node edit UI (some are from the D6 branch):
#743920: allow programmatic save of node via drupal_execute
#176762: how to programmatically assign to a "save as both" CT field
#354975: Adding values with drupal_execute()
Maybe #754512: If a term is entered into a content tax field, and node created, value saved but field not populated on edit node?

Thank you for your responses. I'm using Drupal 6, but apparently the problem is still relevant. I'll look into the links if I find the solution. Again thank you.

Using Drupal 6 and having the same problem.

I also use Hierarchical Select.

Re: #17/#18 (and maybe #12/#13 too) -- I'm not sure how it could be the same problem in 6.x? The setting options described in the title don't exist anymore. I'd suggest opening a new issue with a full description of your problem in that case. Be sure to indicate in the new issue how your vocab is configured, how your field is configured, which widget you're using, and whether you're editing the node normally with the node edit form or by some other means.

Cleanup of old issues. According to maintainer: "active development is only done for the 6.x branch! 5.x is not supported any more".
Reopen issue if problem still exist in 6.x branch.

I have a patch to fix this one on Drupal5, if anyone is interested:

In content_taxonomy.module under content_taxonomy_field() function add the following new case to the code:

      // if cck field was set to be saved as 'both' (on cck table as well),
      // then if node was saved via code (node_save()) and not via the node/edit form, this info was lost.
      // For example, when using the workflow history tab.
      
      // The fix is:
      // this hook with 'update' is called just before content_field() on content.module, that does the actual saving to DB.
      // When coming from node edit form, since form is submitted, the syntax of $node_field is: 
      // array(tid => array('value' => tid));
      // But, if called from node_save, the syntax is :
      // array(0 => array(tid => term_object)).
      // So we convert from one format to the other...
      // --------------------------------------------------------------------------------------------------------------------
    case 'update': 
        if (!isset($field['save']) || $field['save'] != 'both')
            return;
             
        // Check if $node_field is in the wrong format
        // --------------------------------------------
        $is_rebuild_node_field = FALSE;
        foreach($node_field as $tid => $tid_value) {
            if(!$tid && count($tid_value)) {
                foreach($tid_value as $internal_tid => $term_data) {
                    if($internal_tid && is_object($term_data) && isset($term_data->tid)) {
                        $is_rebuild_node_field = TRUE;
                        break;   
                        
                    }
                }
                
            }
        }

        // In wrong format - convert it to the right format
        // -----------------------------------------------------
        if($is_rebuild_node_field) {
          $node_field = array();
          foreach($node->taxonomy as $tid => $term) {
               if($term->vid == $field['vid']) {
                   $node_field[$term->tid] = array('value' => $term->tid);
               }
          }
          $node->{$field['field_name']} = $node_field;
        }

I tested it and it solves the problem completely.
See the comment inside the code to understand what it works and what it does.