Customizing View + exposed filter <= How to make the added class executed?

Changing the query ( CONTAIN ANY WORDS ...) is about changing the construction of the SQL. This is related to the Filter object.

I changed code directly (views_handler_filter_string class) and add the new operator successfully. Now I would like to implement it in the way of the child class of views_handler_filter_string, instead of changing it directly.

So, I created Mymodule and do the following:

I do the following:
1) register my module to views by implementing views_api()

function tcfilter_views_api()
{
  return array(
    'api' => 2,
    'path' => drupal_get_path('module', 'MYMODULE') . '/inc',
  );
}

2) implement the class MYMODULE_handler_filter_MYFILTER (extends views_handler_filter_string), and overide the functions related to my modification. Since I just would like to add one option to the operator to the exposed filter, there is not much to change for the form.

3) In Mymodule_views_handlers() register the object to the parent,
'parent' => 'views_handler_filter_string',.

function MYMODULE_views_handlers() {
  return array(
    'info' => array(
      'path' => drupal_get_path('module', 'MYMODULE') . '/inc',
    ),
    'handlers' => array(
      // The name of my handler
      'MYMODULE_handler_filter_MYFILTER' => array(
        // The name of the handler we are extending.
        'parent' => 'views_handler_filter_string',
      ),
    ),
  );
}

However, after the module enabled without errors, the code (number 2 step) is not executed. I miss something here? Anyone knows the problem? Thanks.

Hosais

Changing this to coding issue.

Fantastic! Genial! Thank you dereine.

With your help, I found the definition of handler in node.view.inc.

$data['node']['title'] = array(
    'title' => t('Title'), // The item it appears as on the UI,
    'help' => t('The title of the node.'), // The help that appears on the UI,
     // Information for displaying a title as a field
    'field' => array(
      'field' => 'title', // the real field. This could be left out since it is the same.
      'group' => t('Node'), // The group it appears in on the UI. Could be left out.
      'handler' => 'views_handler_field_node',
      'click sortable' => TRUE,
     ),
    'sort' => array(
      'handler' => 'views_handler_sort',
    ),
    // Information for accepting a title as a filter
    'filter' => array(
      'handler' => 'views_handler_filter_string',
    ),
    'argument' => array(
      'handler' => 'views_handler_argument_string',
    ),
  ); 

After modifying handler in hook_views_data_alter(&$data), it works.

hosais

OK.

About "I would like to reuse the exposed filter in a link. That is, I am interested passing arguments in URL to the exposed view filter.", I think it was discussed at Pull filter value from an argument (http://drupal.org/node/357082).

hosais

Hi,

I just finished tracing the code and conclude my little module. To pass the argument to filter, the key point is

1) disable query of argument handler (Not add where clause);
2) let the filter handler read the argument to value property of a view(for example, $this->value = $this->view->args[0];). The code could be put into per_query().

hosais