Jump to: navigation, search

The overall appearance and layout of MediaWiki pages is dictated by skins, the interface upon which the page is viewed. Users can choose to use different skins (and further customize User styles), and a site administrator can change the default skin for a wiki. The default skin packaged with every MediaWiki install is MonoBook, famous as the default on various WikiMedia projects. When a site administrator creates a custom skin, it is easiest for them to work with an existing skin such as MonoBook.

The latest default skins are mainly based on CSS, so you don't have to change the page source to get a very different look.

Generic CSS classes for content[edit | edit source]

You can reference CSS classes from articles. To allow better and more uniform styling for content elements (infoboxes for example) you should define a global set of css classes that can be referenced from the content. For example: españa

Creating a Skin based on MonoBook (1.6.x)[edit | edit source]

Assuming you would like to create a new skin called "FooBar" based on MonoBook you would:

1 - copy the file skins/MonoBook.php to skins/FooBar.php

2 - create a directory skins/foobar and copy the directory skins/monobook to skins/foobar

3 - edit skins/FooBar.php

3a - FIND:

class SkinMonoBook extends SkinTemplate {
       /** Using monobook. */
       function initPage( &$out ) {
               SkinTemplate::initPage( $out );
               $this->skinname  = 'monobook';
               $this->stylename = 'monobook';
               $this->template  = 'MonoBookTemplate';


class SkinFooBar extends SkinTemplate {
       /** Using foobar. */
       function initPage( &$out ) {
               SkinTemplate::initPage( $out );
               $this->skinname  = 'foobar';
               $this->stylename = 'foobar';
               $this->template  = 'FooBarTemplate';

3b - FIND:

class MonoBookTemplate extends QuickTemplate {


 class FooBarTemplate extends QuickTemplate {

3c - FIND:

wfRunHooks( 'MonoBookTemplateToolboxEnd', array( &$this ) );


wfRunHooks( 'FooBarTemplateToolboxEnd', array( &$this ) );

Your skin is now ready to be plugged in and modified. At this point you can zip up your FooBar.php and foobar directory and consider it a bootstrap for any forthcoming skins you might want to create.

4 - Next up is your Mediawiki configuration. We need to modify your LocalSettings.php file, changing the default skin to your new one...

cd /path/to/mediawiki/
vi LocalSettings.php

4a - FIND:

$wgDefaultSkin = 'monobook';


$wgDefaultSkin = 'foobar';


  • Even though a user changing their skin preference will be presented with a list containing 'FooBar' (same as the file name), the variable $wgDefaultSkin must be 'foobar'. (The capitalisation is different). Getting this wrong will mean that the default skin is invalid (and displays as a badly formatted page).
  • Make sure this line isn't commented out either! Remember to clear your browser cache and hit reload. View page source and search for your new style name (FooBar, foobar), namely the CSS paths.


Remove Skins[edit | edit source]

(for MediaWiki 1.6.7)

To remove specific skin choices from the User Preferences skin choices, put this in LocalSettings.php:

# To remove various skins from the User Preferences choices
$wgSkipSkins = array("chick", "cologneblue", "myskin", "nostalgia", "simple", "standard");

"standard" is the skin called Classic. Omit skins from above line that you want to remain as choices.

Remove Skin tab from User Preferences[edit | edit source]

(for MediaWiki 1.6.7)

To remove the Skin link/tab from User Preferences so that users do not have to be bothered with it at all, go in includes\SpecialPreferences.php (in MediaWiki 1.13.4 go to includes\specials\SpecialPreferences.php) and comment out (put another # at the beginning of each line, or enclose them in /*....*/) these lines:

               # Skin
               $wgOut->addHTML( "<fieldset>\n<legend>\n" . wfMsg('skin') . "</legend>\n" );
               $mptitle = Title::newMainPage();
               $previewtext = wfMsg('skinpreview');
               # Only show members of $wgValidSkinNames rather than
               # $skinNames (skins is all skin names from Language.php)
               foreach ($wgValidSkinNames as $skinkey => $skinname ) {
                       if ( in_array( $skinkey, $wgSkipSkins ) ) {
                       $checked = $skinkey == $this->mSkin ? ' checked="checked"' : ;
                       $sn = isset( $skinNames[$skinkey] ) ? $skinNames[$skinkey] : $skinname;
                       $mplink = htmlspecialchars($mptitle->getLocalURL("useskin=$skinkey"));
                       $previewlink = "<a target='_blank' href=\"$mplink\">$previewtext</a>";
                       if( $skinkey == $wgDefaultSkin )
                               $sn .= ' (' . wfMsg( 'default' ) . ')';
                       $wgOut->addHTML( "<input type='radio' name='wpSkin' id=\"wpSkin$skinkey\" value=\"$skinkey\"$checked /> <label for=\"wpSkin$skinkey\">{$sn}</label> $previewlink
\n" ); } $wgOut->addHTML( "</fieldset>\n\n" );

Ensure users using skipped skins use the default instead[edit | edit source]

(for MediaWiki 1.9.0)

This piece of code ensures that if you have removed a skin, and have specified this in the $wgSkipSkins array in LocalPreferences.php, users who have previously selected the removed skin, will now use $wgDefaultSkin instead. This is an easy way to ensure all of your users are running the same skin, merely put all of the other skins in $wgSkipSkins.

The middle section needs to be inserted into the "normalizeKey( $key )" function in the "includes/Skin.php" file.

         * Normalize a skin preference value to a form that can be loaded.
         * If a skin can't be found, it will fall back to the configured
         * default (or the old 'Classic' skin if that's broken).
         * @param string $key
         * @return string
         * @static
        static function normalizeKey( $key ) {
                global $wgDefaultSkin, $wgSkipSkins;
                $skinNames = Skin::getSkinNames();
                if( $key == '' ) {
                        // Don't return the default immediately;
                        // in a misconfiguration we need to fall back.
                        $key = $wgDefaultSkin;
                if( is_array($wgSkipSkins) && in_array( $key , $wgSkipSkins ) ) {
                        $key = $wgDefaultSkin;
                if( isset( $skinNames[$key] ) ) {
                        return $key;
                // Older versions of the software used a numeric setting
                // in the user preferences.
                $fallback = array(
                        0 => $wgDefaultSkin,
                        1 => 'nostalgia',
                        2 => 'cologneblue' );
                if( isset( $fallback[$key] ) ){
                        $key = $fallback[$key];
                if( isset( $skinNames[$key]  ) ){
                        return $key;
                } else {
                        // The old built-in skin
                        return 'standard';

Hopefully this will be merged with the release version in the future (However I have not submitted it as yet!)

Additionally, the final if-then-else statement appears to default to a specific skin when all else fails. I believe this should try $wgDefaultSkin before using 'standard'. If I were a better man, I would have implemented this whilst I was at it.

Works with 1.6.8 too, just fix global $wgDefaultSkin; at the start to global $wgDefaultSkin, $wgSkipSkins;. Otherwise you'll get a "Warning: in_array(): Wrong datatype for second argument" error message.