Extension talk:Vector

Defaulting Toolbox to "collapsed" for some users

I don't really recommend it - but if you want the Toolbox section to render in the collapsed mode by default for non-sysops, you can make the following change near line 170 in modules/ext.vector.collapsibleNav.js:

Original:

                        if (
                                state == 'true' ||
                                ( state == null && i < 1 ) ||
                                ( state == null && version == 1 && id == 'p-lang' )
                        ) {

New:

                        if ( jQuery.inArray( 'sysop', wgUserGroups ) == 1 && (  // local edit
                                state == 'true' ||
                                ( state == null && i < 1 ) ||
                                ( state == null && version == 1 && id == 'p-lang' )
                            )  // local edit
                        ) {

Note: This probably won't do the right thing if there are additional collapsible sections. -Jlerner 22:02, 3 April 2011 (UTC)

Setting Portlets Non-collapsible

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)

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

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:

Original:

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

New:

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

Miigotu 05:37, 2 September 2011 (UTC)

SimpleSearch scroll bars visible in MW 1.17.0rc1

So, I see in IE and Chrome scroll bars in SimpleSearch. I changed Vector\modules\ext.vector.expandableSearch.css setting "overflow: auto;" to "overflow: hidden;". Strange that I dont see scroll bars at any Wikimedia project sites. Wikinaut 06:21, 14 June 2011 (UTC)

Fatal error: Unsupported operand types in /home5/ethancom/public_html/mediawiki/extensions/Vector/Vector.php

I just installed Vector and I'm getting the following error: Fatal error: Unsupported operand types in /home5/ethancom/public_html/mediawiki/extensions/Vector/Vector.php on line 109. Any advice? Wikinaut 06:22, 14 June 2011 (UTC)

CollapsibleLeftNav Set Default Status

How would I set the default status on this?

It always shows the first portal, which you can't collapse. The second portal seems to default to uncollapsed. The third and other portals seem to default to collapsed.

How can I make the third default to uncollapsed?

Thank you. 24.40.138.185 05:18, 23 June 2011 (UTC)

I also need to set the default status (collapsed / uncollapsed) for the left navigation. Is this possible? 195.37.78.240 07:33, 12 April 2012 (UTC)

Anyone had any luck finding a solution? Perhaps via css? Varnent (talk) 07:19, 19 May 2012 (UTC)

Is there a way to disable CollapsibleTabs?

Because CollapsibleTabs depends on a drop down menu being present, my MenuToTabs gadget technically breaks it. This gives the odd effect of the History tab just moving to the #p-caction tabs. Short of removing each .collapsible class from all tabs, are there any other way of controlling collapsibility? — Edokter (talk) — 20:14, 26 June 2011 (UTC)

The Vector extension has full support for the toggling of individual features. This includes collapsibletabs.

By default, wikis installing this extension have collapsibletabs enabled for everyone without the option for users to disable it. This was probably done because it fixes problems where tabs would not fit on the screen (why would someone disable it ?).

But in case of Gadgets, you probably want to allow users to enable it. Simply set user to true to allow users to disable it (users using your gadget for example). Look here for the default configuration. Set the folllowing in LocalSettings.php (or, if for Wikipedia et al.), request so in bugzilla::

$wgVectorFeatures['collapsibletabs']['user'] = true;

Krinkle 21:05, 26 June 2011 (UTC)

Is the extention in any way configurable by the user? I need to be able to disable it on enwiki to test what is causing the IE6 javascript bug. This extension may be involved as it consistently refuses to collapse the left toolbar on IE6 as well, wether there are errors or not. — Edokter (talk) — 12:58, 3 July 2011 (UTC)

I already answered this in the previous message. The Vector extension has full support for every featured to be toggled on both a site-wide basis and a per-user basis, including at the same time.

However the installation of the extension at Wikipedia has disabled the per-user configuration for some features, likewise some features disabled by default (the ones not stable yet). Krinkle 22:54, 3 July 2011 (UTC)

Let me rephrase: Is there any way to disable it in javascript? — Edokter (talk) — 22:43, 16 July 2011 (UTC)

Suggestions

Hi,

from the code I can see that your extension tries to handle the suggestions by itself. However if I don't comment out the part where you disable the mwsuggest feature, I don't get any suggestions at all? Nothing popping up, just as if there would be no suggestion feature at all? Do I need to do something special? (The documentation is rather sparse...)

I'm using 1.17.0 and latest Vector from svn 83.65.127.178 11:55, 27 June 2011 (UTC)

So far I've got the same problem. Can't seem to get search suggestions without MWSuggest enabled and commented out from the Vector-code. KristianS 20:46, 3 August 2011 (UTC)

We got a similar problem with the latest trunk versions (r93825) on our test system where MWSuggest does not work while our production system uses a more outdated Vector version (trunk r89954) with MWSuggest working as advertised. MWJames 04:23, 4 August 2011 (UTC)

(Un)CollapsibleTabs

I made a script that makes the menu turn to tabs and vice-versa, by clicking the arrow. Would this be a feature worth adding to the extension? — Edokter (talk) — 22:09, 10 July 2011 (UTC)

Bump? — Edokter (talk) — 18:36, 18 November 2011 (UTC)

As far as I know the click event is used in core already as of 1.18 or 1.19; Use case being tablets viewing a MediaWiki site, unable to do :hover on a touch device. Krinkle 23:32, 18 November 2011 (UTC)

I know there is a click event to make the menu appear, but not the turn it into tabs (and vice versa). (Although I never considerd touch devices, there are ways around that; touch 1: appear, touch 2: toggle.) — Edokter (talk) — 14:37, 19 November 2011 (UTC)

How to enable SectionEditLinks?

I don't know how to use it. Does this figure really exist？ Zoglun 13:53, 12 July 2011 (UTC)

Not working for me either. The module files are missing. I grabbed them from the trunk version, but that still does not get them enabled. 85.80.205.112 17:10, 15 August 2011 (UTC)

SectionEditLinks is enabled by default, you can enable it via your preference under editing, then right click on sections to edit. 97.115.150.66 17:53, 24 August 2011 (UTC)

This thread is about the Vector extension feature "SectionEditLinks", not about the ability itself to edit a page by section.

The feature is that the editsection-links are positioned to the left with a pencil, which, according to usability research and edit statistics makes it easier to users to recognize which links belongs to which section, and it also resulted it more people going to edit. Krinkle 21:46, 24 August 2011 (UTC)

Same problem here. I spent a couple of hours of trying to get it to work or finding information about it.

It is really unfortunate that an Extension so widely in use and in the install bundle is documented that poorly...

Is SectionEditLinks supposed to work or not? Under what conditions? And how?

For those who know it shouldn't be too hard to add a line or two in the section potentially saving people hundreds of hours of trying to get this feature to work... 87.179.165.9 13:45, 24 December 2011 (UTC)

And same problem here. I recently upgraded to MW 1.18.1, and have now switched my users to the Vector skin and enabled this extension (version 0.30.0). I get the new SimpleSearch box (so I know the extension is active), but see no change in the SectionEditLinks.

Is there something to do to turn this on? Does it require a more-recent version of MediaWiki? Or what? Paul Lustgarten (talk) 20:24, 11 July 2012 (UTC)

"It is really unfortunate that an Extension so widely in use and in the install bundle is documented that poorly..."

I fully agree with that. Just look at the problems people have with the new menu. As soon as stuff works for WP, devs don't care much anymore. Subfader (talk) 06:46, 12 July 2012 (UTC)

People, I think "they" are still working on this but this will probably be implemented with the arrival of Parsoid and VisualEditor. See Link for a discussion.

When you do want to try and enable 'sectioneditlinks' you can do this in Vector.php. It is listed under the "unstable" features. I tried it with a clean MW 1.19 in Firefox 13.0.1 but it does not work, it only breaks the 'collapsiblenav' feature.

// Each module may be configured individually to be globally on/off or user preference based
$wgVectorFeatures = array(
	'collapsiblenav' => array( 'global' => true, 'user' => true ),
	'collapsibletabs' => array( 'global' => true, 'user' => false ),
	'editwarning' => array( 'global' => false, 'user' => true ),
	'simplesearch' => array( 'global' => false, 'user' => true ),
	// The follwing are experimental and likely unstable - use at your own risk
	'expandablesearch' => array( 'global' => false, 'user' => false ),
	'footercleanup' => array( 'global' => false, 'user' => false ),
	'sectioneditlinks' => array( 'global' => false, 'user' => false ),
);

I am not really a programmer but maybe the solution is not so difficult when someone with "knowledge" looks at the Java code (ext.vector.sectionEditLinks.js) and the style sheet (ext.vector.sectionEditLinks.css). Felipe de Jong (talk) 09:51, 12 July 2012 (UTC)

Thank you for your feedback. Zoglun (talk) 21:29, 23 July 2012 (UTC)

My left menu won't collapse

I have installed the extension as described, I have inserted the necessary text into local.php, yet the menu won't collapse. Stranger yet: I have 2 wikis: collapsible menu works in one wiki, but not int the other. Same extensions installed, same localsettings.php. Could there be some problem with style sheets? I have differences there. Thanks for any tip. Anja 129.233.51.12 13:03, 26 July 2011 (UTC)

I have the same. It just won't collapse. Its not the browser, since the collapse of the SideBar here works.

Any requirements on the links on the SideBar page? I just have a bunch of

• title
  • Pagename1|alias1
  • Pagename2|alias2
  • Pagename3|alias3
  • Pagename4|alias4
• title2
  • Category:name1|alias5
  • Category:name2|alias6

....LocalSettings.php :

require_once( "$IP/extensions/Vector/Vector.php" );

$wgDefaultUserOptions['useeditwarning'] = true;

$wgVectorFeatures['editwarning']['global'] = true;

$wgVectorFeatures['editwarning']['user'] = true;

$wgVectorUseSimpleSearch = true;

$wgVectorFeatures['collapsiblenav']['global'] = true;

$wgVectorFeatures['collapsiblenav']['user'] = false;

MediaWiki 1.17.0

PHP 5.3.8 (apache2handler)

MySQL 5.0.91-community

Installed extensions

Special pages

ChangeAuthor (Version 1.1)

EditUser (Version 1.6.1)

Password Reset (Version 1.7)

User Merge and Delete (Version 1.6.1)

Cite

DynamicPageList (Version 1.8.9)

MobileDetect (Version 1.0b)

ParserFunctions (Version 1.4.0)

RegexFunctions (Version 1.4.1)

Author Protect (Version 1.2)

ConfirmEdit

FCKeditor

Lockdown

Vector (Version 0.3.0) 84.196.119.55 00:17, 22 October 2011 (UTC)

Its working now.

In Localsettings i removed all the options.

only require_once( "$IP/extensions/Vector/Vector.php" ); remains.

I also moved it up.

it is now the first extension defined, just after the $wgDefaultSkin = "vector";

Maybe that is related 84.196.119.55 11:31, 24 October 2011 (UTC)

Thank you. That did it for me. There is inherent confusion in that having the 'Vector' style as your default does not automatically give you the collapsing menus. You MUST add this line in LocalSettings.php as well.

require_once("extensions/Vector/Vector.php" ); 173.10.110.108 00:56, 16 March 2012 (UTC)

MW 1.18.0 and none of the settings work. I also tried moving it up and down in LocalSettings.php

$wgDefaultSkin = 'vector';

require_once("$IP/extensions/Vector/Vector.php");

$wgVectorFeatures['collapsibletabs']['global'] = false;

$wgVectorFeatures['collapsibletabs']['user'] = false;

$wgVectorFeatures['collapsiblenav']['admin_tools'] = false;

$wgVectorFeatures['collapsiblenav']['user'] = false;

$wgVectorFeatures['editwarning']['global'] = true;

$wgVectorFeatures['editwarning']['user'] = true;

$wgVectorFeatures['expandablesearch']['global'] = false;

$wgVectorFeatures['expandablesearch']['user'] = false; Subfader 22:08, 10 December 2011 (UTC)

Tried on second clean installion. The same. Also the user setting doesn't appear in the prefs. No effect and not working at all! Subfader 11:17, 12 December 2011 (UTC)

I guess this is worth a bug report. Cheers [[kgh]] 13:15, 12 December 2011 (UTC)

I don't care much anymore since I decided to go for Monobook as default skin for another while, but here you go https://bugzilla.wikimedia.org/show_bug.cgi?id=32989 Subfader 17:15, 12 December 2011 (UTC)

I never went Vector. Still I believe it was the right decision to let them know that there is something not working as it is expected or as it should. Cheers [[kgh]] 20:00, 12 December 2011 (UTC)

Hello Guys,

I try to use the expandable nav in the sidebar. It doesn't work for me.

I use the mediawiki 1.18 and I try the stable version of the vector extension and also the development branch. Both of them didn't work.

In my LocalSettings, I add only one line:

require_once( "$IP/extensions/Vector/Vector.php" );

I try also to add it directly behind the Default Skin Line.

Nothing worked for me, any Idea to troubleshot the problem?

Thanks - Helmut 178.201.91.139 12:23, 10 April 2012 (UTC)

Set the number of search suggestions?

Is there any way to change the number of AJAX search suggestions displayed in the SimpleSearch box? In Monobook you can change $wgMWSuggestTemplate to append &limit=20. SimpleSearch does not respect $wgMWSuggestTemplate however. (It probably should....)

Thank you. Maiden taiwan 21:10, 27 July 2011 (UTC)

Delay before collapsing on page load

When I reload this page, the collapsible sidebar is shown at once. But when I reload a page on my own mediawiki install with Vector installed, it first shows the old menu, then on page load replaces it with the new collapsible version. How can it be prevented that the old version is briefly shown first? 83.117.230.8 10:03, 29 July 2011 (UTC)

i'm getting the same problem with my wiki. also, i kept navigation as a header, it disappears on reloading a page. 112.207.218.134 14:18, 30 August 2011 (UTC)

It appears that this is by design. go to the mediawiki.org homepage and refresh, you'll see the same behavior. 165.212.186.27 23:47, 15 August 2012 (UTC)

Alignment of search suggestions

On MediaWiki-wikis the search suggestions are aligned with the right side of the search box, so that long titles expand towards the left. (Example: Search for "Category:Discussion and forum extensions" on this wiki). On my test-wiki, 1.17.0 basic install, Vector skin with the latest Vector extension, the search suggestions align with the left side of the search box. This causes long titles to widen the site enough to produce horisontal scroll bars.

How and where do I configure the wiki to align the results with the right side of the search box?

Thanks for any answer or comment. KristianS 13:08, 9 August 2011 (UTC)

Complete slow down

This theme completely slowed down my wiki. 147.188.254.156 16:27, 24 August 2011 (UTC)

Problem with tab names.

Hi, after our wiki upgrade to MediaWiki 1.17.0 and Vector (Version 0.3.0) (r95680). Something got messed up with the tab names, most of the tab names has lost it's names (for example on this page I wont see the extension and duscussion text) the special pages show as <vector-namespace-special> and User pages shouw user and user ... here is an screenshot to ilustrate the problem.

any Ideas on how to fix that, because it really driving me mad.Mor2 23:45, 19 September 2011 (UTC)

I'm also having this problem, would love to see a fix. Can see http://gamification.org for example of the problem. 76.21.57.88 01:05, 20 September 2011 (UTC)

It seems that we had a problem with the older 1.16 Vector extension that wasnt compatible, we fixed and now it works, however there is another tiny problem, that I would appreciate some help with. The 'new pages' tabs do not show in red and the new pages itself has some weird numbers popping at the corner of the screen. i realise that my description probably isnt that good so I have created an illustration for you guys.

Any ideas what the problem might be or what is the relevant code that we should be looking into? Mor2 12:58, 9 October 2011 (UTC)

Sorry to bump this thread up, but could you please tell how did you fix it? I also having this problem too. Thanks very much :) Korrawit 04:40, 15 November 2011 (UTC)

Hi guys,

I had the same problem and I could solve it:

The vector skin from 1.16.x is not compatible with MediaWiki 1.17. There e.g. are breaking changes inside the file skins/Vector.php, which is why you do no longer see the right tab names (but something like <vector-namespace-special> instead.

Do the following: Remove the folder skins/vector/ and the file skins/Vector.php and replace them by the version which comes with your MediaWiki 1.17 package. After that the skin should be working correctly again.

Things are more tricky if you (like me) have created a custom skin based on vector, which now shows these errors. I think in that case the only solution is to compare the old and the new version of vector and to adjust your skin by hand. :-( 88.130.100.238 21:39, 20 November 2011 (UTC)

Thanks very much. It really helps! Korrawit 03:44, 24 November 2011 (UTC)

It seems that we had a problem with the older 1.16 Vector extension that wasnt compatible, we fixed and now it works, however there is another tiny problem, that I would appreciate some help with. The 'new pages' tabs do not show in red and the new pages itself has some weird numbers popping at the corner of the screen. i realise that my description probably isnt that good so I have created an illustration for you guys.

Any ideas what the problem might be or what is the relevant code that we should be looking into? Mor2 12:58, 9 October 2011 (UTC)

EditWarning non working

Hi folks, I just setup the Vector extension on a vector style 1.17 Mediawiki (french). I checked any parameters needed as well as users preferences, but nothing helps... I still face no warning when I quit the editor (FCKEditor), allowing to loose all changes in case of navigator error (ie : especially on laptop which handles specific shortcuts for previous page). Any idea ? 212.74.185.22 15:31, 28 September 2011 (UTC)

Hi all... The extension is finally working... After a few hours of patience.

Something with the browser cache I guess. Cheers. 212.74.185.22 08:55, 29 September 2011 (UTC)

How to remove "Take me Back" and "New Features" at top of every page?

I am a sysop and I administer a site with this vector extension installed. However, when logged in I see two links with text "take me back" and "New features" left of my user name on top of every page. Clicking these links takes to a wiki description of the vector skin and other things unrelated to my site. How can I disable/remove these two links. Wikimanz 16:09, 23 October 2011 (UTC)

What does 'footercleanup' do?

This extension is poorly explained. What does 'footercleanup' do?

$wgDefaultSkin = 'vector';
require_once("$IP/extensions/Vector/Vector.php");
$wgVectorFeatures['footercleanup']['global'] = true;

seems to have no effect on the footer. Subfader 12:05, 13 December 2011 (UTC)

It makes the footer of the edit page (the place where save page, preview etc are) more compact. Bookysmell (talk) 03:46, 9 September 2012 (UTC)

What does the 'simplesearch' do?

<pre>$wgDefaultSkin = 'vector'; require_once("$IP/extensions/Vector/Vector.php"); $wgVectorUseSimpleSearch = true;

has no effect on the search in Vector skin for me. Subfader 12:38, 13 December 2011 (UTC)

The search bar should look very different. Check this screenshot for example. On the right is with SimpleSearch enabled. Krinkle 01:08, 15 December 2011 (UTC)

Ah, works now. Thanks. Subfader 09:33, 15 December 2011 (UTC)

Here its not working either, how did you fix it?

I wrote the same lines that Subfader.. 177.69.29.113 13:05, 24 April 2012 (UTC)

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? 205.254.147.8 16:59, 11 May 2012 (UTC)

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

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

in skin/vector.php (line 468) 78.220.29.24 16:39, 3 September 2013 (UTC)

How to use Vector features for new skin?

Hi,

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)

How to create a skin FooBar based on the default skin Vector Pastakhov 13:32, 21 December 2011 (UTC)

That's not what he asked. He wants to know how to use the Vector extension with a skin that is based on Vector. 194.80.246.1 21:24, 4 February 2012 (UTC)

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. Ashimema (talk) 18:49, 22 March 2012 (UTC)

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... FreedomFighterSparrow (talk) 21:27, 22 March 2012 (UTC)

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. Kryand (talk) 21:29, 12 February 2013 (UTC)

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...) FreedomFighterSparrow (talk) 18:41, 18 February 2013 (UTC)

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. 109.226.59.54 16:58, 22 September 2013 (UTC)

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. 109.226.59.54 16:20, 23 September 2013 (UTC)

Does vector ignores $wgUseFileCache?

Hello,

im using vector now and its causing a very high CPU load, like Im disabling $wgUseFileCache. When i delete the cache and let it build up again, its done in 1-2 hours, but Vector is causing this load over days. Is vector ignoring or disturbing the cache? 77.1.84.229 19:44, 15 February 2012 (UTC)

Did you recently upgrade? MySQL load / CPU usage raised since MW 1.17 Subfader (talk) 11:06, 16 February 2012 (UTC)

No i didnt upgrade recently.

I deinstalled Vector yesterday and now the CPU usage is low again. 77.1.94.54 15:34, 16 February 2012 (UTC)

I skipped MW 1.17 and 1.18 for other reasons. It didn't feel faster at all. The Ressource Loader is evil. MW 1.19 will be released soon. Waiting may be worth it. Subfader (talk) 17:39, 16 February 2012 (UTC)

Do you think that MW 1.19 will overcome this shortcoming observed here? I guess it very uncool to cause a high CPU load in case it is not necessary. So far I skipped Vector (skin and this extension) for various reasons but I guess it will become inevitable to use it one day. Cheers [[kgh]] (talk) 18:41, 16 February 2012 (UTC)

CPU: Most probably it won't be solved.

ResourceLoader 2 is scheduled for later this year. Subfader (talk) 20:13, 16 February 2012 (UTC)

Conflict!! When ExpandableSearch and SimpleSearch enable at the same time

I think a expandable simple search bar will be gorgeous.

Can anyone fix it? Zoglun (talk) 02:17, 24 February 2012 (UTC)

Vector sidebar Functionality Broken?

I have been banging my head against the wall trying to figure out why this is not working. Maybee someone can help.

When I use this in the markup: {{#subpages:format=sidebar}}

It outputs a line of code like this: *MediaWiki:Sidebar/testing|testing

And on the MediaWiki:Sidebar page it looks like it should but on the actual sidebar it is not parsing it into a list item. I am not understanding why because as a preprocessor it should render the output before the nav bar processes the rest of the page. This was proven by: ** {{# ifeq: Vector | Vector | True | False }} | {{# ifeq: Vector | Vector | True | False }} as well as by pasting the output into the markup section alone.

Any help is appreciated. Thrasmion (talk) 03:28, 12 March 2012 (UTC)

Clarity needed for Vector default options like $wgDefaultUserOptions['vector-simplesearch']

This edit by me was undone as "not unnecessary". I disagree and ask to have it reinserted into the page in an appropriate way. We just struggled for two days trying to figure out why the simple search box wasn't displaying in our mediawiki. We couldn't find any references to these default terms, especially

$wgDefaultUserOptions['vector-simplesearch'] = 1;

Even when googling that exact variable, this wiki does not show up in the first 10 results. This seems to indicate there is a gap in the documentation and that is what I was trying to address with my edit. The default user options for Vector need to be more clearly spelled out and this extension page would seem like the appropriate page to do so. Thank you. Don 205.254.147.8 20:38, 11 May 2012 (UTC)

Works for me without that. Jasper Deng (talk) 23:04, 11 May 2012 (UTC)

Works for me as well.

You did set:

$wgVectorUseSimpleSearch = true;

right ? Krinkle (talk) 23:27, 12 May 2012 (UTC)

Invalid response from Extension Distributor remote client.

Getting the above error when going to the download page.

MediaWiki = 1.19.1 PHP = 5.3.15-pl0-gentoo (apache2handler) MySQL = 5.1.62-log James3mc (talk) 22:25, 18 October 2012 (UTC)

All extensions on GIT have that error Subfader (talk) 08:25, 19 October 2012 (UTC)

< MW1.18.6 what is the trick?

I am trying to use ArticleFeedback extension. I have noticed that it is not playing nice with Vector. Also, I am using git and I think I have tried every combination of MW1.19 and greater with Vector and I can't find the combination.

How do I get Vector working with MW 1.20+ AND ArticleFeedback?

Any help would be greatly appreciated.

Margaret 144.15.255.227 15:31, 5 December 2012 (UTC)

Install MediaWiki 1.20, with the 1.20 version of Vector and 1.20 version of ArticleFeedback? Krinkle (talk) 23:43, 14 December 2012 (UTC)

my collapse navigation not work

i have install wiki 1.20.2 but my collapse navigation not work any ideas i have apache server mysql database and wiki 1.20.2 115.69.156.210 19:19, 6 December 2012 (UTC)

I also just installed Mediawiki 1.20.2 but the collapse functionality of the extension "Vector" does not work. Is there any instruction how to get this to work? 83.228.142.188 02:02, 11 December 2012 (UTC)

I had this same problem and I was using the master branch from Git. I switched to the REL1_20 branch (git checkout REL1_20) and it works fine now. Jamie Thingelstad 22:24, 20 December 2012 (UTC)

Hello everybody, having the same issue, my left navbar isn't work correctly. Is there a how-to-fix guide or any other useful stuff, to fix this bug? Tested with following browser: Firefox 17.0.1, Google Chrome 23.0.1271.97 m, Rockmelt 0.16.91.483, Opera 12 and IE 9.0.8112.16421 (only working with Rockmelt (shows the Toolbox). Any help is appreciated. Abani79 (talk) 12:25, 27 December 2012 (UTC)

Same problem. New clean 1.20.2 installation. Never filed a bug, someone can do that please? 88.134.160.61 00:36, 17 January 2013 (UTC)

This isn't a bug. The master branch isn't compatible with 1.20.2. You need to checkout the right branch. See my comment above. Jamie Thingelstad 02:58, 17 January 2013 (UTC)

I'm not a GIT user and I'm very.. new to using wikis. How do we change vector versions to fix this? 99.177.222.135 09:33, 23 January 2013 (UTC)

This version was tagged for the MW 1.20 branch: tgz [[kgh]] (talk) 12:56, 23 January 2013 (UTC)

Vector / notitle prob

hey,

i'm using Vector and notitle - but it seems that there is a problem: notitle does not work.

vektor overwrites notitle :( - any ideas?

greetings from germany torferde 2001:638:708:30D1:500B:6200:FE03:A563 15:14, 31 January 2013 (UTC)

Hallo und Gruß aus dem Lande. :)

Sie nutzen den Vektorskin, aber es wird kein Titel ausgegeben, meinen Sie damit den Titel ihres Wiki oder worauf wollen Sie hinaus? Ein Beispiel könnte ggf. helfen, ihr Problem besser nachzuvollziehen. Abani79 (talk) 15:30, 31 January 2013 (UTC)

Hui,

ich nutze die Erweiterung NoTitle und möchte auf der Hauptseite den Titel ausblenden ("Hauptseite"), nach einem ?action=purge ist der auch weg, kommt aber wieder. Nach bisher nicht nachvollziehbaren Aktionen.

Wenn ich die Extension:Vektor ausmache, dann gehts. Und ja als Skin nutzen wir auch Vektor.

torferde 2001:638:708:30D1:500B:6200:FE03:A563 15:50, 31 January 2013 (UTC)

Problem genauer gefunden:

immer wenn ich die Navigation aus bzw einklappe wird die andere extension unwirksam :( 2001:638:708:30D1:500B:6200:FE03:A563 16:42, 31 January 2013 (UTC)

Da mit dieser Erweiterung derzeit noch auf experimentieller Basis gearbeitet wird, wäre es vielleicht sinnvoll, diese noch vom Entwickler weiter ausreifen zu lassen und stattdessen eine Alternativmethode anzuwenden.

Versuchen Sie body.page-Main_Page h1.firstHeading { display:none; } in Ihrer MediaWiki:Common.css Datei einzufügen, evtl. könnte das Ihr Problem lösen.

Gruß Sandro Abani79 (talk) 17:05, 31 January 2013 (UTC)

I would like to suggest to only communicate in English. Otherwise your posts will more than likely be ignored by developers. You cannot even blame people for doing this. However, this talk should better be on the NoTitle page. Besides, the NoTitle extension is experimental and currently being reworked. [[kgh]] (talk) 16:54, 31 January 2013 (UTC)

sorry, i forgot to write in englisch :)

let's go to NoTitle to solve the problem ;) 2001:638:708:30D1:500B:6200:FE03:A563 17:05, 31 January 2013 (UTC)

Core javascript features not working after upgrading from 1.16 to 1.20.2

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
TypeError
 load.php:151
Exception thrown by ext.vector.collapsibleNav: Cannot call method 'test' of undefined load.php:151
TypeError
 load.php:151
Exception thrown by mediawiki.searchSuggest: Object #<Object> has no method 'first' load.php:151
TypeError

85.112.162.30 10:09, 13 March 2013 (UTC)

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. Krinkle (talk) 01:51, 14 March 2013 (UTC)

I had similar problem with BugzillaReports extension. I disabled the jquery loaded by this extension and the problems went away. Noti1234 (talk) 13:02, 25 February 2014 (UTC)

I've hit the same problem with BugzillaReports, can you explain how you disabled the jquery for the extension? 137.69.117.62 18:38, 18 May 2015 (UTC)

I had a similar issue - try disabling CollapsibleTabs. Immewnity (talk) 00:26, 19 June 2013 (UTC)

SectionEditLinks conflict with CollapsibleNav

When $wgVectorFeatures['sectioneditlinks']['global'] = true; , the navbar does not Collapse, and no icon or any change could be observed around title.

Please fix it as soon as possible, the SectionEditLinks problem last at least one year.

environment: MW 1.20.3 with default packed vector extension Zoglun (talk) 06:22, 17 March 2013 (UTC)

Same problem here. It has same problem in MW 1.20.5. Anyone can solve this? 211.61.23.35 06:19, 16 May 2013 (UTC)

Simplesearch and Full-text

Hi, I've installed Simplesearch on our internal wiki (on 1.17) which is much more suitable for our purposes. However I'm struggling to figure out how to make the default search a full-text one, ie instead of jumping directly to the relevant page if an exact match is found, I'd like it to return a list of all hits with the exact match link at the top. Right now I have the following in localsettings.php:

<div id="p-search">
	<h5<?php $this->html('userlangattributes') ?>><label for="searchInput"><?php $this->msg( 'search' ) ?></label></h5>
	<form action="<?php $this->text( 'wgScript' ) ?>" id="searchform">
		<input type='hidden' name="title" value="<?php $this->text( 'searchtitle' ) ?>"/>
		<?php if ( $wgVectorUseSimpleSearch && $wgUser->getOption( 'vector-simplesearch' ) ): ?>
		<div id="simpleSearch">
			<?php if ( $this->data['rtl'] ): ?>
			<button id="searchButton" type='submit' name='button' <?php echo $this->skin->tooltipAndAccesskey( 'search-fulltext' ); ?>><img src="<?php echo $this->skin->getSkinStylePath('images/search-rtl.png'); ?>" alt="<?php $this->msg( 'searchbutton' ) ?>" /></button>
			<?php endif; ?>
			<input id="searchInput" name="search" type="text" <?php echo $this->skin->tooltipAndAccesskey( 'search' ); ?> <?php if( isset( $this->data['search'] ) ): ?> value="<?php $this->text( 'search' ) ?>"<?php endif; ?> />
			<?php if ( !$this->data['rtl'] ): ?>
			<button id="searchButton" type='submit' name='button' <?php echo $this->skin->tooltipAndAccesskey( 'search-fulltext' ); ?>><img src="<?php echo $this->skin->getSkinStylePath('images/search-ltr.png'); ?>" alt="<?php $this->msg( 'searchbutton' ) ?>" /></button>
			<?php endif; ?>
		</div>
		<?php else: ?>
		<input id="searchInput" name="search" type="text" <?php echo $this->skin->tooltipAndAccesskey( 'search' ); ?> <?php if( isset( $this->data['search'] ) ): ?> value="<?php $this->text( 'search' ) ?>"<?php endif; ?> />
		<input type='submit' name="go" class="searchButton" id="searchGoButton"	value="<?php $this->msg( 'searcharticle' ) ?>"<?php echo $this->skin->tooltipAndAccesskey( 'search-go' ); ?> />
		<input type="submit" name="fulltext" class="searchButton" id="mw-searchButton" value="<?php $this->msg( 'searchbutton' ) ?>"<?php echo $this->skin->tooltipAndAccesskey( 'search-fulltext' ); ?> />
		<?php endif; ?>
	</form>
</div>

Rather out of my depth with php code but would be grateful for any pointers. thanks Themicksa (talk) 14:32, 12 April 2013 (UTC)

sorry, that code is in vector.php NOT localsettings.php Themicksa (talk) 15:22, 12 April 2013 (UTC)

Collapsing only on some pages

I've implemented CollapsibleNav on http://www.pidgi.net/wiki/Main_Page , but it doesn't always collapse. Any ideas? Immewnity (talk) 02:07, 18 June 2013 (UTC)

Solved. Disabling CollapsibleTabs made it work! Immewnity (talk) 00:25, 19 June 2013 (UTC)

expandablesearch broken sinse 1.21.1

Hi folks, I had activeated some vector features for a while without any problem. But since the latest mediawiki update 1.21. the expandablesearch feature is broken. The search box no longer expands, its showing a scrollbar now. Tested in 3 differents wikis with several browsers. My Setting is: $wgVectorFeatures['expandablesearch']['global'] = true; Can someone confirm that and will there be a workaroun?

THX, Brocchinia (talk) 21:01, 7 July 2013 (UTC)

Monobook support

Please add support for monobook so the toolbar looks like vector but instead it is on the left in the sidebar please 90.209.96.40 18:07, 16 August 2013 (UTC)

First level text disappears

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

Has anyone found a way around that?

Thanks Wade.courtney (talk) 23:57, 21 November 2013 (UTC)

CollapsibleNav - problem with MW 1.22.7

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?

Thx! Mrnett1974 (talk) 19:50, 2 June 2014 (UTC)

collapsibleNav is not configurable. The bug will not be fixed, see bugzilla:39035#c10. Nemo 10:13, 3 June 2014 (UTC)

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. [[kgh]] (talk) 11:41, 3 June 2014 (UTC)

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. [[kgh]] (talk) 09:56, 7 July 2014 (UTC)

I have created (and I am using it on my MediaWiki 1.23 wikis) code that can be added to LocalSettings.php to disable collapsible sidebar on MediaWiki 1.23 without modifications of MediaWiki files. The code is available at:

https://github.com/DavisNT/CodeSamples/blob/master/MediaWiki%20hacks/Disable%20Collapsible%20Sidebar%20on%20MW%201.23.php This code is not tested on MediaWiki 1.22. DavisNT (talk) 16:41, 28 June 2014 (UTC)

I have a similar problem, I just tried to insert the code of DavisNT and it works on version 1.22.6 37.77.117.146 00:56, 15 July 2014 (UTC)

clarification on what it means to be bundled vs core.

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? Zeefreak (talk) 14:34, 12 December 2014 (UTC)

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. [[kgh]] (talk) 01:15, 13 December 2014 (UTC)

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. Zeefreak (talk) 15:42, 16 December 2014 (UTC)

MW 1.24.1 Fresh Install - Vector sidebar does not collapse

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. 75.88.176.235 05:45, 23 January 2015 (UTC)

For users that use Mediawiki 1.24 or higher can use the CollapsibleVector extension to get "collabsiblenav" (collabsible navigation) back. Rob Kam (talk) 07:02, 23 January 2015 (UTC)

Vector not working

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. Hansel2324 (talk) 20:06, 8 December 2015 (UTC)

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 :-/ 87.173.22.166 (talk) 08:07, 20 February 2016 (UTC)

Seems to be a installation/upgrade-bug

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

works fine for me. 87.173.22.166 (talk) 08:36, 20 February 2016 (UTC)

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. 213.55.103.174 (talk) 07:05, 31 March 2016 (UTC)

The 'Monobook' skin runs fine Hansel2324 (talk) 20:07, 8 December 2015 (UTC)

I also can't get PageTriage or WikiEditor to work either and I don't know if the issues are related. Hansel2324 (talk) 20:08, 8 December 2015 (UTC)

Issue already reported in 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. Ciencia Al Poder (talk) 10:49, 9 December 2015 (UTC)

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? Hansel2324 (talk) 14:23, 10 December 2015 (UTC)

See Manual:Installation requirements Ciencia Al Poder (talk) 20:45, 10 December 2015 (UTC)