Last modified: 2011-03-13 18:05:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 157 - Inconsistant Skin options
Inconsistant Skin options
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
PC Linux
: Lowest minor with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-08-17 21:23 UTC by Paul Scanlon
Modified: 2011-03-13 18:05 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Paul Scanlon 2004-08-17 21:23:13 UTC
Using V1.3.0 the following Skins are optioned in the user Preference list when logged 

 Cologne Blue

However, in the stylesheets directory the following appears

davinci <dir>
mono <dir>
monobook <dir>
myskin <dir>

- as well as some other style sheets and files. There are clearly some styles that 
are offered that do not relate to style sheets or directories. Similarly there are 
style directories that are not offered as preferance options (ie davinci).

Looking at include/Skin.php there are some options commented out

    #$wgValidSkinNames['davinci'] = 'DaVinci';
    #$wgValidSkinNames['mono'] = 'Mono';
    #$wgValidSkinNames['monobookminimal'] = 'MonoBookMinimal';

Should this be more consistant. EG. each style should have it's own directory under 
stylesheets, and if it's not going to be offered as an option, then perhaps it should 
be removed - or a refrenece to it in the Release notes saying it's disabled.
Comment 1 Brion Vibber 2004-08-17 21:40:04 UTC
Those are just leftover files from development, and are not currently functional.

Note You need to log in before you can comment on or make changes to this bug.