When you have a module with your own data, you can implement it and define (field/filter) handlers for it. But what if you want to override a default handler for all views?

For example: handler views_handler_filter_in_operator is used for views a,b and c, etc and I want to replace the basic views_handler_filter_in_operator handler for all these views.

Why do I want this? I'm writing a module where it is possible to have checkboxes and radios in exposed filter. In the $this->query->add_where-statement there is the use of array_values. And when used in combination with radios then this value is a string. This is one of the last bumbs in the road before I can continue on a module than can be tested on the big audience. Here is already a taste of it (see screenshot). http://drupal.org/project/views_filter_pack

I thank you in advance

CommentFileSizeAuthor
Screenshot.png190.6 KBpeter-boeren

Comments

dawehner’s picture

When you have a module with your own data, you can implement it and define (field/filter) handlers for it. But what if you want to override a default handler for all views?

I think you could manage to do this with a hook_views_data_alter(&$view); you would have to scan through all definitions and replace the filter handlers if needed.

esmerel’s picture

Status: Active » Closed (fixed)

no response to suggested fix