Extension:GlobalBlocking
Appearance
GlobalBlocking Release status: stable |
|
---|---|
Implementation | Special page , User identity , API , Database |
Description | Allows IP addresses and accounts to be blocked on multiple wikis |
Author(s) | Andrew Garrett, Trust and Safety Product Team, Dreamy Jazz |
Compatibility policy | Snapshots releases along with MediaWiki. Master is not backward compatible. |
MediaWiki | 1.39 and later |
Database changes | Yes |
Virtual domain | virtual-globalblocking |
Tables | globalblocks global_block_whitelist |
License | GNU General Public License 2.0 or later |
Download | |
|
|
|
|
Quarterly downloads | 78 (Ranked 64th) |
Public wikis using | 1,015 (Ranked 250th) |
Translate the GlobalBlocking extension if it is available at translatewiki.net | |
Vagrant role | globalblocking |
Issues | Open tasks · Report a bug |
The GlobalBlocking extension allows a user with the appropriate permissions to block an IP address or IP address range (but not accounts before MediaWiki 1.43) on all wikis in a group sharing the same globalblocking
database.
It is intended to be used for combating severe cross-wiki vandalism and spam.
Installation
[edit]- Download and move the extracted
GlobalBlocking
folder to yourextensions/
directory.
Developers and code contributors should install the extension from Git instead, using:cd extensions/
git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/GlobalBlocking - Add the following code at the bottom of your LocalSettings.php file:
wfLoadExtension( 'GlobalBlocking' );
- You will also need to create a dedicated database for this extension to work. At a minimum (all wikis running on the same host), you need to create a local database for the global tables. Usually this database is named
globalblocking
, but you can choose a different name. For example, on WMF wikis this table is on a database namedcentralauth
. - Grant all database users that your wikis run as full permissions on the database created in the above step (at a minimum,
SELECT, UPDATE, INSERT, DELETE
). - Do either of the following depending on the version of MediaWiki you are running:
- If you run MediaWiki 1.42 or above, define the configuration
$wgDatabaseVirtualDomains['virtual-globalblocking'] = 'globalblocking';
(replacingglobalblocking
with the name of the database created in the steps above). See Manual:$wgVirtualDomainsMapping for more detail on how this configuration value works. - If you run MediaWiki 1.41 or below, define the configuration
$wgGlobalBlockingDatabase = 'dbname';
wheredbname
is replaced with the name of the database you created in the steps above. If you called your databaseglobalblocking
then you can skip this step.
- If you run MediaWiki 1.42 or above, define the configuration
- After creating the database, you should import the SQL from
tables-generated-globalblocks.sql
into the global blocking database. - You also need to run
update.php
on each of your local databases, or otherwise import the SQL schema intables-generated-global_block_whitelist.sql
to them. - Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
Configuration
[edit]Config variable | Description | ||
---|---|---|---|
$wgApplyGlobalBlocks | Whether to respect global blocks on this wiki. This is used so that global blocks can be set on one wiki, but not actually applied there (i.e. so people can contest them on that wiki). | ||
$wgGlobalBlockingBlockXFF | The flag $wgGlobalBlockingBlockXFF , set to true by default, causes blocks to apply to all of the IP addresses in the X-Forwarded-For (XFF) header. Set this flag to false to disable this feature. For more details, see task T25343.
| ||
$wgGlobalBlockingCIDRLimit | Largest global rangeblocks allowed, set by CIDR prefix. The format is the same as $wgBlockCIDRLimit and the default values are /16 for IPv4 and /19 for IPv6, as with $wgBlockCIDRLimit. | ||
$wgGlobalBlockingDatabase |
globalblocks table. This table is on a different database because only one table is used for all wikis in a wiki farm.
| ||
$wgGlobalBlockRemoteReasonUrl | Full path to api.php to use to expand templates in block reasons. | ||
$wgGlobalBlockingAllowedRanges | A list of ranges or IP addresses which are exempted from all global blocks which target the ranges or IP addresses. This exemption does not apply to global account blocks (even if the user is on an exempt range or IP address). | ||
$wgGlobalBlockingCentralWiki | The ID of the central wiki where global blocks are performed. Used to provide a link to the global block log which is likely to have entries, instead of the local log which is unlikely to contain entries. If the value is false , then the local log is used.
|
API
[edit]Two API modules are provided, one to (un)block users, and another to view existing global blocks. They are documented at Extension:GlobalBlocking/API.
Usage
[edit]The following requires appropriate permissions, assigned by default to stewards, which by default can be added or removed by bureaucrats. To make a global block:
- Go to Special:GlobalBlock.
- Enter the target you want to block. This can be an account post MediaWiki 1.43, an IPv4 address or range up to $wgGlobalBlockingCIDRLimit (by default /16, and also /16 hardcoded before that variable was introduced), or any IPv6 address or range up to $wgGlobalBlockingCIDRLimit (by default /19; /4 before that variable was introduced).
- You may decide you want to only block anonymous users, which can only be done for blocks on IPv4 or IPv6 addresses. To only block anonymous users, check the checkbox.
- Submit the form. The target of the block is now globally blocked on your wikis that opt in to the global blocking. Account creation is blocked (even if you selected "anonymous users only": phab:T42190), and the blocked user cannot edit any associated user talk pages on any wiki affected and opted in to the global block. If Extension:AbuseFilter is installed, globally blocked IP addresses are prohibited from viewing the abuse log if the particular wiki is opted in to the block.
To remove a global block:
- Go to Special:GlobalUnblock and click "Remove a global block".
- Enter the target of the block you want to remove and the reason, and submit the form. The account, IP address, or IP range will no longer be globally blocked.
See also
[edit]- Combating spam
- Combating vandalism
- BulkBlock Extension — an extension that allows administrators to easily block multiple users at once on a MediaWiki website.
This extension is being used on one or more Wikimedia projects. This probably means that the extension is stable and works well enough to be used by such high-traffic websites. Look for this extension's name in Wikimedia's CommonSettings.php and InitialiseSettings.php configuration files to see where it's installed. A full list of the extensions installed on a particular wiki can be seen on the wiki's Special:Version page. |
This extension is included in the following wiki farms/hosts and/or packages: This is not an authoritative list. Some wiki farms/hosts and/or packages may contain this extension even if they are not listed here. Always check with your wiki farms/hosts or bundle to confirm. |
Categories:
- Stable extensions
- Special page extensions
- User identity extensions
- API extensions
- Database extensions
- GPL licensed extensions
- Extensions in Wikimedia version control
- CentralAuthInfoFields extensions
- ContributionsToolLinks extensions
- GetBlockErrorMessageKey extensions
- GetLogTypesOnUser extensions
- GetUserBlock extensions
- LoadExtensionSchemaUpdates extensions
- OtherBlockLogLink extensions
- SpecialContributionsBeforeMainOutput extensions
- SpreadAnyEditBlock extensions
- UserIsBlockedGlobally extensions
- UserMergeAccountFields extensions
- All extensions
- Extensions used on Wikimedia
- Extensions included in Miraheze
- Extensions included in Telepedia
- Extensions included in WikiForge
- Extensions for data exchange with other local wikis