function views_handler_filter_in_operator::value_submit
3.x views_handler_filter_in_operator.inc | views_handler_filter_in_operator::value_submit($form, &$form_state) |
2.x views_handler_filter_in_operator.inc | views_handler_filter_in_operator::value_submit($form, &$form_state) |
Perform any necessary changes to the form values prior to storage. There is no need for this function to actually store the data.
Overrides views_handler_filter::value_submit
2 methods override views_handler_filter_in_operator::value_submit()
- views_handler_filter_term_node_tid::value_submit in modules/
taxonomy/ views_handler_filter_term_node_tid.inc - Perform any necessary changes to the form values prior to storage. There is no need for this function to actually store the data.
- views_handler_filter_user_name::value_submit in modules/
user/ views_handler_filter_user_name.inc - Perform any necessary changes to the form values prior to storage. There is no need for this function to actually store the data.
File
- handlers/
views_handler_filter_in_operator.inc, line 279 - Definition of views_handler_filter_in_operator.
Class
- views_handler_filter_in_operator
- Simple filter to handle matching of multiple options selectable via checkboxes
Code
function value_submit($form, &$form_state) {
// Drupal's FAPI system automatically puts '0' in for any checkbox that
// was not set, and the key to the checkbox if it is set.
// Unfortunately, this means that if the key to that checkbox is 0,
// we are unable to tell if that checkbox was set or not.
// Luckily, the '#value' on the checkboxes form actually contains
// *only* a list of checkboxes that were set, and we can use that
// instead.
$form_state['values']['options']['value'] = $form['value']['#value'];
}