Template talk:Navboxes/Archive 1

Archive 1

Usage

To group together Navigation boxes

• title=Title of this box
• list1=The templates to be grouped such as

{{Navboxes
|title= Giovanni Trapattoni Navigation boxes
|list1={{Italy Squad 1962 World Cup}}
{{Italy national football team managers}}
{{Republic of Ireland national football team managers}}
{{A.C. Milan managers}}
{{F.C. Internazionale Milano managers}}
{{Juventus F.C. managers}}
{{Bayern Munich managers}}
{{Cagliari Calcio managers}}
{{ACF Fiorentina managers}}
{{Italy Squad 2002 World Cup}}
{{S.L. Benfica managers}}
{{VfB Stuttgart managers}}
{{FC Red Bull Salzburg Squad}}
}}

which gives

Succession boxes

If succssion boxes are first a <span> is need to have the template display correctly see sample below

Add documentation

{{editprotected}} See User:Gnevin/sandboxGnevin (talk) 23:36, 2 July 2008 (UTC)

Done. --- RockMFR 23:56, 2 July 2008 (UTC)

Force collapsed

{{editprotected}} ,Can you add state=collapsed see User:Gnevin/sandbox1 for code. Currently if succession boxes as added with no templates the boxes doesn't collapse Gnevin (talk) 22:44, 5 August 2008 (UTC)

 Done Thanks, PeterSymonds (talk) 00:53, 6 August 2008 (UTC)

Transfert du modèle vers wiki français

Je souhaiterais recuperer ce modèle pour le transferer et l'utiliser sur le wikipedia français ? Est-ce possible ou pouvez vous le faire tout simplement ?David.0390 (talk) 18:22, 5 September 2008 (UTC) I would wish to recover this model to transfer it and use it on the French wikipedia? Is this possible or can you do it quite simply?David.0390 (talk) 18:22, 5 September 2008 (UTC)

Should be doable ,does just copy and paste the code and change the English to French. This template uses {{Navbox}} so you'll need to point to that or create that also.Sorry but my french is terrible so this is the best i can do for you Gnevin (talk) 10:50, 9 September 2008 (UTC)

Adding list

{{editprotected}} Can you add |list = <span>{{{list|}}}</span> to allow a possible merge with {{Template group}} and also their is no need for the 1. I'll update links to this template using AWB Gnevin (talk) 00:55, 29 October 2008 (UTC)

Change {{{list1}}} too {{{list1|}}}Gnevin (talk) 00:56, 29 October 2008 (UTC)

I confess I don't understand this. You want to add a list parameter to the {{Navbox}} call in this template? But Navbox doesn't use a list parameter. What am I missing? —Wknight94 (talk) 02:16, 2 November 2008 (UTC)

Nevermind ,further testing has shown this change doesn't work as i hoped Gnevin (talk) 13:16, 2 November 2008 (UTC)

The code should be:

|list1 = <span>{{{list1|{{{list|}}}}}}</span>

to prepare for the redirect. Note this is a change to the existing code, not an addition like the original request. ~ Paul^T+/_C 23:46, 6 January 2009 (UTC)

 Done Ruslik (talk) 14:32, 7 January 2009 (UTC)

{{editprotected}} Thanks. Also, I just saw that there is also a {{{state}}} parameter on {{template group}}. Can the following change be made for the same reasons as above?

|list1 = {{{list1|{{{list|}}}}}}
|state = {{{state|collapsed}}}

I don't see any need for the <span> tag either so I have removed it. Sorry for not including this in the first place. Thanks for the prompt change!  ~ Paul^T+/_C 16:01, 8 January 2009 (UTC)

 Done Ruslik (talk) 17:59, 8 January 2009 (UTC)

Hiding navboxes

I don't see how this template is useful. Sure it makes the page tidier, but at the huge expense of making all the navboxes pointless if they can't be seen. The very point of navboxes is to link related articles in a way that can be easy for casual readers, most of the time a click on a navbox link is spontaneous because the link was visible to the user. Making someone open an all-encompassing navbox, then a list of navbox groups, then open the navbox itself, then finally being able to see what related links are available to them, is defeating the object and makes the very navboxes this template is hiding redundant. We should be looking at the individual templates that are useful and merging or deleting others, instead of removing any sense of usefulness from one of Wikipedia's best features just so the page height is a few pixels smaller. --Joowwww (talk) 18:41, 8 January 2009 (UTC)

The trouble with Merging,deleting or removing template is one most pages the template is useful and can't be remove . Having too click open will hardly that much effort. Most examples of this usage dont include a sublist of navboxes but just navboxes and the navbox the user is looking for. Gnevin (talk) 19:00, 8 January 2009 (UTC)

If I may, I'd like to add that combining Navbars into a Template group and placing it at the bottom of an article, presumably where readers will wind up when finished reading the article, might be less daunting or overwhelming for readers. They don't see an overwhelming list of new links and articles to read until they have clicked on the "SHOW" link. Not all readers are fast readers, so this template is not the "speed bump" that some editors think it is. Some readers read the English Wikipedia in English as a second or third language rather than their primary language, and those readers might not read as fast as someone who has learned English as a primary language.

 —  ^{.`</sup>^) Paine Ellsworth<sup>diss`cuss} (^^`.  10:48, 12 October 2009 (UTC)

The "Coord" template

{{Editprotected}} Just before the Succession boxes subsection, it states:

Important: Don't include {{coord}} in the group. This would prevent the coordinates from being displayed.

This isn't entirely true, as can be seen below...

(This one just shows degrees and minutes. Of course, seconds can also be shown if known.)

As long as the "display=" is set to "inline", the coordinates appear in all skins including monobook.

Perhaps it is time to change that note to read that...

The {{coord}} template can now be included in the group. Just remember to set the "display=" parameter equal to "inline" thusly: {{coord|18|30|N|64|30|W|display=inline}}. The {{coord}} template can even be nested in a Navbox titled  Geographic locale, which is already found on many country pages.

(or something like that)...

• PS. Also note that the info in the template can be bolded just like regular text can be.

• PPS. This is certainly a learning process for me. Experimenting shows that if the "display=" value is changed from "title" to "inline" then the coordinates appear in all skins, even in the "monobook" skin. If set equal to "title", then the coordinates will only appear in the "simple" and "myskin" skins, but will not appear in all the other skins, including the "monobook" skin. Of course when you use "inline", you lose the "Coordinates" link just before the globe, which links to "Geographic coordinate system", however that can easily be added back in manually. One has to consider, though, that somebody is probably working on a fix for the Coord template, and how manual inputs may not be needed at some point in the future; then all those manual entries would be redundant and have to be removed. Perhaps its better to wait for the fix than to edit in all those manual entries?

Snag

I like this template and find it quite useful, but I've run into a snag on the article Testosterone, where the shell only includes the first of the four navboxes. I've looked at the navboxes involved and don't see any obvious non-conformities, and I think my implementation of the shell is correct. Could someone more knowledgable than I take a look and see what they can see? Thanks. Beyond My Ken (talk) 21:28, 7 April 2010 (UTC)

Some recent problems

In the past week or so, I have been noticing a problem with the template. Once I add the {{Template group}} and close it after the navigation boxes and save the nav boxes in side of the template will not show. Is there something new to do? Thanks. Nascar1996 23:00, 27 November 2010 (UTC)

I think I may have figured it out. I wish you did not make the redirect change because everysinge article that had it is now not working properly. Uhhhh. Nascar1996 23:03, 27 November 2010 (UTC)

I did figure it out nevermind (it also wasn't the above). I was putting 1= instead of list= :) 23:05, 27 November 2010 (UTC)

Threshold for number of navboxes

I've recently started seeing this template being used with as few as two or three navboxes on a page, which is really too small for it to have any benefit to outweigh the cost of hiding the individual navboxes. I would like to suggest that the documentation recommend that this template not be used if there are less than five (or so) navboxes on the page. The exact number is of course open to discussion, but I think five is an appropriate number. Antony–22 (^talk⁄_contribs) 03:54, 1 February 2011 (UTC)

Whether to use this template should be in the realm of normal editorial decisions, depending on the state of the article, but if we're going to set a minimum reccommended number, 3 would seem better to me than 5. Beyond My Ken (talk) 04:51, 1 February 2011 (UTC)

Problems with change of Mediawiki version?

Has anyone noticed any change in the operation of this template since the changeover? When I added it to the Headache article, it only seems to enclose the first navbox, at least with FireFix and the MonoBook skin. Beyond My Ken (talk) 04:47, 27 February 2011 (UTC)

It's the same under IE as well. Beyond My Ken (talk) 04:49, 27 February 2011 (UTC)

Font-size

Hi. The current font-size setting for the templates grouped by this template is too small, i.e. it makes the links listed within the templates more difficult to read and the dots between them almost invisible. Please, therefore, replace the line

|liststyle = padding:0px;font-size:111%;

with

|liststyle = padding:0px;font-size:115%;

i.e. increase the font-size specified from 111% to 115%.
213.246.117.201 (talk) 14:36, 3 September 2011 (UTC)

I can expand it to 113%; this would counter the original navbox font-size of 88% better. 115% makes the font too big (bigger then the original navbox font size). — Edokter (talk) — 15:44, 3 September 2011 (UTC)

Looks fine now -- thanks. 213.246.116.224 (talk) 12:13, 7 September 2011 (UTC)

Display problem

For some reason this template is displaying the text "Template: Navboxes" instead of the template itself at, for example, Isreael#External links and New York City#External links. Fixing the problem is beyond my capability. Anyone here who can do the repair? Butwhatdoiknow (talk) 11:44, 24 June 2012 (UTC)

fix for state = off

currently, the value for "navbar" is set to "plain", which is perfect in all cases except for when "state=off", in which case it should be set to "off". I added an ifeq in the sandbox to fix this. a demonstration for you:

Live version

Sandbox version

so my request is to replace the current code with this version of the sandbox. thank you. Frietjes (talk) 15:47, 11 July 2012 (UTC)

Looks good, so Done --Redrose64 (talk) 17:19, 11 July 2012 (UTC)

Why not simply pass {{{navbar|plain}}} and let the editor have some freedom in the matter? — Edokter (talk) — 09:03, 21 August 2012 (UTC)

Problem

I can't seem to get the shell to work on MDMA. It looks fine in section preview, but doesn't showup properly when I save. You can see my results here and in my next two edits. I tried purging the page, but no joy. Any ideas? Beyond My Ken (talk) 08:14, 21 August 2012 (UTC)

There's nothing basically wrong with your code (although the first instance shouldn't have had the unbalanced closing </span>); the problem is that wrapping the navboxes in the shell takes the page over the expansion limit. The usual indication of this is that instead of being expanded, there is a link to the template instead. In these cases, this is present as the link to Template:Navbox. A check of the page source code shows that the link is there: <a href="/wiki/Template:Navbox" title="Template:Navbox">Template:Navbox</a>. This is immediately followed by an error message:

<!-- WARNING: template omitted, post-expand include size too large -->

To "shell" the navboxes, you really need to reduce their complexity. But is it really necessary to have all of them? It's normal practice to show only those navboxes which have a direct link to the article concerned; the article name then shows in black boldface. Looking through them however, only a few have MDMA. The others should perhaps be removed as not directly relevant. --Redrose64 (talk) 16:52, 21 August 2012 (UTC)

Thanks, I as unaware of this limit, and your advice re: removing some of the navboxes is a good one.Beyond My Ken (talk) 17:25, 21 August 2012 (UTC)

Suggestion (default titlebar background)

Hi. As I understand it, this navbox can expand to show other (collapsed) navboxes within it. Currently, that means that this template's titlebar background is usually the same as those of any Navbox or other Navboxes titlebars around it. This can make it difficult to discern this template's titlebar from the others, i.e. show that the others are grouped below it. So, how about changing this template's default titlebar background to e.g. something lighter, e.g....

...rather than...

...? CsDix (talk) 16:52, 2 December 2012 (UTC)

...No thoughts either way, so:

Here's the amended code. The change is the background:#e8e8ff; in the titlestyle parameter (a colo/ur between the #ddf;s and #eef;s I've seen used by Navbox / Navbox|child) and it can be overridden using {{{titlestyle}}}:

{{Navbox
|navbar = {{#ifeq:{{{state|}}}|off |off |plain}}
|title = {{{title|Links to related articles}}}
|list1 = {{{list1|{{{list|}}}}}}
|state = {{{state|collapsed}}}
|titlestyle = background:#e8e8ff;{{{titlestyle|}}}
|liststyle = padding:0px;font-size:113%;
|listpadding = 0px;
|tracking = no
}}<noinclude>

{{documentation}}
</noinclude>

CsDix (talk) 12:30, 14 December 2012 (UTC)

Done; thanks. Nyttend (talk) 14:06, 18 December 2012 (UTC)

Thank you! CsDix (talk) 06:05, 20 December 2012 (UTC)

state = autocollapse

{{Navboxes
|title = TITLE
|state = autocollapse
|list1 = {{Navbox
         |navbar = plain
         |title  = ASDF
         |list1  = asdf
         }}
}}

The resulting box will collapse after the page is loaded. Even though state is set to autocollapse, the presence of the Navbox in list1 will cause the collapse of both boxes. Given the fact that the intended use for this template is to contain other boxes inside it, there will be virtually no situation where the box will autocollapse, so setting the state to this value is pointless. Perhaps the template's documentation should be updated to reflect this?

This behaviour is caused by the createCollapseButtons function in MediaWiki:Common.js (the second for loop). — {{carismagic|6 February 2014, 09:15}} —Preceding undated comment added 09:15, 6 February 2014 (UTC)

complexity

FYI, if you check this version and scroll down to the very bottom, you will notice that managerial career boxes are not appearing. this is due to the added complexity of passing the navboxes through {{navboxes}}. however, I was able to fix it by switching to {{collapse top}}/{{collapse bottom}}. it seems that we can dramatically reduce the complexity by rewriting this template to simply append something like {{collapse top}}/{{collapse bottom}} to the top and bottom of the list of navboxes. 198.102.153.1 (talk) 16:21, 27 May 2014 (UTC)

It fails because the Post‐expand include size has hit the maximum. This is not a proper fix, just a band-aid. — Edokter (talk) — 19:56, 27 May 2014 (UTC)

what is the proper fix? Frietjes (talk) 23:32, 27 May 2014 (UTC)

Clean up the page, or lua-fy this template. — Edokter (talk) — 09:07, 28 May 2014 (UTC)

Limit of templates?

There is a limit of templates in the | list1 = parameter? Because I'm editing Dorival Júnior, and when it reaches 15 templates, it stops showing all of them. With 14, it's working just fine. MYS77 ^✉ 17:14, 24 November 2015 (UTC)

Strangely, the |list1= parameter in the navboxes template on Vanderlei Luxemburgo includes 16 navboxes with no issue. — Jkudlick ^tc_s 13:35, 26 November 2015 (UTC)

This is the same problem mentioned in the section above. Horrible navbox bloat on all these Brazilian football managers. Set up list articles for the managers of all the teams that have played in Série A, and one navbox "Lists of managers of Série A teams", whose entries would be these lists. Then get rid of all all the Brazilian football managers navboxes. The system can't cope with all these navboxes, which are a bad idea anyway. See Category:Pages where template include size is exceeded. By the way Vanderlei Luxemburgo does have a problem: scroll to the bottom and you'll see that it can't display Template:Navboxes colour for the same reason. NSH002 (talk) 14:16, 26 November 2015 (UTC)

@NSH002: I don't think Navboxes is a bad idea, it compresses the whole bunch of manager templates quite well, in my opinion. But after checking the section above, I copied Parreira's collapsible box and adjusted it to Dorival's article, thanks! The problem is that Brazilian clubs tend to change their managers more quickly than almost every other country in the world... MYS77 ^✉ 02:17, 27 November 2015 (UTC)

MYS77 - the bad idea isn't {{Navboxes}}, it's the idea of having all these Brazilian football manager navboxes in the first place; they should probably all be nominated for deletion. The problem with {{Navboxes}} is that it effectively doubles the transclusion size of all the navboxes within it (which is why it hits the limit), but that can be fixed by re-writing it in Lua. In the meantime, Vanderlei Luxemburgo (and probably others) need to be fixed in the same way as you have done for Dorival (ping Jkudlick). Regards, NSH002 (talk) 06:58, 27 November 2015 (UTC)