Wikis are a common target for spammers wishing to promote products or web sites due to their open editing nature. MediaWiki offers a number of features designed to help block wiki spam.
Many IP address blacklists lists are available. For instance stopforumspam.com has a list of "All IPs in CSV" which (as of 2011) contains about 140,000 IPs of known spambots.
When you install a fresh copy of MediaWiki, it is susceptible to different kinds of intentional vandalism. Due to the nature of a wiki website, no matter how many protections are present, vandalism will always be present to a certain extent. This page will describe how to limit it.
Sysops can block and unblock IP addresses from editing, uploading files, moving pages, and, if they have been granted such rights, protecting/unprotecting and deleting/undeleting pages.
User Merge and Delete extension allows wiki users with the usermerge permission (Bureaucrat by default) to merge one Wiki user's account with another Wiki user's account.
The Title Blacklist extension allows wiki administrators to block the creation, movement and upload of pages which title matches one or more regular expressions, as well as blocking creation of accounts with matching usernames.
Twinkle is a set of JavaScript functions that gives registered users several extra options to assist them in common Wikipedia maintenance tasks, and to help them deal with acts of vandalism.
Semantic Result Formats (SRF) is a MediaWiki extension, used in conjunction with the Semantic MediaWiki extension, that bundles a number of further result formats for SMW's inline queries. The individual formats can be added to the installation independently, including...
The InputBox extension is a MediaWiki extension that adds already created HTML forms to wiki pages. Users can "complete" a form (entering text, selecting menu items, etc.) by entering text into the box.
This extension enables installation and updating of extensions and MediaWiki itself. It obtains deployment packages by using the API provided by the Distribution extension, parses these and applies them. For this it provides several special pages. You can read more about the deployment effort on the deployment page.
A list of special gadgets users can enable on their preferences pages, as defined by the definitions. This overview provides easy access to the system message pages that define each gadget's description and code.
The list of available gadgets is defined on MediaWiki:Gadgets-definition. Gadgets defined there show up in the "Gadgets" section of Special:Preferences, so users can pick the gadgets they would like to use. An overview of the gadgets defined by MediaWiki:Gadgets-definition is also shown on Special:Gadgets, along with links to the respective system messages, for easy editing.
Custom client-side JavaScript and CSS-based scripts, widgets and gadgets are the lifeblood of making a really awesome MediaWiki site. Power users create and share their own tools, which can get merged out to everyone or kept for individual opt-in.
Make sure the relevent interwiki prefixes have iw_trans set to 1 in the database.
You should now be able to type {{wiki:template name}} or {{wiki::main namespace page name}} to transclude the page from a foriegn wiki.
You can also do {{raw:wiki:template name}} to do a raw transclude, where all templates on the foreign page are expanded as if they come from your wiki instead of the other wiki.
Scary Transclusions: Exact Character Case Matters!
May 24, 2011: Noticed that at least some scary transclusions seemed to stop working. Also noticed this for the first time:
Ultimately discovered that the lowercase "wikipedia" was removed from the Special:Interwiki table. Restored it, ran an update.php command in the maintenance folder and the scary transclusions began working again. -WikiMaster (talk) 12:37, 24 May 2011 (PDT)
Transclusion template fix?
(yup, in a sort of half-ass way. hip hip fuckin' hooray. only wasted half a dozen painful hours so far...)
Intermittent functionality at this point. Caching issue?
Try purging page:
And the "Template fetch failed" error message is often something that goes away if you purge the page cache adding "?action=purge" to the URL.