Edit/re-save computed field set to 'multiple' loses $node_field[1], $node_field[2], ..

That is incorrect. I can handle the field computing on subsequent editing -- I want to, in fact, so I can verify the values computed before and change them if necessary. The form is being changed, and my computed value relies on other fields, so being able to execute on edit is a necessity.

The problem is this morsel of code.

/**
 * Implementation of cck hook_widget
 */
function computed_field_widget($op, &$node, $field, &$node_field) {
  switch ($op) {
    case 'form':
      $form = array();

      $form[$field['field_name']] = array('#tree' => true);

      $form[$field['field_name']][0]['value'] = array(
        '#type' => 'value',
        '#title' => t($field['widget']['label']),
        '#default_value' => isset($node_field[0]['value']) ? $node_field[0]['value'] : '',
      );
      return $form;
  }
}

.. because of this:

$form[$field['field_name']][0]['value'] = array( ..trunc.. )

.. my computed_field code only has access to $node_field[0].

I need access to the complete array $node_field ([ 0, 1, 2, 3, .. etc ]) .. ['value'].

Here is my computed_field code to demonstrate (still a revision or two from final):

srand((double)microtime()*1000000);

$chars = 'ABCDEFGHJKLMNPRSTUVWXYZ23456789';
$clen = 8;
$spos = 4;
$schar = '-';
$fname = 'field_code_generator';

if (!$node_field[0]['value']) $node_field = array();

while (sizeof($node_field) < $node->field_total_codes[0]['value']) {
  $code .= substr($chars, rand()%33, 1);
 
  if (strlen($code) >= $clen):     
    $code = trim(chunk_split($code, 
                  floor($clen/ceil($clen/$spos)), $schar), $schar);

    if ( !in_array( array('value' => $code), $node_field ) &&
         !db_result(db_query("SELECT COUNT(*) FROM {content_%s} WHERE %s = '%s'", $fname, $fname, $code)) ): 
      $node_field[] = array('value' => $code);
    endif;

    $code = '';
  endif;
}

As you can see, I am growing $node_field until it reaches a length set in a Text input field.

The inner code is of little consequence, but we are basically generating a unique hyphen-split 8 character code (thus the SELECT). Once we are certain it's unique, we tack it on the end of $node_field.

If someone were to edit the node and raise field_total_codes by 10 and save, this will add the additional entries onto the end. Because these codes cannot be taken back once they are generated -- they are forever, we do not account for a reduction in field_total_codes.

My patch wraps that single $form[$field['field_name']][0]['value'] = array( ..trunc.. ) into a loop, that iterates through the entirety of $node_field to construct the true value:

      foreach($node_field AS $key => $value) {
        $form[$field['field_name']][$key]['value'] = array(

.. and it seems to work in the old case also. I don't see an ill effect yet, but would like someone else to test.

Thanks,
Jason

Excellent, thank you.