Manual talk:Skinning/Vector

I have duplicated folder "/skins/vector" into "/skins/foobar", then duplicated files Vector.php and Vector.deps.php into FooBar.php and FooBar.deps.php and after that changed the mentioned in manual words in FooBar.php and added a code $wgResourceModules['skins.runavector'] = array(...); just after the "if !defined (' MEDIAWIKI' ){...} And I've got en error "Call to a member function getGroup on a non-object in /var/www/runa/includes/OutputPage.php on line 2707". How can I fix that error?

Waltztime: Unfortunately, it is unclear to me what "register your skin's module: in FooBar.php's global scope:" means. How do you do that? Where do you put this code snippet? It would improve this page if this was made more explicit and concrete. --Waltztime 00:25, 13 September 2011 (UTC)

SeizamDev: MediaWiki [1.17] needs registration of skin in resources/Resources. This solves the error reported above. But registering a second time inside FooBar.php seems redundant (the new skin works without it). This (kind of) answers Waltztime question above. What about removing this from the instruction? SeizamDev 10:12, 24 October 2011 (UTC)


 * registering the skin by editing resources/Resources should not be necessary. It will do the job of course, but editing a core file should not be part of adding a new skin. - 95.96.101.60 10:22, 24 October 2011 (UTC)

How to hide action list?
It would be nice to cover in the article the following questions:
 * 1) How to hide from unregistered visiters everything from the action list (toolbar), so they could just read article but could not see discussion, history and so on?
 * 2) How to move "Log in" link to the bottom?
 * 3) How to hide elements in the footer

Everything I could find on those questions were for Monobook skin and nothing for Vector. If you know where it it described, please provide a link.

Pavel Malakhov 10:34, 15 September 2011 (UTC)


 * hiding/moving interface items is likely done using CSS and thus more or less the same as in monobook.
 * hiding interface elements can also be done using  in (a copy of) Vector.php
 * restricting (read) usage of an entire namespace like Talk: look at $wgGroupPermissions top-tabs will (should) display with respect to visibility.
 * See also Extension:Lockdown and Security issues with authorization extensions - Arent 12:38, 15 September 2011 (UTC)