Getting Search row style to work

I don’t know about using theme('search_result') but another thing that I found is that in template_preprocess_views_view_row_search() we need to set the $node->build_mode

EG:

function template_preprocess_views_view_row_search(&$vars) {
  // ...
  $node = node_load($nid);

  if (empty($node)) {
    return;
  }
  
  $node->build_mode = NODE_BUILD_SEARCH_RESULT;
  // ...
}

@ambientdrup
This is all the files you need to deal with.

views/modules/search.views.inc
views/theme/views-view-row-search.tpl.php

@ptitb
To get the snippet to work I do the following. I also don't know what the best way is.
Your way looks simpler and I am hard coding the Filter identifier.

  // Get filter keys from views object
  // Need to find a way not to hard code 'keys'
  if (!isset($vars['filter_options'])) {
    $vars['filter_options'] = $vars['view']->display_handler->handlers['filter']['keys'];
  }
  // Reduce memory
  if (isset($vars['filter_options']->view)) {
    unset($vars['filter_options']->view);
  }
  // Set search identifier
  $vars['identifier'] = $vars['filter_options']->options['expose']['identifier'];
  
  $vars['snippet'] = search_excerpt($vars['view']->exposed_data[$vars['identifier']], $node->body);

The attached patch is what works best for me after some more experimentation.
This patch does not address merlinofchaos point in #2.

Please note that normally I generate patches with winmerger but this patch was made with Kompare on Suse and it’s my first time using Kompare.

@dereine
No, that is only relevant to shared hosts that don’t give you enough memory to output view objects to screen while debugging. It can safely be removed.

@dereine
I was using dsm() and I was about the to ask about the difference when I saw that dsm() is now considered a legacy function. Thanks.

Using Views 2.12 and the latest patch from #19 I ran into some minor problems.

First I got include errors.

warning: include(./sites/all/modules/views/theme/search-result.tpl.php) [function.include]: failed to open stream: No such file or directory in

I solved this by copying the search modules search-result.tpl.php into the views/theme directory. I assume putting it into my theme would also solve this error.

But then I ran into the same problem that Dasha_V ran into. I put his workaround into the views/theme/search-result.tpl.php.

I also tried the search-results.tpl.php with the correct filename "views-view" prefix, that also did not work.

It looks like we need a preprocess function for something, to change the template file being used to the search modules template file and to extract the correct variables.

To get the info variables working in the tpl file I also changed the render function to build the info variables.

    $info = array(
      'type' => check_plain(node_get_types('name', $node)),
      'user' => theme('username', $node),
      'date' => $node->changed,
    );    
    if (isset($extra) && is_array($extra)) {
      $info = array_merge($info, $extra);
    }    
    $result = array(
      'link' => url('node/' . $nid, array('absolute' => TRUE)),
      'type' => $info['type'],
      'title' => $node->title,
      'user' => $info['user'],
      'date' => $node->changed,
      'node' => $node,
      'extra' => $extra,
      'score' => $score,
      'snippet' => $snippet,
      'info' => implode(' - ', $info),
      'info_split' => $info,
    );

Is there a reason we are doing this. If we are suppose to divide the score by the total, should the total not be relative the view instead of the entire node table. If this is correct should we not be using a static cache for this query.

    if ($this->options['score']) {
      if ($total = db_result(db_query('SELECT COUNT(*) FROM {node} WHERE status = 1'))) {
        $score = $row->score / $total;
      }
    }

If anybody is interested the attached patch is how I hacked D7 to get it to work. Its mostly based on the above. It should only work for nodes, but with the entity systems it should be possible to make it work for any entity.