Jump to content

Extension:TitleKey: Difference between revisions

From mediawiki.org
Content deleted Content added
chg
Known problems
Line 51: Line 51:
|no-registration-version=1.27
|no-registration-version=1.27
}}
}}

== Known problems ==

* It breaks [[VisualEditor]] autocompletion for templates ([[Topic:Uci3j110eoxumevd]]).

Revision as of 22:48, 14 March 2019

MediaWiki extensions manual
TitleKey
Release status: stable
Implementation Search
Description Provides a case-insensitive page title prefix search
Author(s) Brion Vibber (Brion VIBBERtalk)
Latest version continuous updates
MediaWiki 1.25+
Database changes Yes
Tables titlekey
License GNU General Public License 2.0 or later
Download
README
Quarterly downloads 62 (Ranked 70th)
Translate the TitleKey extension if it is available at translatewiki.net
Issues Open tasks · Report a bug

The TitleKey extension provides a case-insensitive page title prefix search. It uses a separate table for the keys, so it can be deployed without an expensive rebuild of core tables, and uninstalled later in preference for a different search extension such as CirrusSearch .

For the average site administrator, the benefit of this extension is that it allows search suggestions (e.g. from Opensearch API) to be case-insensitive.

This extension provides no benefit if you are using CirrusSearch .

Installation

  • Download and move the extracted TitleKey folder to your extensions/ directory.
    Developers and code contributors should install the extension from Git instead, using:cd extensions/
    git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/TitleKey
  • Add the following code at the bottom of your LocalSettings.php file:
    wfLoadExtension( 'TitleKey' );
    
  • Run the update script which will automatically create the necessary database tables that this extension needs.
  • Run the "rebuildTitleKeys.php" script (this requires command-line access):
php extensions/TitleKey/rebuildTitleKeys.php
  • Yes Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.

Known problems