function user_relationship_implications_edit_submit in User Relationships 5.2

Same name and namespace in other branches

1. 5 plugins/user_relationship_implications/user_relationship_implications.module \user_relationship_implications_edit_submit()
2. 6 user_relationship_implications/user_relationship_implications.module \user_relationship_implications_edit_submit()
3. 7 user_relationship_implications/user_relationship_implications.module \user_relationship_implications_edit_submit()

Edit relationship type submission processor

File

plugins/user_relationship_implications/user_relationship_implications.module, line 161

Drupal Module: User Relationship Implications

Code

function user_relationship_implications_edit_submit($form_id, &$form_values) {

  // the rtid is in a different place when adding a new type vs. editing an existing type
  if (isset($form_values['relationship_type']) && !is_null($form_values['relationship_type'])) {

    // editing an existing relationship type
    $rtid = $form_values['relationship_type']->rtid;
  }
  else {

    // adding a new relationship type - go figure
    $rtid = $form_values['rtid'];
  }
  db_query("DELETE FROM {user_relationship_implications} WHERE rtid = %d", $rtid);
  foreach ($form_values['implications']['opts'] as $implied_rtid => $elements) {
    if ($elements["implies_{$implied_rtid}"]) {
      $strict = $elements["implied_{$implied_rtid}_strict"] ? 1 : 0;
      $reverse = $elements["implied_{$implied_rtid}_reverse"] ? 1 : 0;
      db_query("INSERT INTO {user_relationship_implications} (riid, rtid, implies_rtid, strict, reverse) VALUES (%d, %d, %d, %d, %d)", db_next_id('{user_relationship_implications}_id'), $rtid, $implied_rtid, $strict, $reverse);
    }
  }
}