Template talk:Navbox/Archive 13

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Archive 12 Archive 13 Archive 14

More groups

Can someone changes this so that more than 20 groups? I made the Template:Portuguese infantes and the Template:Portuguese infantas by marriage. But nothing beyond the 20th generation shows up. --Queen Elizabeth II's Little Spy (talk) 01:04, 14 November 2009 (UTC)

No, sorry. See #More than 20 groups above. EdokterTalk 01:08, 14 November 2009 (UTC)
Actually, since it was archived, see the first item in the "Please read before posting" box at the very top of the page instead. ダイノガイ千?!? · Talk⇒Dinoguy1000 11:13, 19 November 2009 (UTC)

Multiple Navboxes

I have seen the code in Common.css that is as follows:

table.navbox + table.navbox {

This code makes sure that top/bottom borders are shared between navboxes on pages that feature multiple ones at once. On Wikipedia most pages that feature this are implemented like so:


...with each template call on a different line. However, on my Wiki, if you do that (each on its own line) you get random blank space in between them. After a page is served, if you look at the page source, you see the following in between the navboxes:

<p><br />

This mysterious insertion of blank space disappears if you call the templates like this:


...I.e. all on the same line.

As far as I can tell, there is no difference between our navboxes and the ones on Wikipedia that would make this occur. This also does not occur if I directly use the "navbox" class on two sequential, hand-coded tables. Now, we're on 1.13.2, not the latest of 1.15.1 or whatever it currently is. Is this some sort of well-known transclusion bug in older versions? Or is this a clear sign that there's something majorly wrong with our navboxes?
--Cogniac (talk) 14:42, 23 December 2009 (UTC)

First thing to check for in your navbox, and the templates that use it, is the presence of extranious linebreaks. Note the every linebreak in our template is surrounded by HTML comment tags, so Mediawiki does not interpret them as linebreaks. Two linebreaks (even if not on the same page) causes Mediawiki to insert a <p>. EdokterTalk 15:10, 23 December 2009 (UTC)
Aha. Well played, sir. We had a {{{category}}} parameter at the bottom for attaching a category on every transcluding page, and that was on a new line right after the table itself. When this was compressed and put on the same line as the end of the table, the blank space went away. Thanks!
--Cogniac (talk) 16:12, 23 December 2009 (UTC)
Glad to be of help. EdokterTalk 16:18, 23 December 2009 (UTC)

Wikia based Navbox (with collapsed groups) and help on show and hide group of Navbox

Hello and please help. Over at E-Wrestling Encyclopedia, I have a navbox collapsed groups template located at here, I noticed that the groups listings are shown when they are ment to be hidden. I copied the files accordingly and still have and issue. What is the problem?

Second problem that mainly is a from this article, over at Dog The Bounty Hunter Wiki, I have a problem with the code #ifexist code in the navbox template shown on this article. How do I fix the problem. The templates are located at Template 1 and Template 2.

Thanks for the help, Merry Christmas, and a Happy New Year.

Sundogs Wikia UserPage | Roller Derby Wiki 15:06, 25 December 2009 (UTC)

Is this how you meant it? If you transclude parts of tables in wikicode, you have to replace | with {{!}}. Svick (talk) 21:53, 25 December 2009 (UTC)

No more than twenty groups?

I made a navbox ({{Buteoninae}}) for all the Buteoninae species. I'm not sure why, but for some reason, all of the groups listed that are higher than twenty are hidden. There is no "show" button, and they can only be seen when editing it. Is there some automatic feature I don't know about, or did I type something in wrong? --The High Fin Sperm Whale (TalkContribs) 01:36, 29 December 2009 (UTC)

This template doesn't support more than twenty groups, you can use {{Navbox long}} that supports up to 38 of them. Also, as the documentation of that template says: “if you really need that many groups, please first consider if the template you are working on is too large to be useful”. Svick (talk) 01:48, 29 December 2009 (UTC)
Thanks. I think it is useful, because there are lots of animal templates, such as {{Carnivora}}, that are very long indeed. But now there is another problem:group24 is called Ichthyophaga, but the name of the group isn't there and so the contents are in the middle of the template, instead of the edge. --The High Fin Sperm Whale (TalkContribs) 02:21, 29 December 2009 (UTC)
There was a typo in {{Navbox long}} that caused the problem with group24, I fixed it. I also set the width of the column with group names in your template, so that it looks better. Svick (talk) 02:36, 29 December 2009 (UTC)

Problem with color

Template:Cultural Properties of Japan has some light-blue (#F7F7F7) background colors in the "Lists" rows. I don't see this color mentioned in the code and don't know how to get rid of it (=make it white like the "Designations" rows). Pleas help. bamse (talk) 08:37, 29 December 2009 (UTC)

See Template:Navbox#Style_parameters, parameters oddstyle, evenstyle and evenodd. In navboxes, even and odd rows have different background. If you want to turn this off, use the parameter evenodd = off. Svick (talk) 12:33, 29 December 2009 (UTC)
Thanks. bamse (talk) 12:49, 29 December 2009 (UTC)


Is there any way to remove the bolding in this template? Say I want make a template, but I don't want the {{{title}}} to be bolded. Is there anyway to do this? (talk) 00:32, 5 January 2010 (UTC)

Add the following line to your template:
| titlestyle = font-style: normal;
EdokterTalk 01:50, 5 January 2010 (UTC)
Thanks. Wouldn't it be better that the template have no extraneous formatting like bolding by default? (talk) 03:55, 5 January 2010 (UTC)
Most people like bolding; you're in the minority. rʨanaɢ talk/contribs 17:13, 5 January 2010 (UTC)


Since the Wikipedia-Books are now mainstream (although not yet common), I think it's time to talk about how to implement books into navboxes (otherwise, we'll have a mess of non-standardized ways to include books in navboxes a year from now). Let's take for example Book:Nimitz class aircraft carriers and {{Nimitz class aircraft carrier}}

I would suggest to place the book in parenthesis next to the "topic", i.e something like

Nimitz-class aircraft carrier (Book)

By default it would link (assuming the page exists) to [[Book:{{BASEPAGENAME}}]], but could be specified manually (using a |book=) if a book is located elsewhere. If no book exist at the default location and |book= left blank, the template would behave as it does now.

I'll make a sandbox version soon. Headbomb {ταλκκοντριβς – WP Physics} 22:59, 5 January 2010 (UTC)

I don't see a reason why a separate and specific parameter would be needed. The WikiProjects can figure out the placement of the books. --Izno (talk) 23:05, 5 January 2010 (UTC)
What do you mean? Headbomb {ταλκκοντριβς – WP Physics} 23:25, 5 January 2010 (UTC)
As it is now, navbox already allows the WikiProjects to place the Portal and other such non-article pages where they wish; they usually end up in |above=, |below=, or |title=. As well, they style them to suit themselves rather than how navbox would force them to style them. I see no reason to raise books above portals and such in the manner you're asking for, and I don't know how a book significantly differs in a manner which would suggest that it have an option just for itself. I.e., you're asking for creep, imo. --Izno (talk) 00:03, 6 January 2010 (UTC)


Here's what it would look like ({{User:Headbomb/Sandbox11}})

User:Headbomb/Sandbox11 Headbomb {ταλκκοντριβς – WP Physics} 23:25, 5 January 2010 (UTC)

It kinda makes it look like the Nimitz Class Aircraft carrier *is* a book. Like if I said some noun that you didnt already know with the word "book" next to it, you would think, this is a book. Bonewah (talk) 23:39, 5 January 2010 (UTC)

Well ... we could go for the longer User:Headbomb/Sandbox12

or perhaps italicize the book link User:Headbomb/Sandbox13

or maybe seperate them by a pipe User:Headbomb/Sandbox14

The last one looks rather nice IMO. Headbomb {ταλκκοντριβς – WP Physics} 23:48, 5 January 2010 (UTC)

Try with smaller text, in second example. At the moment it detracts, rather than enhances. GraemeLeggett (talk) 13:45, 6 January 2010 (UTC)

Collapsable Navbox

How do you get the navboxes to collapse? I copied the code into Wikia, but it does not carry over the collapsing state. -- (talk) 15:52, 6 January 2010 (UTC)

wikia:niwenglisc:Template:Pyrénées-Orientales communes that is on the page you linked to collapses properly for me. Svick (talk) 19:09, 6 January 2010 (UTC)

h (history)

I was wondering whether h should be added to vde to show the history of a template. Simply south (talk) 13:13, 9 January 2010 (UTC)


Hello, I have tried to put this template on bs.wiki, but everything does not work. The hide/show button is not visible.

I've added the code "Collapsible tables" bs:mediawiki:common.js What's wrong? please answer on my talk page ;) bye --DzWiki (talk) 10:51, 20 January 2010 (UTC)

I am having some aggravating troubles with importing Template:Navbox onto my wiki. I have exported Template:Navbox from Wikipedia, and its been imported into my wiki. When I try to use the template it is a mess. I cannot understand what is going on, if you all have any insight please respond to me on my talk page. Here is a link to the navbox on my wiki. Thanks so much ~ Mowgli541 (talk) 3:40, 24 January 2010 (PST)

Adding 3 More Bluelinks


In the little corner, you can click on v, d, and e. You need to change the template so that it includes editing the discussion page, viewing the history, and viewing the discussion history. (talk) 23:34, 4 March 2010 (UTC)

I will draw your attention to the words "consensus should be obtained before the template is added" at Template:Editprotected. This means you have to propose the change on this talk page, and wait for others to agree with it, before adding the editprotected template.--Father Goose (talk) 07:18, 5 March 2010 (UTC)
I would oppose this change. All those links are one click away, and adding them makes the template more convoluted with little added benefit. Ucucha 04:00, 6 March 2010 (UTC)
Well, why include those 3 at all? There is as much benefit as adding any number of letters. (talk) 06:20, 6 March 2010 (UTC)
I agree with Ucucha. Too much clutter confuses people. The three letters we have are more than enough; all the other options are easily accessed after clicking one of those three.--Kotniski (talk) 11:26, 6 March 2010 (UTC)
It's good to have a fast way to access the template when it's transcluded onto a page without having to track it down by hitting 'edit', then figuring out which template it is, then copying the template name to the search bar and adding "template:". Only one link on the template is really needed for that: [v]iew. I can see how editors might want to sometimes jump straight into editing the template after viewing a page it is included on. Wanting to go straight to its discussion page is somewhat less likely. Least likely of all is the possibility that someone would want to edit its discussion page (or view its history) without looking at what discussion is contained there first.--Father Goose (talk) 22:18, 6 March 2010 (UTC)

Bad centering in main heading

The overall heading for the navbox isn't centered correctly if it uses more than one line. Specifically, the second line is well to the right of center. Lines three and four look okay. —Codrdan (talk) 13:15, 4 May 2010 (UTC)

This is a known problem that is caused by the navbar and show/hide spans. It's easy to fix though, by adding the syntax <br clear=all> to break lines. For example:
--CapitalR (talk) 07:22, 7 May 2010 (UTC)
Thanks. I added a doc section for it. —Codrdan (talk) 07:46, 7 May 2010 (UTC)

Show/hide color

Hi, I've set the color for the background of a navbox to be purple but someone has told me that this makes the show/hide link hard to see as it blends in with the purple too easily. I've seen in some other templates, like in HiddenMultiLine, that it's possible to make the background immediately around the show/hide link to be a different color to make it stand out. Is it possible to do this with navbox? I'd like to keep the overall background as purple if at all possible... Thanks in advance. Rudy 08:47, 15 May 2010 (UTC)

Just use the titlestyle parameter to change the text color -- WOSlinker (talk) 09:02, 15 May 2010 (UTC)
Cheers, the navbox I'm using isn't as simple as the one above so it took a bit of playing around but you pointed me in the right direction, think the problem's been solved, thanks! Rudy 11:59, 15 May 2010 (UTC)

Multiple images

Is there a way to add more than one image to a template using this design? I can think of a few cases where this could be useful. Alzarian16 (talk) 15:29, 9 June 2010 (UTC)

You can easily use multiple images like this:
 | image = [[File:Image1.png|none|50px]] [[File:Image2.png|none|50px]] ...

--fryed-peach (talk) 07:57, 10 June 2010 (UTC)

Ah, thanks. I didn't think it would be that simple! Alzarian16 (talk) 12:30, 10 June 2010 (UTC)

Java script question

Recently I have been removing junk EL per WP:EL, which happens to be where navboxes are located. I weirdly stumbled upon a few articles over the course of a few weeks that had the navbox commented out. When looking at the article history, whoever made that edit had some comment like "navbox is longer than the article" or something. Then the other day I was using a dial-up connection that was so slow it was 1999 -- so I turned off my java script to speed things up a bit. I came across a shark article, and with no javascript, the navbox was HUGE. I do not know enough about java script to ask an intelligent question about it, so bear with me. So, if java script is disabled, is there some way to disable a navbox or make an error or warning message appear saying java script must be enabled for the navbox to work properly? It might not be appropiate on smaller navboxes, but maybe a parameter can be included on larger navboxes? A bot could add it to a navbox if it is over XX kilobytes? I don't know, probably a dumb question, just thinking out loud. (talk) 16:07, 17 June 2010 (UTC)

If you created an account, you could set your user style, so that you wouldn't see navboxes at all. But generally, it is much better to see the navbox in full rather than not seeing it at all, if you don't have JavaScript enabled. For example, some users that have some disability access websites using special software, that may not have the ability to use JavaScript at all. Also, I'm not sure whether disabling JavaScript would help much on dial-up, disabling images would be probably more efficient. Svick (talk) 17:23, 17 June 2010 (UTC)
Thanks for the response, but you are missing the point. Creating an account and setting preferences won't help someone who is just reading an article, an account is not necessary for that, and it is disappointing when the first thing someone tells an IP is to get an account. Disabling JavaScript on a dialup connection can speed up loading a WP page two-fold (and other sites that rely more heavily on JavaScript four- to five-fold), while disabling images helps, it does not speed up loading a page near as much, but that also was not the point and is irrelevant to my question. Seeing a navbox in the full rather than not at all was not what was being proposed.
Rather, what was being proposed (at least for discussion) was a notice that appears when JavaScript is disable. For example: when you go to a site that has a form you want to fill out online, and you have Java Script turned off, a notice appears that says "You need JavaScript enable to complete this task" or whatever. Therefore, rather than a user coming across an article with a massively HUGE navbox at the bottom that is fully expanded with no "show/hide" button (which only appears with JavaScript enabled), instead they would see - say right under the title of the navbox - a small unobtrusive notice in the same font and font size as the rest of the navbox that says you need to have JavaScript enable to collapse the navbox (note, this also includes the qualifications given above - a parameter is created "javascript = yes/no" which would be set to yes only if the navbox is over XX kilobytes, a bot could add it to old ones, the parameter if set to yes would add the unobtrusive notice if and only if it determined JavaScript was disabled, etc.). That would immediately give notice to the reader that their WP experience would be improved with JavaScript, rather than them thinking the huge navbox is inappropriate and distracting for that page.
I imagine the developers of the navbox are well aware of what functions require JavaScript and what happens without it. This is a relatively minor question when compared to the effort it may require, but I thought it might improve someone's experience when coming across a navbox template, albeit a significantly small pool of people - a pool of people nonetheless. Thanks for hearing me out, I don't know. (talk) 12:47, 20 June 2010 (UTC)
Telling people without JavaScript that they should enable it isn't much better than showing them nothing – it still means they can't see the navbox and thus are missing an important part of navigation. JavaScript shouldn't be necessary for the full experience, if some site tells you that have to have JS enabled to use it, it usually means the site is badly designed. One solution to this problem would be to split huge navboxes, but that would require someone to do it. Svick (talk) 13:48, 20 June 2010 (UTC)
To expand on a main point here, it is almost always good practice for a website to be designed for use without Javascript, which we have done here. This is called graceful degradation: the idea that without Javascript or other advanced Internet features (CSS and HTML5 come to mind), the navigation and website in general can still be useful. Websites should not be resorting to "if you do not have Javascript enabled, the site will not work" or "please turn on Javascript to enable use of this site", because it really is bad site design (I know of some very pretty sites that I wish didn't resort to this method, because otherwise they would be considered masterpieces of web and graphical design).
If you're finding navboxes which are too large, you should consider leaving a note on the relevant template talk pages to get someone's attention, or perhaps editing them yourself. I know it is difficult to create pages (without using, say, the Article Wizard) as an IP, so there's not much more we can tell you to do to try and fix the situation aside from creating an account. --Izno (talk) 14:07, 20 June 2010 (UTC)

RfC re template naming

moved to Wikipedia talk:WikiProject Templates#RfC re template naming Svick (talk) 11:13, 26 June 2010 (UTC)

Swap "v • d • e" and "[hide]"/"[show]"

In Wikipedia you may edit a section by clicking on "edit" to the right of the title. I consequently suggest that the "v • d • e" (view, discussion, edit) links of the Navboxes should be placed to the right. Instead, the more important "[hide]"/"[show]" link should be placed to the left, making it the first thing the reader would see. Mange01 (talk) 16:06, 21 January 2010 (UTC)

See also stalled discussion earlier on the page. #Usability_and_AccessibilityTheDJ (talkcontribs) 16:47, 21 January 2010 (UTC)
Now archived at Template_talk:Navbox/Archive_12#Usability_and_Accessibility. --John Vandenberg (chat) 07:33, 1 July 2010 (UTC)

Uncollapsing all navboxes within a particular article

What can I do to make all navboxes within a particular article uncollapsed by default (the same as using "uncollapsed" as the default state, but just affecting one article)? Josh Gorand (talk) 04:52, 6 June 2010 (UTC)

I don't believe this is possible. You'll have to manually set each one to be uncollapsed. This isn't a restriction stemming from this template, it just can't be done based on the current JavaScript implementation of collapsible tables found at MediaWiki:Common.js. --CapitalR (talk) 06:40, 6 June 2010 (UTC)
But is it possible to set a particular template within a particular article to uncollapsed? Josh Gorand (talk) 17:09, 6 June 2010 (UTC)
Yes, but you may have to edit the template code itself, to include a "state" parameter, and then set the state parameter to "uncollapsed" (or whatever the word is) in the article.--Kotniski (talk) 19:07, 6 June 2010 (UTC)
Maybe working this way? I used a pass-through variable in a enveloping-enveloped set of templates. See major {{subst:Vowels}} transcluding minor {{subst:IPA vowel chart}} (they're about phonetic symbols, and the minor is not a navbox, but alas). Both templates accept the named variable shownonIPA. The trick is in the major calling: |list1 = {{IPA consonant chart|shownonIPA={{{shownonIPA}}} }}. More nuts and bolts: ultimately I use the {{yesno}} template, which produces a nice default=yes, allows choosing output-text and is very systematic & tolerant on non-existing (say non-defined, or not-used) incoming variables. Probably you'll need somehow default=no construct, which is not just a reversed yes. Maybe start using, in the minor, called template(s), like: | state = {{yesno|{{{defaultstate}}}|yes=collapsed|no=uncollapsed}}. And sandboxing is very good to crank up your edit counts, you know. Need more on this? -DePiep (talk) 08:58, 11 July 2010 (UTC)

Show/Hide Help

I know this question has been asked a million times and I've done everything I have found on here, but I still cannot get the Show/Hide to work on my Navboxes. If someone can tell me what I'm missing it would help greatly. I've been trying to fix this for over a year now, and I have no clue what I'm doing wrong! I think MediaWiki should package this and release it as an add-on! :P Anyway, here is an example of the Navbox I have: Click. Please take a look at my codes! Usakoi84 (talk) 17:09, 21 July 2010 (UTC)

Your MediaWiki:Common.js is missing the hasClass() function. You can copy it from MediaWiki:Common.js. Also, this may not be the only problem, so it may not work work even if this one is fixed. Svick (talk) 00:30, 22 July 2010 (UTC)

Change background color around the group list

How do I change the background color around the group list (the below area)? I don't want it white, I would like that background color to be yellow. I tried hex code colors with the groupstyle attribute, but it's still white. /HeyMid (contributions) 09:30, 28 July 2010 (UTC)

I think you want |belowstyle=. ---— Gadget850 (Ed) talk 12:35, 28 July 2010 (UTC)
Nope, that didn't work. I want to change the background color of the information box in the middle, not like the title or group headlines box. /HeyMid (contributions) 15:34, 28 July 2010 (UTC)
setting style & liststyle as below will do it. -- WOSlinker (talk) 16:02, 28 July 2010 (UTC)
or maybe you just want liststyle? -- WOSlinker (talk) 16:04, 28 July 2010 (UTC)


should images really be used in navbox? it seems really unnecessary and only makes navbox less easier to navigate. Plus hardly anyone uses them, should they jsut be removed?Bread Ninja (talk) 16:32, 22 March 2010 (UTC)

  1. For navboxes that just use images as ornamentation, eg {{Monarchies}}, I generally agree, personally. -- I don't think we're likely to add a "rule" against them though, in order to avoid instruction-creep. Any removals should probably be done carefully, with respect given to any page's/wikiproject's consensus to include one. (it's not worth long arguments over this.)
  2. For navboxes that use images as a link to a Portal, eg {{Time Topics}}, there is less likely to be agreement for removal.
Nonetheless I saw many articles in a particular project that had the same portal in a navbox (or several navboxen), in See also and in one or two infoboxes. INWLAOT either but I would be happy to see them go. Rich Farmbrough, 19:19, 29 August 2010 (UTC).
  1. For navboxes that use images as informative components/imagemaps, eg {{Solar System}}, they should obviously be retained. (I realize you weren't meaning these types of image, but thought I should mention them just to give a complete overview of what exists). -- Quiddity (talk) 19:13, 22 March 2010 (UTC)
To me WP:ICONDECORATION covers this sort of usage Gnevin (talk) 11:23, 10 June 2010 (UTC)

State parameter - having to add manually

I'm wondering if we could add the "state=..." parameter to the default navbox, so that it doesn't need to be added manually in each instance? e.g.

|state = {{{state|autocollapse}}}

Would that conflict with anything? I assume it could still be overridden in any given scenario...?

Thanks. -- Quiddity (talk) 01:56, 18 August 2010 (UTC)

Template inheritance doesn't work like that. You can't pass attributes to the grandparent template from the child directly; you always have to manually specify it in the parent. Changing that now would be impossible. Chris Cunningham (user:thumperward: not at work) - talk 10:41, 18 August 2010 (UTC)
Couldn't we just send it back in time to kill its grandfather?
Okay. Thanks. -- Quiddity (talk) 19:49, 18 August 2010 (UTC)

width parameter

why width:auto; is needed? thanks --ebraminiot 08:56, 24 August 2010 (UTC)

It's because the default style for a list has set width: 100% (as documented at Template:Navbox#Intricacies). I think it's done that way, so that something like the following doesn't happen. Svick (talk) 20:33, 24 August 2010 (UTC)

hmm, but i think it is better that be fixed.(i dont like put width:auto; specially when i use {{navbox subgroup}}). thanks. --ebraminiot 19:34, 26 August 2010 (UTC)

Since width could be a reasonaly common option to set for {{navbox subgroup}}, one option could be to add a |groupwidth= parameter. Thoughts? -- WOSlinker (talk) 20:28, 26 August 2010 (UTC)
Groupstyle/liststyle seem adequate to me in this regard. It's more flexible and is slightly less to deal with in the code. --Izno (talk) 21:05, 26 August 2010 (UTC)
this is a good idea, but my issue was other thing, i dont like put liststyle = width:auto; when i want groupstyle = width:10em; effecting, for example, old (merged) template {{navbox generic subgroup}} have not problem when we use that by this way groupstyle = width:10em; without liststyle = width:auto; seems groupwidth is best idea for solving that.--ebraminiot 21:14, 26 August 2010 (UTC) (edited: --ebraminiot 21:18, 26 August 2010 (UTC))
Here's a version in the sandbox with a groupwidth param. -- WOSlinker (talk) 21:40, 26 August 2010 (UTC)
hmm, seems good. but after it, may |listwidth= also needed.‌(for having balance)--ebraminiot 07:04, 27 August 2010 (UTC)
No as you wouldn't be able to use both options together. When the groupwidth parameter is used, it sets the width of the group section and removes the width:auto; from the list section. If there was a listwidth parameter, it would need to be coded so that if both parameters were set, then they would both be ignored, but since the width of the list area doesn't really need to be set (apart from removing auto), there doesn't appear to be a need for a listwidth param. -- WOSlinker (talk) 08:46, 27 August 2010 (UTC)
hmm, yes. i have not a lot experience. but i dont like users be confused. (they may think if |groupwidth= available so |listwidth= must available too!). (balance of available paramaters!). thanks again :) --ebraminiot 12:27, 27 August 2010 (UTC)
Searchtool.svg Review Can someone review my changes in the sandbox before I implement them. Thanks -- WOSlinker (talk) 12:41, 27 August 2010 (UTC)
 checked I'm not really familiar with this template but the changes look okay to me. — Martin (MSGJ · talk) 11:02, 31 August 2010 (UTC)
Perhaps I should have checked earlier. I've removed the pipes from the already evaluated parameters. I also added documentation. EdokterTalk 20:45, 31 August 2010 (UTC)

thanks all :) --ebraminiotalk 19:21, 3 September 2010 (UTC)

transition when click

i think it would look better if when you clicked show/hide it did something like what the sidebar does in vector and transitions from one to the other, is this even possible? Mark (talk) 06:42, 23 September 2010 (UTC)


Could you please post a version number (eg. date) after making changes in source code of the template? Possible format would be a HTML comment at the beginning of the source code. This can help external users (nonWikipedia users of MediaWiki software) to follow advancement of this perfect tool. pozdro Paweł —Preceding unsigned comment added by (talk) 00:24, 27 October 2010 (UTC)

Need help with a navbox template

Can anyone help clean-up the bottom of the {{Birth control methods}} template? It's pretty wonky looking. Kaldari (talk) 21:52, 1 November 2010 (UTC)

Change of color?

I think the default background colors should be changed from blue to gray like {{infobox}}, or maybe a teal color as per the page border colors of the vector skin. Thoughts? SharkD  Talk  16:31, 3 December 2010 (UTC)

That's not teal, that's aqua. But I kinda like the current color. EdokterTalk 16:41, 3 December 2010 (UTC)
This would be a large change, which should be advertised. That said, you should search the archives: A color change has been suggested before. --Izno (talk) 01:27, 4 December 2010 (UTC)
New suggestions are never wrong. How about a gradient? EdokterTalk 01:40, 4 December 2010 (UTC)
Which is not to say that that is what I said? :^) As for a gradient, I shall say that I would need to get used to it in solo-form; I don't think it would be a good idea when there are multiple boxes, as the dark fades to light more-or-less in stripes. So I'd say I'd probably oppose such a change as that for the latter reason. --Izno (talk) 01:46, 4 December 2010 (UTC)

raw html table tags to wiki table tags?

How come this template uses the raw html tags? ~kotarou3 04:01, 15 January 2011 (UTC)

Ease of coding. Some parser function do not work when embedded in wikitables. EdokterTalk 12:06, 15 January 2011 (UTC)

Questions on Navbox with MediaWiki 1.16

I am running into an issue with the display of collapsible Navboxes that contain Groups in a local install on MediaWiki 1.16. In "Hide" mode navboxes look fine, however, once "show" is selected and the navbox expands, my header is shrunk to the width of the Group column. Above and below banners still show at 100% width. I have copied over all related Common.css and updated Navbox and Navbar templates. Has anyone encountered this before and can offer advice on a fix? Thank you for the help.--Jcantroot (talk) 17:18, 17 February 2011 (UTC)

Hmm, let's see. In order for Navbox to work you'll also need the template {{Navbar}} copied over, as well as parser functions enabled. I'm guessing you already have the parser functions in place, but make sure {{Navbar}} is there. If it's still not working let us know and we can give you some more help. --CapitalR (talk) 19:41, 17 February 2011 (UTC)

I am having the same issue with a local install of MW 1.17, with Navbox, Navbar and ParserFunctions installed. I also copied Mediawiki:Common.css and Common.js from en.wikipedia. Only thing missing is HTMLtidy - could this be the reason of the strange behaviour? Thank you for help --Sal9000 (talk) 10:18, 21 February 2011 (UTC)

Yes, Navbar requires HTML Tidy. Edokter (talk) — 12:02, 21 February 2011 (UTC)
Thanks.. In fact, I've realized that the issue appears only when Navbar displays broken html. Do you know a good tutorial on how to install HTMLtidy on Ubuntu 10.04? I couldn't find much on the Web. Also, I wonder if HTMLtidy affects performance. This would be an issue, as I am running MW on a tiny Amazon EC2 instance and I am trying to optimize it in every possible way. Thank you for any help! --Sal9000 (talk) 10:23, 23 February 2011 (UTC)
I'll have to refer you to the HTML Tidy homepage at http://tidy.sourceforge.net/. Edokter (talk) — 11:50, 23 February 2011 (UTC)

FIXED! Everything is rendered correctly now. I've decided to use the php extension htmltidy - it works just fine. To install it on Ubuntu 10.04 / PHP 5.2.14:

sudo apt-get install -y php5-dev libtidy-dev
svn co http://svn.php.net/repository/php/php- src/branches/PHP_5_2/ext/tidy/
cd tidy/
sudo make install
cd ../
rm -rf tidy/

Add extension=tidy.so to php.ini; set $wgUseTidy=true in LocalSettings.php; restart apache... Enjoy! --Sal9000 (talk) 20:25, 24 February 2011 (UTC)


I think if load content async better Great Han (talk) 12:05, 23 March 2011 (UTC)

Navbox populated from Category

I'm trying to create a Navbox template that will derive its link content from a category, so that the Navbox does not need to be manually edited each time a page is added to or removed from the category. Obviously I'm not the first to have thought of this, but I have failed to find any help or instructions for achieving it. Can anyone point me to simple instructions? Or even offer advice? My failed attempt is at Template:Horse breeds of Italy; I want it to look something like Template:Spanish horses, with the links on a few lines and separated by bullets. Presumably I'm getting the data from the category in the wrong way? Justlettersandnumbers (talk) 05:57, 28 March 2011 (UTC)

I doubt that this is possible - as far as I know the "categorytree" function always returns the items as a vertical list. Maybe there's some clever trickery to be done with CSS (or even a parameter for categorytree) - you could try asking at the technical village pump, but I suspect there won't be a solution.--Kotniski (talk) 06:56, 28 March 2011 (UTC)
This could be done with css I think, using a declaration of the sort (I don't think this exactly/alone will work) table.navbox td div div.CategoryTreeTag div.CategoryTreeItem { display: inline }. That said, to see this globally, you would need consensus, and I don't think you would be able to find that.
On a side note, the html that CategoryTree renders is horrendous. The use of divs and spans as opposed to uls and lis is appalling. --Izno (talk) 17:41, 28 March 2011 (UTC)
PS: Not as appalling as the html generated by navbox though! :^)


Is there a compelling reason to allow users to add their own styling to a Navbox because Template:Phantom of the Opera and the boxes on Giovanni_Trapattoni are compelling reasing to remove these options Gnevin (talk) 00:15, 16 April 2011 (UTC)

Own styling shouldn't be allowed, but good luck getting consensus on that. Every sports project loves them colors. :| --Izno (talk) 03:37, 16 April 2011 (UTC)
Owe is it one of those issues Gnevin (talk) 18:43, 20 April 2011 (UTC)
Uh huh. :| --Izno (talk) 22:26, 20 April 2011 (UTC)
There is no compelling reason not to allow styling. It has ligitimate uses. Just because some editors abuse it, doesn't mean it should be disabled for the rest. Edokter (talk) — 22:31, 20 April 2011 (UTC)
You have any examples of these uses? Gnevin (talk) 13:50, 21 April 2011 (UTC)

Why is HTML tidy required?

I ask because HTML tidy conflicts with FCK editor, which we use. So we have to switch it off, which implies you cannot use FCK editor & navboxes together! But when I switch off HTML tidy the navboxes look OK. --Robinson weijman (talk) 13:56, 21 January 2011 (UTC)

Perhaps this was true for an older version of MediaWiki? If navboxes do indeed work with Tidy disabled, we should revise the documentation. (But I cannot test it for myself.) EdokterTalk 21:10, 21 January 2011 (UTC)
I can confirm that HTML tidy is not needed, at least, on version 1.16. The "fixed" version provided on the wikify project refuses to render right, copying the template wholesale from Template:Navbox works properly. And HTML tidy is NOT installed on my server. TheGreatTK (talk) 18:59, 21 June 2011 (UTC)

Usage of "Show/Hide" Outside Navbox Context

Sorry if I'm posting this in the wrong place, but I'd like to use the show/hide feature of the navbox in another context...I want to have a description of an item in a table that's hidden by default and can be revealed by clicking "show." Jmajeremy (talk) 01:04, 25 May 2011 (UTC)

I'd think the easy way would be to use the navbox template directly? I'm curious as to what the context is, though. → ROUX  01:06, 25 May 2011 (UTC)
Here's what I've come up with so far. Not sure if it's "kosher" wikicode, though...
{| class="wikitable sortable"
! Header text !! Header text !! Header text
| {{Navbox|none
    |title=The Cobra     
}} || Example || Example
| Example || Example || Example
| Example || Example || Example
Header text Header text Header text
Example Example
Example Example Example
Example Example Example
--Jmajeremy (talk) 03:03, 25 May 2011 (UTC)
If it works, it's kosher. I'm still trying to understand under what circumstances this would be useful though. What is the purpose of this? → ROUX  03:12, 25 May 2011 (UTC)
Basically, you can use the show/hide feature on any table by giving it the "collapsible" class. The show/hide link will appear in the first table header. Edokter (talk) — 13:31, 25 May 2011 (UTC)
{| class="wikitable collapsible"
! colspan="2" | Header
|Cell 1
|Cell 2
|Cell 3
|Cell 4
Cell 1 Cell 2
Cell 3 Cell 4

Proposal to remove the styling options

As above, I see no reason to keep these options . Wiki doesn't allow projects and users to style articles, we don't let users decide that alternation paragraphs on Manchester United are going to be red and white. Nor do we allow users to define the font type or in vast majority of cases the size. Only in templates is this allowed . WP:COLOUR outlines a number of issues with certain colour combinations, template such as Template:Phantom_of_the_Opera and Sons of Anarchy are unreadable to my eyes, while Giovanni_Trapattoni is a multi coloured mess. I can't think of a reason to keep this option other that WP:ILIKEIT Gnevin (talk) 16:00, 16 June 2011 (UTC)

I've never used these options, but I see no reason to remove them. If particular templates have issues, address them there. --SarekOfVulcan (talk) 16:22, 16 June 2011 (UTC)
  • Oppose. Just because something can be abused does not mean we should remove it alltogether. Styling is also used to adjust margins and padding in certain cases, especially since this is a meta-template. Removing it would break hundreds of navboxes that do not even use colors. Edokter (talk) — 17:10, 16 June 2011 (UTC)
  • Oppose - discreet/subtle styling is useful for linking together thematically-related navboxes, providing clues as to their contents. I agree that many are horrifying eyesores, but let's keep the baby when we drain the tub, shall we? → ROUX  17:36, 16 June 2011 (UTC)
  • Oppose No, people shouldn't be using horrid color combinations in navboxes, but we should not be removing the styling options altogether. Navboxes are used for much more than just articles, and more flexibility should be allowed for projectspace or userspace navboxes. Instead, we should be add to WP:COLOR certain instances when navbox styling is appropriate and not appropriate (e.g., things like padding fixes should be fine, and colors shouldn't be used carelessly). But for many cases, colors are useful for identification. We also have some color elements in infoboxes—perhaps we could standardize things and match them up by subject area? /ƒETCHCOMMS/ 18:11, 16 June 2011 (UTC)
  • Oppose — Fix abuses as needed but don't remove the features. Before styling was added, editors were using all sorts of horrible hacks to style elements. Perhaps add a class so someone who hates the colors can remove them in personal CSS. -— Gadget850 (Ed) talk 18:19, 16 June 2011 (UTC)
  • Oppose - Tail wagging the dog. If you are having difficulty with specific stylized templates that expand from this, then raise your concern with them. Otherwise please collect a affirmative response from every usage of this template acknowledging that they're Ok with the removal of the stylizing options. When you are attempting to take some flexibility away from users you really should get consent from everyone as people expect software to work the same unless they've been notified prior to usage about it. Hasteur (talk) 18:43, 16 June 2011 (UTC)
  • Support the core idea but oppose the methodology. I completely agree that we need to do something about the massive wp:deviations just for the sake of "I like it" and "it looks pretty". However, as has been pointed out above, there these style fields are used for more than just colouring. We should create a task force to try to remove the superfluous deviations in colouring, but, this is something which cannot be simply addressed at the level of this template. Frietjes (talk) 23:23, 16 June 2011 (UTC)
I've only ever seen the style used for colouring , can you give some examples of the other behavour it addresses Gnevin (talk) 23:46, 16 June 2011 (UTC)
  • Comment I'd challenge those above to show me a case where the use of the style para has led you to say wow this really improves the project. This isn't about indivual cases I don't like, even perfectly good templates when combined can look terrible and present access issues. This para should improve the project, it doesn't Gnevin (talk) 23:46, 16 June 2011 (UTC)
    • That's twisting the point. The style parameter doesn't have to make me say "wow". Without it, I would say "ew" if messy margins or widths ensued. Again, I think you're focusing on the wrong thing here: the problem is not the parameter's existence. It is people misusing the parameter or making poor choices with what they put in it. So you should instead be formulating a clear guideline for what is appropriate usage of the parameter. /ƒETCHCOMMS/ 19:53, 17 June 2011 (UTC)
  • Oppose - Trying to button things down past a certain point leads to stultifying conformity and blandness. Some deviation should be seen as a positive value. It provides wriggle room around the edges for some creativity and diversity; perhaps even a little colour. Wikipedia already has very bland and uninteresting default formats. Take this further and Wikipedia will start looking like something out of an apparatchik's dream (nightmare?). --Epipelagic (talk) 02:02, 17 June 2011 (UTC)
  • Oppose - While I also prefer standardized colors and styles, I must agree with Edokter that the styling parameters are often used for things other than color, such as width and padding. Removing them would break many hundreds or thousands of templates. --CapitalR (talk) 09:41, 17 June 2011 (UTC)
  • Oppose per Roux. Unusually, it appears to be snowing in June.—S Marshall T/C 11:01, 17 June 2011 (UTC)
  • Support the idea Remove the ability for gaudy color choices and implement a non-gaudy color palette throughout, removing the instances of the horrendous color combinations as demonstrated above. The problem with Fix abuses as needed but don't remove the features. is that there are so many instances of the abuse, particularly on sports pages. Perhaps create a task force to remove the superfluous deviations in coloring as suggested above. --Bob (talk) 22:41, 17 June 2011 (UTC)
  • Comment This parameter is being used for more than colouring as as such removing isn't a realistic option. However I'm still interested in working with those who agreed that this needs to be fixed Gnevin (talk) 00:23, 19 June 2011 (UTC)
  • Oppose based on everything said in opposition to this proposal, above.
    — V = IR (Talk • Contribs) 05:58, 19 June 2011 (UTC)
  • Oppose Colorization is quite useful for identification purposes. If a particular navbox's color scheme is horrible, then fix that navbox. --Cybercobra (talk) 22:40, 19 June 2011 (UTC)
  • Oppose per SarekOfVulcan. And I like the Idea of Gadget850 to add a class so someone who hates the colors can remove them in personal CSS Reo + 13:55, 20 June 2011 (UTC)
This isn't about people hating colours. Its about improving the project Gnevin (talk) 00:04, 22 June 2011 (UTC)
  • Oppose while conceding that the Giovanni Trapattoni managerial positions is jarring when opened. I guess I'm one of those sports people that loves them colors, but when I open the championships etc navbox on Diana Taurasi, the colors are a useful guide. Anyone who follows the sport will recognize the National Flag Blue associated with UConn, will recognize the team colors of the Phoenix Mercury, and the red of Spartak Moscow. It may come across as garish to someone who doesn't follow the sport, but most will make sense to people likely to look at it. As an aside, I have a personal rule to create a collapsed navbox whenever the number reaches five, partly to keep potential garishness to a reasonable level.--SPhilbrickT 20:36, 24 June 2011 (UTC)
  • Oppose if Giovanni Trapattoni is the problem, fix Giovanni Trapattoni, don't try to disable the whole machine because of a few excesses. Justlettersandnumbers (talk) 23:29, 24 June 2011 (UTC)
  • Oppose - Per SOV and Fetchcomms, also wouldn't this mess up thousands of pages with the template ? Mlpearc powwow 23:43, 24 June 2011 (UTC)

Suggested guidelines

Wikipedia_talk:Manual_of_Style_(text_formatting)#Colour I've suggested some guidelines, opinions welcome Gnevin (talk) 00:27, 22 June 2011 (UTC)

Not working despite instructions

I'm in the process of setting up a 1.16 wiki and am trying to copy some of these templates over. I've installed ParserFunctions as well as the provided common.js and common.css (which I know work due to some other templates). Also, I'm using the modified transwiki version which shouldn't require html tidy.

I cannot for the life of me get Navbox to work right. Viewed on my wiki, it appears as:


| class="navbox" cellspacing="0" style=";"


| style="padding:2px;"

| {

| cellspacing="0" class="nowraplinks " style="width:100%;background:transparent;color:inherit;;"


Any ideas what my problem is? TheGreatTK 17:37, 20 June 2011 (UTC) — Preceding unsigned comment added by TheGreatTK (talkcontribs)

Do you have an example of what your trying to achieve ? Mlpearc powwow 12:51, 25 June 2011 (UTC)

added two more examples

titlestyle - a CSS style for the title-bar, Two examples:
Used with Template:Navbox suite: |titlestyle = background:#00529b;color:white;border:2px solid #00529b;
|titlestyle = background:gray;
groupstyle - a CSS style for the group-cells, Two examples:
Used with Template:Navbox suite: |groupstyle = background:#febd10;color:#00529b;border:2px solid #febd10;
|titlestyle = background:#eee;

Errectstapler (talk) 19:11, 17 July 2011 (UTC)

{{Navbox suite}} does not use these parameters (it was vandalized), so I removed the examples. Edokter (talk) — 19:22, 17 July 2011 (UTC)

Is there any way to remove the autocollapsible feature in templates based on this one?

Asked in 2008:

== Is there any way to remove the autocollapsible feature in templates based on this one? ==

Please respond on my talk page if you know.`Savidan 17:18, 9 August 2008 (UTC) ...

|state = plain will not collapse the navbox and hide the show/hide link. EdokterTalk 22:03, 9 August 2008 (UTC)

Not sure the answer, but |state = plain does not hide the show/hide link.

Any other suggestions, thank you. Errectstapler (talk) 22:50, 17 July 2011 (UTC)

oh nevermind, |state = plain does work, i had it listed twice and the template only reads the last state line. Errectstapler (talk) 22:55, 17 July 2011 (UTC)

Transwiki Navbox


I am trying to transwiki the Navbox to my wiki. I have copied over the Common.css and the Common.js as well as the Transwiki versions of TL:Navbox and TL:Navbar. I have also installed parser functions. However, as you can see here, the collapse link won't show up. Any suggestions?-- (talk) 18:23, 12 April 2011 (UTC)

I'm having the same exact problem. I've tried it with and without HTML Tidy and I get the same result: no show/hide button. Can anyone help? Cgseif323 (talk) 19:58, 15 July 2011 (UTC)
I had to go here and make sure my code matched. If it still doesn't work, check the talk page. --Wikisian (talk) 13:32, 1 August 2011 (UTC)

Latest update

I think the latest update messed up the navboxes containing wrap codes. See this one for example: Template:Dioceses of the_Church of the East.--Rafy talk 15:10, 21 July 2011 (UTC)

I don't see anything wrong. What is the problem? Edokter (talk) — 15:22, 21 July 2011 (UTC)
I never had an issue using various Linux distros, but I lately had to use Win7 and I'm unable to view the items on the template with Firefox (Here is a screenshot). They are however visible with Chrome, Opera and IE. Can anyone else confirm this?--Rafy talk 17:32, 21 July 2011 (UTC)
Shows OK on XP with Firefox 5.0. Edokter (talk) — 19:50, 21 July 2011 (UTC)
OK on Win7 with Fx 4.0. What browser version are you using? Fx 5 or 4? --Izno (talk) 23:08, 21 July 2011 (UTC)
Latest stable (5).--Rafy talk 23:26, 21 July 2011 (UTC)

Category changes

In this CfD nomination, I've suggested changing all of the content-based navbox category names to Category:(X) navigational boxes. We've been heading that direction in the last few weeks, and I'd like to see it done automatically so that the category names aren't quite so wildly different. Please comment over at CfD if you have opinions on this.--Mike Selinker (talk) 09:52, 28 October 2011 (UTC)