Actually, if you like to search by groups you can do it like this:
Code:
if ($vbulletin->GPC['searchuser'])
{
// username too short
if (!$vbulletin->GPC['exactname'] AND strlen($vbulletin->GPC['searchuser']) < 3)
{
$errors[] = 'searchnametooshort';
}
else
{
if ( $vbulletin->GPC['searchuser'] == 'devtracker' )
{
$aDevGroups = Array ( 1, 2, 3 );
$q = 'SELECT posts, userid, username FROM `' . TABLE_PREFIX . 'user` where usergroupid IN ( ' . implode ( ',', $aDevGroups ) . ') ';
foreach ( $aDevGroups as $nDevGroup )
$q .= ' OR concat( membergroupids,"," ) LIKE "%' . $nDevGroup . ',%"';
}
else
{
$username = htmlspecialchars_uni($vbulletin->GPC['searchuser']);
$q = "
SELECT posts, userid, username
FROM " . TABLE_PREFIX . "user AS user
WHERE username " .
($vbulletin->GPC['exactname'] ?
"= '" . $db->escape_string($username) . "'" :
"LIKE('%" . sanitize_word_for_sql($username) . "%')"
)
;
}
require_once(DIR . '/includes/functions_bigthree.php');
$coventry = fetch_coventry();
The green section is what you should add in the
search.php file, note that you need to replace the
$aDevGroups = Array ( 1, 2, 3 ); with an array containing the id's of the groups you wish to track.
How does it work?
Pretty easy. The query returns all users that either have one of the specified groups as the primary group (usergroupid field) or user with one (or more) of the requested groups as secondary.
Why the concat in the query ?
The secondary grouplist consists of a comma separate list of group id's.
We have to add a comma to the search term because otherwise we could pick up partial groups (ie a user in group 10 will be returned if we are looking for group 1). Solution to that is to always include a comma, so look for "
1," instead of simple "
1".
This poses a second problem: Should a group be the the last, it will not be detected. (eg "1,2" and we are searching for group "2"). So, the logical thing is to add an extra comma to the end of the
membergroupids and then search for the groupid with a comma, which will always return the correct user.
Please note the following:
Obviously this is a "decent query" when used on a large board with a lot of users, so you might want to consider taking the initial query out and caching it's results into a small separate table, that way you would only have to select the rows from that table. You could have a script update that table so that you only have to run that once when you add or remove "devs".
More Information