Ability to set value of the dependent field

Part of this functionality is already present, though undocumented (I have just committed a fix for a bug that prevented it, so if you want to try download the latest from git).

Here the steps to create a custom jQuery effect when editing fields:

1) Add a new "Effect" to the list supplied by conditional_fields_effects(), by altering the $effects variable:

function MYMODULE_conditional_fields_effects_alter(&$effects) {
  $effects['EFFECT_NAME'] = t('EFFECT DESCRIPTION');
}

2) Edit your dependency, select the new effect, and save. You might have to clear caches from the "Performance" page first to see the new option.

3) When editing the fields, conditional_fields.effect.js will now try to execute a function 'EFFECT_NAME', which you can define as any jQuery plugin. So create a new javascript file, include it either through a custom module or a theme, and fill it with the following:

(function ($) {
  {
    $.fn.EFFECT_NAME = function(e) {
      // You code here...
      // See conditional_fields.effect.js to see examples of how this is implemented with the 'fade' and 'slide' effects.
    };
  }
})(jQuery);

An example: I want the text "LOL!" to be appended before my dependent field any time the dependency is triggered.

1) Create a "lol" module, open lol.module and paste:

function lol_conditional_fields_effects_alter(&$effects) {
  $effects['lol'] = t('LOL!');
}

/**
 * Implements hook_js_alter().
 */
function lol_js_alter(&$javascript) {
  // Include lol.js when conditional_fields.effect.js is present.
  if (isset($javascript[drupal_get_path('module', 'conditional_fields') . '/js/conditional_fields.effect.js'])) {
    drupal_add_js(drupal_get_path('module', 'lol') . '/lol.js');
  }
}

3) Create a file lol.js and place it in the module folder. Paste:

(function ($) {

{
  $.fn.lol = function(e) {
    this.closest('.form-item, .form-submit, .form-wrapper')[e.value ? 'show' : 'hide']().before('LOL!');
  };
}

})(jQuery);

4) Activate the module, select "LOL!" as dependency effect, and voilà!

Please note that CF is still in development, so any of the above may change. I will post here any variation. Soon it will be possible to add behaviors when showing content as well, so you can for example render a dependent in a way when the dependency is triggered, and in another when it's triggered.

I haven't tested, but I think that to implement the new condition you just have to bind a new event to the document, like states.js does:

  $(document).bind('state:CONDITION_NAME', function(e) {
    // ...
  });

This if for example how the "visible" condition is implemented:

  $(document).bind('state:visible', function(e) {
    if (e.trigger) {
      $(e.target).closest('.form-item, .form-submit, .form-wrapper')[e.value ? 'show' : 'hide']();
    }
  });

I mixed up things, sorry. The example in #5 refers to states that can be applied to dependent fields when the dependency is triggered.
If you want to add new "monitoring" functions (called "conditions" in conditional fields), you will have to extend the states.Trigger.states object.

I was just doing so by adding two new useful conditions: focused/blurred and touched/untouched. Ended up with this code:

  focused: function(self) {
    // Attach the event callbacks.
    self.element.bind('focus', function () {
      self.element.trigger({ type: 'state:' + self.state, value: true });
    })
    .bind('blur', function () {
      self.element.trigger({ type: 'state:' + self.state, value: false });
    })
    // Initial state.
    .trigger({ type: 'state:' + self.state, value: self.element.is(':focus') });
  },

  touched: {
    'focus': function(e) {
      return (e === undefined && this.is(':not(:focus)')) ? false : true;
    }
  }

This was done by modifying the module. If you want to add new conditions in a contributed module:

1) Implement MYMODULE_conditional_fields_conditions_alter.
2) Add the following code to javascript when needed:

(function ($) {

// If default states events triggering handling is ok... (like empty, checked, etc...)
{
  Drupal.states.Trigger.states['MY_CONDITION'] = { EVENT_NAME: function(e) {
      // Stuff here...
  }};
} 

// If you need more control... (like focused)
{
  Drupal.states.Trigger.states['MY_CONDITION'] = function(self) {
      // Stuff here...
  };
} 

})(jQuery);

Be sure to use the latest Conditional Fields from git since I just committed a patch that contains the two new conditions and a fix to make "focused" work.

I think the easiest solution to your case is just to implement a new state (NOT a new effect or condition) like outlined in #5:

PHP:

function MODULE_NAME_conditional_fields_states_alter(&$states) {
  $states['hide_and_fill_from_field_2'] = t('Hidden and filled with values from field_2');
}

/**
 * Implements hook_js_alter().
 */
function MODULE_NAME_js_alter(&$javascript) {
  drupal_add_js(drupal_get_path('module', 'MODULE_NAME') . '/MODULE_NAME.js');
}

MODULE_NAME.js:

(function ($) {

$(document).ready(function() {
  $(document).bind('state:hide_and_fill_from_field_2', function(e) {
    if (e.trigger) {
      if (e.value) {
        $(e.target).val($('#edit-field-2-und').val()).closest('.form-item, .form-submit, .form-wrapper').hide();        
      }
      else {
        $(e.target).closest('.form-item, .form-submit, .form-wrapper').show();
      }
    }
  });
});

})(jQuery);

(this js above is buggy and might not give exactly what you expect, but it's a start)

Setup the two dependencies. Descriptions should be something like:
1) field_2 is visible when field_1 has value "B".
2) field_3 is hidden and filled with values from field_2 when field_1 has value: "B".

subscribe

I think this is a much needed feature. As far as I see, with this feature Conditional Fields would also replace the Dependent Fields module which is not ported to D7 and seems inactive.

Can we expect any further development on this soon? Like setting value of the dependent field becoming an official/documented of the feature of the Conditional Fields module?

I wasn't able to get the functionality following the instructions in this thread, so in the meantime further instructions or a patch would be helpful.

Yes this would be useful... Taking it.

@peterpoe: Any progress on this issue? Looking forward to it...

+1

It has been a few months since anything more was said / done in regards to this feature request. I was just curious if there was any further developments?

I see that the Dependent Fields module seems active again.... There was a commit just a few days ago on December 5, 2011. However, there is still no D7 version available. And I highly doubt that there will be since there is an issue pointing back to this post...

In other words, the proverbial ball for D7 functionality of this kind appears to be in Conditional Fields court. So any progress????

I've also have been checking every now and then. Too bad there has been no progress on this issue. I'm looking for ways to work around this module now.

up

Yeah this would be very useful. it appears none of the other options for changing values of dependees works in any module.

Thanks for this module! Has there been any progress on the ability to set the value of the dependent field?

I'm looking to do pretty much the same thing. Would love to hear any ideas or examples. Getting pretty bogged down trying to customize my own module using #states... ugh.
Meanwhile, I can't seem to even get my dependee (a popup date field) to trigger my dependent (an autocomplete field). Thanks.

Has been committed for 8.x and above but forgotten to be set as "fixed". Apart from that:

Thanks for the report and all the efforts in here. But due to inactivity in this issue for some years and because of the upcoming EOL of Drupal 7, I will close this issue on the way by cleaning up the issue queue.

Feel free to re-open as "Needs review" if you found a solution or have a patch to be reported to help others on this outdated version.

If you think this issue or missing feature should be addressed in a newer Drupal core 8 and above compatible version of this project, then please file a new issue to the latest dev.