Support for User Search Results

I think you would want to put this in the user display module maybe in a sub-module like ud_search?

Can you post a patch so I can see your code and maybe give you some help?

Swentel,

Would it be safe to assume that the logic would be much like the nd_search module for this ud_search? If that is the case, I can take a stab at it and see what I come up with. (As you can tell from me posting issues on all your modules, and on the apachesolr module pages, I'm building some big solr web apps right now :D )

Thanks!

Swentel, I'll start playing around with this today and let you know my progress.

Swentel, have you ever used Drupal's arg() function? http://api.drupal.org/api/function/arg

I believe you would be able to grab that uid from a url such as localhost/drupal/user/1 using arg(1);

I have tested this on individual user pages and my DPM is displaying the correct data. I tried to implement your code into my user_display.module file with the arg change I have suggested but unfortunately it doesn't seem to change anything, I suppose this is because there is currently no admin interface to enable user display search or should it just override it by default?

Hope that helps!

Cheers,
Donovan

Ugh disregard my last post, I just realized that the arg() function would only help if that user url was the URL in the browser.

<?php
function user_search_page($results) {
  $output = '';

  /*
  if (variable_get('nd_search_preprocess_vars', 'none') != 'none') {
    $variables = array();
    _nd_search_preprocess($variables);
    $output .= '<div class="nd-search-extra">'. $variables[variable_get('nd_search_preprocess_vars', 'none')] .'</div>';
  }*/
  global $base_url;
  
  foreach ($results as $key => $result) {
    // Get uid from $result  - we'll have todo some regexpress on this.
    $subject = $result['link'];
    $pattern = $base_url . "/user/";
    $uid = split($pattern, $subject); 
    // $uid = preg_replace(); // pseudo
    $account = user_load($uid[1]);
    $account->type = 'ds_profile';
    $account->build_mode = 'search';
    user_build_content($account);
    $output .= theme('user_profile', $account);
  }

  $output .= theme('pager', NULL, 10, 0);

  return $output;
}
?>

What do you think of that?

Swentel, even if they do have an alias for their profile, doesn't drupal still generate a /user/ page for that user even though there might be an URL alias to get to that profile?

Ah I see what you mean now, bummer. That condition you suggested should do the trick though.

Swentel, do you think you can post an updated version of the module with the user search support sometime relatively soon?

Swentel, I updated to the latest code and I see the search tab under Display Suite -> Layout -> User -> Search

I have added the fields I wanted, but when I do a search and a user is returned its still the default output which is a link to their profile.

With Node Display Search, there is an option Display Suite -> Node Display -> Nd_Search which then has several configurable options, most importantly the checkbox:

Override search page
Toggle this checkbox if you want to display the result of search with the display suite.

I have enabled this thinking it would help, and yes it removes the default search results and replaces them with DS but on user results it says "undefined" for me even though in the Search build mode for users I've added several fields.

Maybe the search for user display needs a checkbox like that to override the search results with whatever build mode the user selects? Also, the path admin/ds/ud/search just redirects me to the base User Display page.

Perhaps I'm missing a step?

Yeah I see your hook_menu_alter and you have obviously implemented it correctly. I've cleared cache, rebuilt the menu router, tried everything possibly and i still dont get access to that page.

I've looked at a lot of the code now and it all looks good, I'm just not sure where I can't access that page, I'm the super user so it's definitely not a permissions issue. Perhaps I have a conflicting module?

Ah okay I see it now, I should update my DS module then too.

cvs update -dP ftw. :)

Thanks, I'll let you know how it works.

Swentel, it works great with default drupal search, I tried it on my local sandbox and it worked as intended, but for the application I need it for, we are using apache solr search for users. We want to have this application were users can select districts & schools in faceted filters, and then only get their username and email as the result (hence my need for display suite & user display), so when I enabled the module and set it to override user search pages on the solr driven site, it didn't override the results, it still gave me the default ones. Would it be easy for you to add support for apache solr user search?

Btw, here is the apachesolr user search module, http://github.com/SupermanScott/apachesolr_users

Thanks for your help, I seriously owe you like half of my paycheck.

Swentel

The URL is the same as core apachesolr search.

http://localhost/drupal/search/apachesolr_search/

It just allows $users & $user profiles to be indexed and searched by solr.

I'm looking at your nd_search module in the section where you override solr search and seeing how I can implement it with the ud_search.

here is a screenshot of a DPM of one of the $result objects passed to the

function apachesolr_search_search_page($results)

Maybe this will help you....

Well Swentel, I finally got off my lazy arse and did it myself. I think I got it to work.

Here is the new function I added to the ud.module

<?php
/**
 * Implementation of hook_search_page for apache solr search.
 */
if (variable_get('ud_override_search_page', FALSE)) {
  function apachesolr_search_search_page($results) {
    $output = '';
    // Search form. 	 
    $type = 'apachesolr_search';
    $keys = trim(search_get_keys()); 
    $output .= drupal_get_form('search_form', NULL, $keys, $type);
    
    // Search results
    if (variable_get('nd_search_apachesolr_show_title', FALSE)) {
      $output .= '<h2>'. t('Search results') .'</h2>';
    }

    if (variable_get('nd_search_preprocess_vars', 'none') != 'none') {
      $variables = array();
      _nd_search_preprocess($variables);
      $output .= '<div class="nd-search-extra">'. $variables[variable_get('nd_search_preprocess_vars', 'none')] .'</div>';
    }

    // Content.
    foreach ($results as $key => $result) {
      dpm($result);
      $uid = $result['fields']['uid']['value'];
      dpm($uid);
       if (is_numeric($uid)) {
          $account = user_load($uid);
          if ($account->uid) {
            $account->type = 'ds_profile';
            $account->build_mode = 'search';
            user_build_content($account);
            $output .= theme('user_profile', $account);
          }
      }
    }

    // Pager
    $output .= theme('pager', NULL, variable_get('apachesolr_rows', 10), 0);

    return $output;
  }
}
?>

I'll have to test it with the normal node search, the system I need the apachesolr user search though will probably only be for searching users though. It would be nice to make this flexible to work both ways though.

It can be set to fixed, but I'd like you to implement this code for the 1.3 release so I don't have to use a "hacked" version of the module.

Swentel, after some quick testing it seems like node search results are replaced by the buildmode that user search results are using...

Do you think there is a way we can detect if it's a user or node result and then load the appropriate build mode for that content type? edit: if you look at the dpm($result); you will see that there is a type attribute in the $result object. It is always NULL for users, and if it's a node, it should have the content type in there. Perhaps this is how we can check if it's a user or a node and then load the search result build mode for whatever content type it is.

Swentel, I got the latest code for nd_contrib (for nd_search) and reverted my ud.module. It's working great man, this is exactly what I wanted. Thanks for all your time and help. If you ever need help maintaining these modules I'd be more than happy to help out, I've got a good grasp of the code now. :)

Now, I just need to get faceted filters for CCK fields that are in a node (content_profile module) to show up for when the users are returned so that's what I'll be working on for the next few days.

Thanks again Swentel, I couldn't have done this without you.