Result count

Hi Quinten.

Search Lucene API uses the standard global pager variables, so you have access to all this information. See the code below:

/**
 * Some function.
 */
function myfunction() {
  global $pager_page_array, $pager_total, $pager_total_items;

  // total number of items in result set.
  $pager_total_items[0];

  // total number of pages in the result set
  $pager_total[0];

  // the current page number
  $pager_page_array[0];

  // number of items per search results page
  luceneapi_variable_get('luceneapi_node', 'results_per_page');

}

You can use this information in your display logic to do what you illustrated above.

Thanks,
Chris

P.S to get the offset and first item, you would have to do the following:

/**
* Some function.
*/
function myfunction() {
  global $pager_page_array;

  // the current page number
  $page = $pager_page_array[0];

  // number of items per search results page
  $limit = luceneapi_variable_get('luceneapi_node', 'results_per_page');

  // zero based offset
  $offset = $limit * $page;

  // first item
  $first_item = $offset + 1;
}

Hi Quentin.

You do not want to modify the Search Lucene API files. It is generally bad practice to modify Drupal core code and contributed modules because it introduces unintended bugs and breaks upgrade paths. See the following post for more info : http://drupal.org/node/144376. Fortunately Search Lucene API does implement theme hooks fairly well, so you are able to modify what is displayed in a custom theme. Unfortunately a theming tutorial is out of the scope of this support request, but I will point you to the post at http://adaptivethemes.com/theme-your-search-results for a quick overview on how you can get this information into your templates. The pagination variables described above will be set in the preprocess function, and you can chose where to display it in the custom template.

Hope this points you in the right direction,
Chris

This is a bit off topic but another neat idea to expand on this would be by adding the words the user is searching for by using something like search_get_keys() I assume. That way you get the full phrase.

So you could have "(x-amount) results found for (my entered search term)."

Marking as closed after a long period of inactivity.