Extension talk:Vector
Contents
 First page |
 Previous page |
 Next page |
 Last page |
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.
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
$wgDefaultSkin = 'vector';
require_once("$IP/extensions/Vector/Vector.php");
$wgVectorUseSimpleSearch = true;
has no effect on the search in Vector skin for me.
The search bar should look very different. Check this screenshot for example. On the right is with SimpleSearch enabled.
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?
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
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)
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
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;
Tried on second clean installion. The same. Also the user setting doesn't appear in the prefs. No effect and not working at all!
I guess this is worth a bug report. Cheers
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
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)
That's not what he asked. He wants to know how to use the Vector extension with a skin that is based on Vector.
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.
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...
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: Extension talk:Vector/Vector sidebar Functionality Broken? | Extension talk:Vector/Vector sidebar Functionality Broken? | True | False }} | {{# ifeq: Extension talk:Vector/Vector sidebar Functionality Broken? | Extension talk:Vector/Vector sidebar Functionality Broken? | True | False }} as well as by pasting the output into the markup section alone.
Any help is appreciated.
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?
No i didnt upgrade recently. I deinstalled Vector yesterday and now the CPU usage is low again.
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.
I don't know how to use it. Does this figure really exist？
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.
SectionEditLinks is enabled by default, you can enable it via your preference under editing, then right click on sections to edit.
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.
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...
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.
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.
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 :)
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. :-(
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)
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?
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)
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 ?
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' ); }
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?
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.
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
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.
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.
First page |
Previous page |
Next page |
Last page |
