MediaWiki  1.29.1
UserNamePrefixSearch.php
Go to the documentation of this file.
1 <?php
29 
39  public static function search( $audience, $search, $limit, $offset = 0 ) {
40  $user = User::newFromName( $search );
41 
42  $dbr = wfGetDB( DB_REPLICA );
43  $prefix = $user ? $user->getName() : '';
44  $tables = [ 'user' ];
45  $cond = [ 'user_name ' . $dbr->buildLike( $prefix, $dbr->anyString() ) ];
46  $joinConds = [];
47 
48  // Filter out hidden user names
49  if ( $audience === 'public' || !$audience->isAllowed( 'hideuser' ) ) {
50  $tables[] = 'ipblocks';
51  $cond['ipb_deleted'] = [ 0, null ];
52  $joinConds['ipblocks'] = [ 'LEFT JOIN', 'user_id=ipb_user' ];
53  }
54 
55  $res = $dbr->selectFieldValues(
56  $tables,
57  'user_name',
58  $cond,
59  __METHOD__,
60  [
61  'LIMIT' => $limit,
62  'ORDER BY' => 'user_name',
63  'OFFSET' => $offset
64  ],
65  $joinConds
66  );
67 
68  return $res === false ? [] : $res;
69  }
70 }
$tables
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist Do not use this to implement individual filters if they are compatible with the ChangesListFilter and ChangesListFilterGroup structure use sub classes of those in conjunction with the ChangesListSpecialPageStructuredFilters hook This hook can be used to implement filters that do not implement that or custom behavior that is not an individual filter e g Watchlist & $tables
Definition: hooks.txt:990
UserNamePrefixSearch\search
static search( $audience, $search, $limit, $offset=0)
Do a prefix search of user names and return a list of matching user names.
Definition: UserNamePrefixSearch.php:39
$user
please add to it if you re going to add events to the MediaWiki code where normally authentication against an external auth plugin would be creating a account $user
Definition: hooks.txt:246
User\newFromName
static newFromName( $name, $validate='valid')
Static factory method for creation from username.
Definition: User.php:556
$res
$res
Definition: database.txt:21
php
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
Definition: injection.txt:35
wfGetDB
wfGetDB( $db, $groups=[], $wiki=false)
Get a Database object.
Definition: GlobalFunctions.php:3060
$limit
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist Do not use this to implement individual filters if they are compatible with the ChangesListFilter and ChangesListFilterGroup structure use sub classes of those in conjunction with the ChangesListSpecialPageStructuredFilters hook This hook can be used to implement filters that do not implement that or custom behavior that is not an individual filter e g Watchlist and Watchlist you will want to construct new ChangesListBooleanFilter or ChangesListStringOptionsFilter objects When constructing you specify which group they belong to You can reuse existing or create your you must register them with $special registerFilterGroup removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set and then return false from the hook function Ensure you consume the ChangeTagAfterDelete hook to carry out custom deletion actions as context called by AbstractContent::getParserOutput May be used to override the normal model specific rendering of page content as context as context the output can only depend on parameters provided to this hook not on global state indicating whether full HTML should be generated If generation of HTML may be but other information should still be present in the ParserOutput object to manipulate or replace but no entry for that model exists in $wgContentHandlers please use GetContentModels hook to make them known to core if desired whether it is OK to use $contentModel on $title Handler functions that modify $ok should generally return false to prevent further hooks from further modifying $ok inclusive $limit
Definition: hooks.txt:1049
DB_REPLICA
const DB_REPLICA
Definition: defines.php:25
UserNamePrefixSearch
Handles searching prefixes of user names.
Definition: UserNamePrefixSearch.php:28
$dbr
if(! $regexes) $dbr
Definition: cleanup.php:94