MediaWiki 1.9/New toys
Wikia - creating communities
There were a lot of changes in the 1.7 to 1.9 upgrade. Here is a community compiled list of how to use some of these. Note that many of the new features should be moved to Help pages at some point, but can start here.
Contents |
[edit] For staff
[edit] MediaWiki: defaults deleted
MediaWiki: Defaults are no longer required or useful existing, unless customized, and have been (or are being) deleted.
This is good for several reasons:
- Easier to keep track of all customized via Special:Prefixindex or Special:Allpages
- Easier to upgrade without User:MediaWiki_default having to edit every updated message on every upgrade.
- Easier for us to change a global default message without editing several thousand MediaWiki: pages (although there will still be a caching issue involved in this).
[edit] For bureaucrats/sysops
[edit] Spam Whitelist
You may know about the w:Spam Blacklist, but did you know the newest version of the Spam Blacklist extension allows local per-wiki whitelists? These are located at MediaWiki:Spam-whitelist. For example, on en.wikipedia: wikipedia:en:MediaWiki:Spam-whitelist. These use simple regex, such as:
#Spam whitelist encyclopediadramatica\.com # we allow it here
[edit] Automatic edit summaries
Automatic edit summaries now exist for several actions, such as new pages, blanking, or replacing pages. These can be customized/disabled through several MediaWiki: messages.
[edit] Rollback on history pages
You'll notice, as an administrator or user granted with rollback permissions, that you will see a [rollback] link on history pages.
- more info/help?
[edit] Undelete deleted files
Files can now be undeleted. This was a new optional parameter, that is now enabled. This means you can adopt a "Delete first, ask questions later" attitude towards questionable uploads.
- more info/help?
[edit] New blocking options
(this will need a full help page)
- more info/help?
[edit] New MediaWiki:Common.js
Now in addition to MediaWiki:Monobook.js we also have a Common.js which will work under all skins. MediaWiki:Monobook.js is actually obsolete (And if you look at the code source deprecated) because Monobook only stuff can be done in Common.js using a if( skin == 'monobook' ).
- more info/help?
[edit] For all users!
[edit] Redirect to section
It is now possible for a redirect-to-a-section to work (requires javascript).
Example:
- A page contains a link to [[Foo]]
- Foo contains: #REDIRECT [[Bar#Foo]]
- Clicking on [[Foo]] takes you to /wiki/Bar, but on page load the URL is changed to /wiki/Bar#Foo
Prior to this, as redirects were (and still are) handled more like transclusions (rather than http 30* redirects), it was not feasable to augment the URL. And the page containing [[Foo]] had no idea that the article Foo contained a section anchor.
But now MediaWiki checks the contents of [[Foo]] and sets a javascript tag on Bar with:
redirectToFragment("#Bar");
[edit] Recent changes byte change
Recent changes now shows the byte difference for each edit. This can be styled in user css or site-wide css for example:
.mw-plusminus-pos {color: #006400;}
.mw-plusminus-neg {color: #8B0000;}
.mw-plusminus-null {color: #777777;}
Or even completely disabled:
.mw-plusminus-pos {display: none;}
.mw-plusminus-neg {display: none;}
.mw-plusminus-null {display: none;}
[edit] Undo
On diff links, there is now an 'undo' link next to the newer revision. This feature (when clicked) attempts to undo the changes made in that revision, even if it is not the top revision.
If the attempt is successful (if there have been no changes made to the same lines, per the crude edit conflict detection engine), you are presented with an edit page showing the contents with the revision's changes removed, which you can then review and save.
Unlike rollback or manual rollback, this performs on only one revision, and the revision need not be the top edit.
- See Help:Undo
[edit] Custom edit buttons
You can now add custom edit buttons to your edit windows easily.
[edit] Per-page css
The <body> tag now has several new CSS classes. For example, this page:
<body class="mediawiki ns-0 ltr page-MediaWiki_1_9_New_toys">
This means, you can customize any of this pages content style by referring to it in your user/monobook.css as:
body.page-MediaWiki_1_9_New_toys {}
- more info/help?
[edit] New javascript variables
If you view a page source, you will see a new <script> tag defining many new variables, that you can use in user and site-wide javascripting. For example, Wikia produces:
var skin = "monobook"; var stylepath = "/skins"; var wgArticlePath = "/wiki/$1"; var wgScriptPath = ""; var wgServer = "http://www.wikia.com"; var wgCanonicalNamespace = ""; var wgCanonicalSpecialPageName = false; var wgNamespaceNumber = 0; var wgPageName = "Wikia"; var wgTitle = "Wikia"; var wgArticleId = "5"; var wgIsArticle = true; var wgUserName = null; var wgUserLanguage = "en"; var wgContentLanguage = "en"; var wgBreakFrames = false; var wgCurRevisionId = "73926";
