class views_handler_relationship_translation in Views (for Drupal 7) 6.2
Same name and namespace in other branches
- 6.3 modules/translation/views_handler_relationship_translation.inc \views_handler_relationship_translation
- 7.3 modules/translation/views_handler_relationship_translation.inc \views_handler_relationship_translation
Handles relationships for content translation sets and provides multiple options.
Hierarchy
- class \views_object- class \views_handler
 
Expanded class hierarchy of views_handler_relationship_translation
1 string reference to 'views_handler_relationship_translation'
- translation_views_data_alter in modules/translation.views.inc 
- Implementation of hook_views_data_alter().
File
- modules/translation/ views_handler_relationship_translation.inc, line 7 
View source
class views_handler_relationship_translation extends views_handler_relationship {
  function option_definition() {
    $options = parent::option_definition();
    $options['language'] = array(
      'default' => 'current',
    );
    return $options;
  }
  /**
   * Add a translation selector.
   */
  function options_form(&$form, &$form_state) {
    parent::options_form($form, $form_state);
    $options = array(
      'all' => t('All'),
      'current' => t('Current language'),
      'default' => t('Default language'),
    );
    $options = array_merge($options, locale_language_list());
    $form['language'] = array(
      '#type' => 'select',
      '#options' => $options,
      '#default_value' => $this->options['language'],
      '#title' => t('Translation option'),
      '#description' => t('The translation options allows you to select which translation or translations in a translation set join on. Select "Current language" or "Default language" to join on the translation in the current or default language respectively. Select a specific language to join on a translation in that language. If you select "All", each translation will create a new row, which may appear to cause duplicates.'),
    );
  }
  /**
   * Called to implement a relationship in a query.
   */
  function query() {
    // Figure out what base table this relationship brings to the party.
    $table_data = views_fetch_data($this->definition['base']);
    $base_field = empty($this->definition['base field']) ? $table_data['table']['base']['field'] : $this->definition['base field'];
    $this
      ->ensure_my_table();
    $def = $this->definition;
    $def['table'] = $this->definition['base'];
    $def['field'] = $base_field;
    $def['left_table'] = $this->table_alias;
    $def['left_field'] = $this->field;
    if (!empty($this->options['required'])) {
      $def['type'] = 'INNER';
    }
    $def['extra'] = array();
    if ($this->options['language'] != 'all') {
      switch ($this->options['language']) {
        case 'current':
          $def['extra'][] = array(
            'field' => 'language',
            'value' => '***CURRENT_LANGUAGE***',
          );
          break;
        case 'default':
          $def['extra'][] = array(
            'field' => 'language',
            'value' => '***DEFAULT_LANGUAGE***',
          );
          break;
        // Other values will be the language codes.
        default:
          $def['extra'][] = array(
            'field' => 'language',
            'value' => $this->options['language'],
          );
          break;
      }
    }
    if (!empty($def['join_handler']) && class_exists($def['join_handler'])) {
      $join = new $def['join_handler']();
    }
    else {
      $join = new views_join();
    }
    $join->definition = $def;
    $join
      ->construct();
    $join->adjusted = TRUE;
    // use a short alias for this:
    $alias = $def['table'] . '_' . $this->table;
    $this->alias = $this->query
      ->add_relationship($alias, $join, $this->definition['base'], $this->relationship);
  }
}Members
| Name   | Modifiers | Type | Description | Overrides | 
|---|---|---|---|---|
| views_handler:: | function | Take input from exposed filters and assign to this handler, if necessary. | 1 | |
| views_handler:: | function | Check whether current user has access to this handler. | 5 | |
| views_handler:: | function | Provide text for the administrative summary | 3 | |
| views_handler:: | function | Determine if the handler is considered 'broken', meaning it's a a placeholder used when a handler can't be found. | 5 | |
| views_handler:: | function | Determine if a handler can be exposed. | 1 | |
| views_handler:: | function | Ensure the main table for this handler is in the query. This is used a lot. | 7 | |
| views_handler:: | function | Render our chunk of the exposed filter form when selecting | 1 | |
| views_handler:: | function | Get information about the exposed form for the form renderer. | 1 | |
| views_handler:: | function | Submit the exposed filter form | ||
| views_handler:: | function | Validate the exposed filter form | 4 | |
| views_handler:: | function | Set new exposed option defaults when exposed setting is flipped on. | 1 | |
| views_handler:: | function | Provide defaults for the handler. | ||
| views_handler:: | function | Provide a form for setting options. | 1 | |
| views_handler:: | function | 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:: | function | Validate the options form. | ||
| views_handler:: | function | Get the join object that should be used for this handler. | ||
| views_handler:: | function | If a handler has 'extra options' it will get a little settings widget and another form called extra_options. | 1 | |
| views_handler:: | function | Determine if this item is 'exposed', meaning it provides form elements to let users modify the view. | ||
| views_handler:: | function | Determine if the argument needs a style plugin. | 1 | |
| views_handler:: | function | Perform any necessary changes to the form values prior to storage. There is no need for this function to actually store the data. | 1 | |
| views_handler:: | function | Validate the options form. | 1 | |
| views_handler:: | function | Run before the view is built. | 1 | |
| views_handler:: | function | Called just prior to query(), this lets a handler set up any relationship it needs. | ||
| views_handler:: | function | If set to remember exposed input in the session, store it there. | 1 | |
| views_handler:: | function | Return a string representing this handler's name in the UI. | 5 | |
| views_handler:: | function | Validates the handler against the complete View. | ||
| views_handler_relationship:: | function | Init handler to let relationships live on tables other than
the table they operate on. Overrides views_handler:: | ||
| views_handler_relationship:: | function | Get this field's label. | ||
| views_handler_relationship_translation:: | function | Add a translation selector. Overrides views_handler_relationship:: | ||
| views_handler_relationship_translation:: | function | Information about options for all kinds of purposes will be held here. Overrides views_handler_relationship:: | ||
| views_handler_relationship_translation:: | function | Called to implement a relationship in a query. Overrides views_handler_relationship:: | ||
| views_object:: | property | Except for displays, options for the object will be held here. | 1 | |
| views_object:: | function | Views handlers use a special construct function so that we can more easily construct them with variable arguments. | 5 | |
| views_object:: | function | 2 | ||
| views_object:: | function | Set default options on this object. Called by the constructor in a complex chain to deal with backward compatibility. | 1 | |
| views_object:: | function | Set default options. For backward compatibility, it sends the options array; this is a feature that will likely disappear at some point. | ||
| views_object:: | function | Let the handler know what its full definition is. | ||
| views_object:: | function | Unpack options over our existing defaults, drilling down into arrays so that defaults don't get totally blown away. | ||
| views_object:: | function | 1 | 
