Extension talk:Vector

About this board

Hansel2324 (talkcontribs)

I'm new to MediaWiki and have stood up an instance with the following versions:

MediaWiki v1.26

PHP v5.6.16

Using IIS and running web site on localhost using IE11 as browser.

When I set 'Vector' as the default skin the only thing I get is all the text to the far left of the page. Has anyone seen this?

I don't know where to start troubleshooting...any help is appreciated. (talkcontribs)

Same to me ...

not working on webserver

MediaWiki 1.26.2
PHP 5.6.17-1~he.2 (apache2handler)

or 5.4.x

while working on local

MediaWiki 1.26.2
PHP 5.6.15 (apache2handler

Chrome and I.E the same :-/ (talkcontribs)

Seems to be a installation/upgrade-bug

$wgCacheDirectory = $IP."/cache"; (in localsettings.php)

works fine for me. (talkcontribs)

Lots of thanks. I had also the same problem, However based on your suggestion I was able to resolve the issue. to add a little: in localSettinhd.php, insert the following

$wgCacheDirectory = "$wgResourceBasePath/cache";

Note: wgResourceBasePath is the path to your mediawiki directory.

This post was hidden by (history)
Hansel2324 (talkcontribs)

The 'Monobook' skin runs fine

Hansel2324 (talkcontribs)

I also can't get PageTriage or WikiEditor to work either and I don't know if the issues are related.

Ciencia Al Poder (talkcontribs)

Issue already reported in task T119934 (feel free to subscribe to that task) and other support questions... Still there's not enought information to see what's happening.

Please see this topic and try to test those load.php URLs to see any error message embedded on them.

Hansel2324 (talkcontribs)

Thanks for the heads up. Made the mistake of starting with the newest releases for everything. I'm going to start to roll back versions until I can get a stable/working instance.

From the traffic on Phabricator, it looks like it works in MW1.25.3. Any idea/suggestion which v. PHP I should use for a stable instance?

Ciencia Al Poder (talkcontribs)
Reply to "Vector not working"

Setting Portlets Non-collapsible

Wikinaut (talkcontribs)

I've been hunting high and low for an explanation for how to set left sidebar nav elements selectively non-collapsible -- specifically, the Google Adsense 2 extension's portlet. Any suggestions? --Balerion 00:05, 5 June 2011 (UTC) (talkcontribs)

If you view the source of the page and get the id of the element you want to stay non-collapsed....Example for adsense:


<!-- googleadsense -->
<div class="portal" id='p-googleadsense'>

Then you can add that id in the if statement near line 170 of modules/ext.vector.collapsibleNav.js:


if (
				state == 'true' ||
				( state == null && i < 1 ) ||
				( state == null && version == 1 && id == 'p-lang' )
			) {
					.addClass( 'expanded' )
					.find( 'div.body' )
			} else {
				$(this).addClass( 'collapsed' );


if (
				state == 'true' || id == "p-googleadsense" ||
				( state == null && i < 1 ) ||
				( state == null && version == 1 && id == 'p-lang' )
			) {
					.addClass( 'expanded' )
					.find( 'div.body' )
			} else {
				$(this).addClass( 'collapsed' );

This post was posted by, but signed as Miigotu.

Reply to "Setting Portlets Non-collapsible"

Core javascript features not working after upgrading from 1.16 to 1.20.2

5 (talkcontribs)

Hello, I just upgraded a site from 1.16 to 1.20.2. The collapsible nav does not work on the front (main) page, but on all other pages. I get the following errors in Chrome:

Exception thrown by jquery.mw-jump: Object #<Object> has no method 'delegate' load.php:151
Exception thrown by ext.vector.collapsibleNav: Cannot call method 'test' of undefined load.php:151
Exception thrown by mediawiki.searchSuggest: Object #<Object> has no method 'first' load.php:151
Krinkle (talkcontribs)

Looking at the errors I'd say it isn't just collapsenav, I suspect the search suggestions when typing in the search bar and the table of contents "Show" and "Hide" don't work either.

Based on the errors I'm pretty sure the problem lies in the fact that there is something on your wiki that is unregistering jQuery plugins, thus causing code that is loaded by MediaWiki to be dereferenced. Specifically:

  • module jquery.delegate
  • module jquery.client method test
  • jquery method jquery.fn.first (introduced in jQuery 1.4)

See also jQuery, it is important that you do not manually load some (ancient version of) jQuery. MediaWiki ships with jQuery by default. Loading your own causes both incompatibilities (since core uses a a much newer version) and it causes plugins to be dereferenced at run time.

Noti1234 (talkcontribs)

I had similar problem with BugzillaReports extension. I disabled the jquery loaded by this extension and the problems went away. (talkcontribs)

I've hit the same problem with BugzillaReports, can you explain how you disabled the jquery for the extension?

Immewnity (talkcontribs)

I had a similar issue - try disabling CollapsibleTabs.

Reply to "Core javascript features not working after upgrading from 1.16 to 1.20.2"

MW 1.24.1 Fresh Install - Vector sidebar does not collapse

2 (talkcontribs)

Hey all. I am having issues with a fresh install of Mediawiki and using Vector. I am using it due to liking how the sidebar collapses the navigation; hwoever, in my install (a fresh Softaculous install), the sidebar is not collapsing. I have made some Vector.css changes, but none that would effect that, as the Vector.css is being migrated to the new install from an old server.

The site in question is www.lexmasqlarp.com. Any help would be appreciated.

Rob Kam (talkcontribs)

For users that use Mediawiki 1.24 or higher can use the CollapsibleVector extension to get "collabsiblenav" (collabsible navigation) back.

Reply to "MW 1.24.1 Fresh Install - Vector sidebar does not collapse"

clarification on what it means to be bundled vs core.

Renamed user G3DXr4qY3n (talkcontribs)

i'm upgrading from 1.19 to 1.23. i understand that this extension moved from bundled to part of the core functionality as of 1.22.

why then does the vector directory still appear under extensions in 1.23, and it shows up under Special:Version if it is called from LocalSettings.php? is there still something that the manually enabled extension still does?

Kghbln (talkcontribs)

I believe that you did not kill the old code while upgrading, meaning that there is still a /.../extensions/Vector/ folder from your earlier installation. Just remove the require "extensions/Vector/Vector.php"; from you "LocalSettings.php" file. After that you may safely kill the above mentioned folder.

Renamed user G3DXr4qY3n (talkcontribs)

you're right kgh. i just realized that and came back here to amend my post, but you beat me to it.

thanks for your quick response. it is appreciated.

Reply to "clarification on what it means to be bundled vs core."

CollapsibleNav - problem with MW 1.22.7

DorianCrede (talkcontribs)

I have tried to disable the CollapsibleNav and collapsibletabs feature in the LocalSettings.php file, but the menus still are collapsible. Here are my settings:

require_once "$IP/extensions/Vector/Vector.php";
// $wgDefaultUserOptions['vector-collapsiblenav'] = 0;
$wgVectorFeatures['collapsiblenav']['global'] = false;
$wgVectorFeatures['collapsibletabs']['global'] = false;

What is wrong?


Nemo bis (talkcontribs)
Kghbln (talkcontribs)

Since Vector is now incuded in core (MW 1.22+) you should not include this utility extension with require_once( "$IP/extensions/Vector/Vector.php" ); Just remove this line together with the rest of the now unsupported features and delete the extension's code.

Kghbln (talkcontribs)

Ah yeah, I have now seen this collapsible disaster unfold on a 1.22.x wiki which has proven my answer to be incorrect. Only the first section is not collapsed while all subsequent ones are. Thus my answer indeed does not help here.

DavisNT (talkcontribs) (talkcontribs)

I have a similar problem, I just tried to insert the code of DavisNT and it works on version 1.22.6

Reply to "CollapsibleNav - problem with MW 1.22.7"

First level text disappears

Wade.courtney (talkcontribs)

When the navigation collapse feature is enalbed, the first line of text formatted as * text disappears.

Has anyone found a way around that?


Reply to "First level text disappears"

How to use Vector features for new skin?

Fxk2 (talkcontribs)


we created a nice new skin for our Wiki - and now we want to integrate the simplesearch-feature, as well as the collapsible sidebar. Any advice on how we can that?

Would it be an idea to copy the Vector-Extension, rename it after our new Skin or something similar? Cheers --Fxk2 13:38, 20 December 2011 (UTC)

Pastakhov (talkcontribs) (talkcontribs)

That's not what he asked. He wants to know how to use the Vector extension with a skin that is based on Vector.

Ashimema (talkcontribs)

I'de love to know the answer to this too.. It must be a simple switch somewhere that sets the Vector extension to rely upon the Vector skin, but i can't see it anywhere in the code upon first look.

FreedomFighterSparrow (talkcontribs)

The one I know of is in Vector.hooks.php, function beforePageDisplay, which looks like this:

public static function beforePageDisplay( $out, $skin ) {
	if ( $skin instanceof SkinVector ) {
		// Add modules for enabled features

Starting on line 96 in MW 1.17. Obviously, you need to change SkinVector to the appropriate class for your skin... but I haven't tested it personally.

Of course, there might be other hidden ones...

Kryand (talkcontribs)

Based on this suggestion, I tried something different. It seems like you should be able to safely extend the Vector classes when you declare the classes of your new skin, for example:

class SkinNEWSKIN extends SkinVector
class NEWSKINTemplate extends VectorTemplate

Rather than extending SkinTemplate and BaseTemplate respectively. That should have the same effect as the above suggestion without requiring that you make modifications to the Vector extension (which may be overwritten in subsequent updates, etc).

So far on my wiki, it's working exactly as expected without a hitch.

FreedomFighterSparrow (talkcontribs)

Yes, that definitely seems like a better solution :-) BTW, if you haven't seen it already, there's a tutorial by Daniel Friesen on doing that.

(I believe I tried something like it when Vector first appeared, but I was too new to MediaWiki and it just didn't work. Anyway, my current skin is so different from Vector that there's no point in it, anymore...) (talkcontribs)

I've been searching this for days, until I found this talk here. I am also very new to mediawiki. Thanks to you, I found this new tutorial. So, thanks for the help, and I hope you'll get to see this because it's an old thread. (talkcontribs)

After reading the above tutorial, and trying it, I can't make it work. I also found THIS post which is exactly what happens to me with V1.21

I wonder if there's an easy way to simply "inherit" the Vector theme and only make visual changes to the .css without learning and changing the inner parts of an installed mediawiki.

Reply to "How to use Vector features for new skin?"

What does the 'simplesearch' do?

Subfader (talkcontribs)
$wgDefaultSkin = 'vector';
$wgVectorUseSimpleSearch = true;

has no effect on the search in Vector skin for me.

Krinkle (talkcontribs)

The search bar should look very different. Check this screenshot for example. On the right is with SimpleSearch enabled.

Subfader (talkcontribs)

Ah, works now. Thanks. (talkcontribs)

Here its not working either, how did you fix it? I wrote the same lines that Subfader.. (talkcontribs)

We are setting $wgVectorUseSimpleSearch to true but our user preferences are not taking the value. We have to go into user preferences -> search options -> Enable enhanced search suggestions and manually set the flag. Any idea why this might be the case? (talkcontribs)

To force the display of simple search, you just have to delete

&& $this->getSkin()->getUser()->getOption( 'vector-simplesearch' )

in skin/vector.php (line 468)

Reply to "What does the 'simplesearch' do?" (talkcontribs)

Please add support for monobook so the toolbar looks like vector but instead it is on the left in the sidebar please

Reply to "Monobook support"
Return to "Vector" page.