Manual:Block and unblock/it

Sysops can block and unblock IP addresses (and registered user accounts if username blocking is enabled) from editing, uploading files, moving pages, and, if they have been granted such rights, protecting/unprotecting and deleting/undeleting pages.

Il blocco
Blocks are applied via the form at the special page Special:Block. Ci sono diversi passi per applicare un blocco:


 * 1) Specificare l'indirizzo IP o il nome utente che dev'essere bloccato. Enter the IP address to be blocked, or the name of the registered user account to be blocked, in the "" field of the form. Note that nonexistent usernames can also be blocked, so be certain you have the correct username. You can also block a range of IP addresses; see  for instructions.
 * 2) Specify the parameters of the block. Select the actions that the block target should be prevented from completing. A  block prevents the block target from editing all pages on the wikis, while a  block prevents the block target from editing the specified pages and/or pages inside the specified namespaces.
 * 3) Specify a duration for the block. You can select a predefined duration from the drop down box labelled "", or you can enter a custom value, using the GNU standard format, in the "Other time" field. If the duration given is "indefinite", then the block will not expire, although the IP address or user account may still be unblocked by a sysop.
 * 4) Specify a reason for the block (optional). This reason will be displayed to the blocked user if they attempt to edit a page.

Click "" to apply the block. All blocks are recorded in the block log, and all currently active blocks are listed at the list of active blocks.

Note that in addition to manually entering the IP address or user account to be blocked into Special:Block, you may also follow the "" link from the toolbox in the sidebar when viewing the "User" or "User talk" page of the IP address or user account. You can also click on the "" link next following an IP address or user account name in the recent changes list or the page history.

Opzioni del blocco
Several extra blocking options were added in version 1.8 of MediaWiki, which are enabled by checking a check box on the blocking form.


 * Block anonymous users only (also called softblocking): This option changes the effect of a block when blocking an IP address. When it is enabled, the block will only affect anonymous users editing from that IP address; registered users editing from that IP address will not be affected. The option has no effect on a block of a registered user, but does on an autoblock caused by it.


 * Block account creation: This option changes the effect of a block when blocking a user or an IP address. When it is enabled, the registration of new user accounts from that IP address will be disabled while the block is in effect.


 * Automatically block the last IP address used by this user, and any subsequent addresses they try to edit from (also called hardblocking): This option changes the effect of a block when blocking a registered user account. When it is enabled, the IP address most recently used by the account, and any IP addresses that the account subsequently attempts to edit from will be automatically blocked.

Unblocking
An IP address or registered user account can be unblocked via the list of active blocks. Find the IP address or registered user account you wish to unblock in the list (you can enter the address or name in the "" field to help you find the entry), and click the "" link displayed to the right of the block's expiry time.

This will lead you to a confirmation page. Enter the reason for unblocking (optional) in the "" field, and click "" to remove the block. All unblockings are recorded in the block log.

Note that if a range is blocked, then the unblock must cover the whole range to be effective. Attempting to unblock an individual IP address in the range will not be effective.

Effects of being blocked
Blocked users may still read pages, but they may not create, edit or move pages, or upload files. Partially blocked users may not edit the particular pages or namespaces specified in their block, but may create, edit or move other pages, and may upload files. Users with certain other user rights may not be able to use those rights when they are blocked, depending on their block. For example, users with the rights to delete and undelete or protect and unprotect pages will not be able to do so if they are sitewide blocked. If they are partially blocked, then for any page they are not blocked from, they will still be able to perform these actions. However, users with the rights to block and unblock users will still be able to do so when they are blocked, including any blocks on their own account, given that they have the  right.

Users who are blocked and attempt to edit a page (or move a page, or upload a file) will see the "Your account or IP address has been blocked" message informing them that they have been blocked.

If the autoblock option has been enabled with respect to a block, and the blocked user attempts to edit (or move a page, or upload a file), the IP address being used by that user will also be blocked.

Configuration settings related to blocking
The configuration options below can be set in and can be used to enable or disable certain aspects of the blocking interface.


 * - controls the ability for sysops to block usernames. This is true by default. If a sysop tries to block a registered user account and this setting is not enabled, then an error message will be displayed, informing the sysop that the "IP Address does not exist".


 * - controls the ability for sysops to block ranges of IP address. This is true by default.
 * - controls how many seconds need to pass until a block on an "autoblocked" IP address will expire. The default is 86400 seconds (one day)
 * - controls whether or not a blocked user is able to edit their own user talk page. This is currently (1.26+) true by default. The ability to disable the ability of a blocked user to edit their own user talk page, when this variable is true, is an option available in Special:Block.
 * and the blockemail user right control the ability for sysops to prevent users from using the Special:EmailUser interface.  is true by default.
 * - controls if blocked users will be allowed to login. This is false by default.
 * - (1.29+) determines whether to set a cookie when a user is autoblocked. Doing so means that a blocked user, even after logging out and moving to a new IP address, will still be blocked. This is false by default.
 * - (1.33+) - allow the creation of partial blocks, which can block a user account, IP address or IP range from particular pages, namespaces or actions. This is false by default.
 * The hideuser user right controls the ability for sysops to prevent a blocked user from appearing in the block log, the active block list, and the user list.

Pagine MediaWiki:

 * MediaWiki:ipboptions - contains a list of suggested block durations
 * MediaWiki:ipb-default-expiry - allows customization of the default duration in the blocking form (if left unchanged, the default duration is "other")
 * More blocking-related interface messages

URL parameters
Special:Block accepts some URL parameters to prepopulate the HTML form:


 * - username/IP address
 * - the type of block restriction (=sitewide or =partial)
 * - the pages to block (only applies for partial blocks; separate multiple pages with %0A; maximum 10 pages)
 * - IDs of the namespaces to block (only applies for partial blocks; separate multiple namespaces with %0A; see for a list of blockable namespace IDs)
 * - expiry time
 * - autoblock setting (=1 or =0)
 * - hard block setting (=1 or =0)
 * - prevent account creation (=1 or =0)
 * - reason, from selection of MediaWiki:Ipbreason-dropdown
 * - prepopulating "other reason" text field

Hooks

 * Manual:Hooks/BlockIp, occurs whenever the software receives a request to block an IP address or user
 * Manual:Hooks/BlockIpComplete, occurs after the request to block an IP or user has been processed
 * Manual:Hooks/GetBlockedStatus, fired after the user's getBlockStatus is set