Skin talk:Vector

Previous page history was archived for backup purposes at Skin talk:Vector/LQT Archive 1 on 2015-07-10.

How do I enable the sticky header in the new vector skin? I am on MW 1.37.1.

Hi, I have made following settings for the skin:

wfLoadSkin( 'Vector' );
$wgDefaultSkin = 'vector';
$wgVectorDefaultSkinVersion = '2';
$wgVectorDefaultSkinVersionForExistingAccounts = '2';
$wgVectorDefaultSkinVersionForNewAccounts = '2';

So the website is switched to the new version of vector skin, but as soon as I login to any account the website displays old version of vector.

Please help me to have new vector skin for all guests, users as default one.

I still cannot exclude old version of vector skin for logged in users. Please help.

$wgDefaultSkin = "vector";

wfLoadSkin( 'Vector' );

$wgVectorResponsive = true;

$wgVectorDefaultSkinVersion = '2';

$wgVectorDefaultSkinVersionForExistingAccounts = '2';

$wgVectorDefaultSkinVersionForNewAccounts = '2';

$wgVectorIsSearchInHeader = true;

$wgVectorLanguageInHeader = true;

$wgVectorUseWvuiSearch = true;

$wgVectorUseIconWatch = true;

$wgVectorUseSimpleSearch  = true;

Manual:$wgLogos has updated information on how to configure logos for skins.

Hi, when I select the modern vector theme, only the name appears instead of the logo. How can I solve this?

Do you mean on MediaWiki.org or your own installation? Does the issue occur on other devices as well? Perhaps the browser cache needs clearing.

Yes, I asked for I installed it on my own localhost.

See Manual:$wgLogos

I have set vector as default via $wgVectorDefaultSkinVersion = '2'; – however that doesn't apply for registered users. The "classic vector" box is still ticked. Any ideas?

I just found out. Just add:

$wgVectorDefaultSkinVersionForExistingAccounts = '2'; $wgVectorDefaultSkinVersionForNewAccounts = '2';

I have added such setting, but they haven't applied to users who logged in their accounts. Any ideas to resolve the problem?

Hi Fokebox

Use this $wgVectorDefaultSkinVersion = '2';

Other options for Vector skin see in this

I have made such setting and I have Vector 2022 as a default, but as soon as I login any account I see old vector version.

You might need to updates to Vector see instructions

I have MW 1.37 included with new vector skin

I got switched automatically to Vector-2022 on MediaWiki.org, but my vector.css affects the appearance of Vector 2022. Is this intentional?

Yes, it’s intentional (but only temporary), see phab:T301212 about the planned removal of this feature.

What is the official / correct way for a user script to test for a page being viewed by a user that is configured to use the new evil Vector rather than the real Vector? They both show up as

mw.config.get('skin') = "vector"

~~~~

I don’t know how official or future proof this is, but

$('body').is('.skin-vector-legacy')

is the original Vector. (It works 100% correctly at the moment.)

Real Vector returns -- mw.config.get('skin') = 'vector'
and has body tag classes -- "skin-vector" and "skin-vector-legacy"

Evil Vector now returns -- mw.config.get('skin') = 'vector-2022'
and has body tag classes -- "skin-vector" and "skin-vector-2022"
(not sure when that started)

See phab:T300987 about the change.

Tracked in Phabricator
Task T288686

Bonjour,

Nous utilisons la dernière version de Vector pour mediawiki 1.38.0-wmf.13 de mediawiki et tout fonctionne, sauf la barre de recherche principale.

En effet, nous installation est directement dans le répertoire principale, mais il semble que vector appel :

mysite/w/rest.php

Au lieu de

mysite/rest.php

Savez-vous comment résoudre ce problème pour faire fonctionner la barre de recherche (celle de mobilefrontend fonctionne elle normalement)?

Cordialement.

Unfortunately it’s not possible in new Vector yet, see phab:T288686. You can temporarily switch back to the old Vector by setting $wgVectorDefaultSkinVersion = '1'; in your LocalSettings.php, or try setting a symlink named w in your wiki root directory (ln -s w, if you have shell access and the server runs some sort of Linux). I couldn’t get the latter work, though, probably it would require some .htaccess magic that I don’t have.

Hello,

Thank you for your lead, I just modified directly the :

wvui-search.commonjs2.js and wvui-commonjs2.js

And it works :)

Kims

Hi,

I recently started using the new Vector. It used to be possible to handle one logo per namespace, using the vector skin, by modifying ''mediawiki:Vector.css'' and using lines like :

.ns-750 #p-logo a, .ns-751 #p-logo a{background-image: url('images/thumb/Projets.svg/120px-logo.svg.png') !important;}

But this does not seem possible anymore, especially since the css does not define the logos anymore. Any idea on how to do that (choose the logo depending on the namespace) with the new Vector skin ?

Thanks in advance

You would need to write a hook handler that changes the value of $wgLogos based on the namespace, I think. Probably something pretty early post-render, like ContentAlterParserOutput.

Hi,

I recently upgraded a site (BikeWOW) that uses Vector to MediaWiki 1.36. After the upgrade, I noticed that the sidebar does not display the extensions that I have, including AddThis and PCRGuiInserts.

Is this due to some modification to Vector? I have attempted to use this:

$wgVectorDefaultSkinVersion = '1';

I have also tried using:

$wgVectorResponsive = true;

$wgVectorDefaultSkinVersion = '2';

In addition to those I have made numerous other modifications, but the issue remains. When I use MonoBook, the sidebar extensions appear normally. I have updated and reinstalled the extensions, as well as disabling each of the extensions and other extensions. These same extensions (AddThis and PCRGuiInserts) both work fine in other parts of the page.

Would any additional information assist in fixing this? I have looked through the documentation and not found a method to show extensions in the sidebar in Vector on 1.36.

When I browsed Wikipedia through the Wayback Machine, I noticed that one edge of the content area (div#content)'s light blue border sometimes appears thicker than another. I examined it through developer tools, and noticed that the border was depicted through an embedded single-pixel PNG graphic (background-image: url(data:image/png;base64,iVBORw0KGgoAAAAN […] and a "border.png" file as fallback) rather than a CSS code border. Since approximately 2013, a pure CSS code border is used.

Just asking out of curiousity, why was a PNG graphic once used? A technical reason? Monobook apparently used CSS borders since at least 2005, possibly since the beginning. How come Vector didn't?

It was changed in February 2013. According to the Bugzilla bug referenced in that commit, it was probably for compatibility with ancient IE versions.