Drupal Programmer

Continuing from Part 1 of the post where we defined custom data table to make drupal aware of our legacy data, we also want to define custom filters that can be used by the views system to define conditional views. in the hook_views_data() or our example code in part one, the candidate_views_data() function you can see that a field was defined as below:     $data [ 'candidate' ][ 'candidate_gender' ] = array (         'title' => t( 'Gender' ),         'field' => array (           'click sortable' => TRUE ,         ),         'filter' => array (             'handler' => 'candidate_handler_filter_gender' ,         ),     ); notice the filter key in the $data array, we want custom data to appear here, for example 'Male' and 'Female', so we have defined a custom handl...

This is a 2 part post, that shows how I exposed a legacy table to views in drupal and used the incredible power of views to create many combinations static and conditional views. This was very helpful for my client. I had a requirement that warranted exposing existing database table to views, so that views can contain data from this table.  To enable this to happen, the following steps need to be taken. In a custom module you need to first define the views_api hook as following: function candidate_views_api(){     $view = array ();     $view = array ( 'api' => 2 ,                   'path' => drupal_get_path( 'module' , 'candidate' ). '/views' );     return $view ; } candidate module was a custom module which I already had, so it made sense to add this hook here.  The important bit here is telling the drupal sub-system where the views file will reside.  ...