![]() | Template:Military navigationispermanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.
|
This is the talk page for discussing improvements to the Military navigation template. |
|
![]() | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||
|
Due to a bug fix with Common.js, these will now always be shown, no matter how many appear on a page. If you wish to fork this template to a version always hidden, add to the NavContent style="display:none;...." ←BenB4 13:29, 8 August 2007 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
I'm requesting that the "navbox generic" template call be replaced by the "navbox" template. The navbox is the new standard style. There should be no significant visible changes to instances of this template, only changes in how the underlying code is structured (and standardization). All that needs to be done is to delete the word "generic" in the first line of code. Thanks, --CapitalR 18:41, 1 September 2007 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
template:US Revolutionary units has been updated so that it actually follows the guidelines given for navbox layout (as opposed to pretending to be a campaign box). But because this article is fully-protected, the version transcluded here is out of date. The page needs to be refrehsed to pick up the template updates. Chris Cunningham 14:47, 24 October 2007 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
Hi. Please help this template resemble and work alongside {{Navbox}} more closely by:
Thanks. Sardanaphalus (talk) 10:26, 2 April 2008 (UTC)[reply]
I've noticed with a few different templates that is you utilize the |image= code, it has a tendancy to add a white bar at the bottom of the nabox when collapsed. Any idea what causes this? It looks funny when stacked with normal navboxes. See Template:US Navy navbox for example. bahamut0013♠♣ 11:40, 5 April 2008 (UTC)[reply]
What does this template provide over the {{navbox}} family of templates? The only visual difference seems to be a variation in colors in the overall heading row. See John_Branch#Sources for a comparision and see {{USSecNavy}} for a diff between the two. If it is just the autocategorization into the wikiproject, wouldn't it make more sense to use the {{navbox}} and just add cats to that? My curious 2c. — MrDolomite • Talk 09:43, 31 July 2008 (UTC)[reply]
class="military-navigation"
or whatever, but that's really just syntactical bickering. Chris Cunningham (not at work) - talk 13:17, 31 July 2008 (UTC)[reply]Why only 15 groups allowed? JonCatalán(Talk) 05:51, 16 December 2008 (UTC)[reply]
Does this template support the "imageleft" field available in Template:Navbox? In my attempt at converting Template:Sydney-Kormoran to use Template:Military navigation, "imageleft" seemed not to work. — Bellhalla (talk) 04:53, 20 August 2009 (UTC)[reply]
I'm trying to break out and alphabetize the Cold War Figures infobox, can someone bump up the group count to 50? - Burpelson AFB ✈ 18:18, 30 August 2011 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
please make this update to allow for the use of border parameter in navbox. This will allow this template to be nested, in the same way that navbox can be nested using the {{navbox|border=child}}
construct. once this is done, it would be great if we could do the same for template:campaign. I am trying to clean up the nesting in Template:Campaignbox Iraq War. thank you. Frietjes (talk) 19:59, 2 February 2012 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
I would like to get some changes for better flexibility:
|title=
so it defaults to nothing (so I do not have to override it to empty in things like {{WWIIJapaneseShips}})|evenodd=
|border=
to take on the value of "subgroup" as well as "child" (so|border=subgroup
works)|listpadding=
and |liststyle=
(so I can use {{Military navigation}} directly do not have to use {{navboxes}}or{{navbox}} with {{WPMILHIST Infobox style}} to emulate it in things like {{WWIIBritishAFVs}} and {{WWIISovietAFVs}})
Note: |style=
still has to be passed to subgroups for things like |style=wide
. I am not sure if there is a better method for this.
Thank you. 50.53.15.51 (talk) 20:05, 27 February 2012 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
please change
|title={{{title}}}
to
|title={{{title|}}}
or (if there is a reason why we need to make |title=
mandatory most of the time)
|title={{#ifeq:{{{border|}}}|child|{{{title|}}}|{{{title}}}}}
which will allow me to remove the blank |title=
from the child box in Template:Shenandoah class destroyer tender. thank you. Frietjes (talk) 16:20, 16 October 2013 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
Please add the capability for additional groups/lists (going from 20 to 30 should be enough). This is to accomodate some ship classes that have more than 20 adiitional operators.
Example code:
...
|group18=
|list18=
|group19=
|list19=
|group20=
|list20=
|group21=
|list21=
|group22=
|list22=
|group23=
|list23=
|group24=
|list24=
|group25=
|list25=
|group26=
|list26=
|group27=
|list27=
|group28=
|list28=
|group29=
|list29=
|group30=
|list30=
...
|list18style=
|list19style=
|list20style=
|list21style=
|list22style=
|list23style=
|list24style=
|list25style=
|list26style=
|list27style=
|list28style=
|list29style=
|list30style=
...
Thank you.
Derekbridges (talk) 05:18, 21 October 2013 (UTC)[reply]
I happened to come across the use of this template parameter at {{Military of Croatia}}. In that case, it was completely misplaced, because there was no obvious reason to do so. Fixing it was also very unintuitive, because "raw_name == no navbar" is not something any editor should be expected to remember. What is the actual purpose of this weirdly named parameter, and can we make it not so horrible? --Joy [shallot] (talk) 13:44, 14 August 2021 (UTC)[reply]
I am currently working on moving Things to TemplateStyles (see MediaWiki_talk:Common.css/to_do) and right now I'm working on the hlist class. I'm planning to always emit it when the use here is as a campaign box (per the note at MediaWiki_talk:Common.css/to_do#Hlist_modules).
However, it would be easier for me, and I think ultimately more consistent with its uses and with the rest of the wiki, for campaign boxes to be {{sidebar}}s instead of navboxes. This would also change the change to be made here to use sidebar for generating the 'non-wide' version instead of always emitting the TemplateStyles.
Soliciting opinions on this before I get started on changing this over. The colors particularly I am sure will be a discussion point. Izno (talk) 23:40, 10 March 2022 (UTC)[reply]
![]() | This edit request has been answered. Set the |answered= or|ans= parameter to no to reactivate your request. |
I would like to propose that this template be deleted. It seems to add no value over and above the standard navbox template other than a different colour scheme of blue and grey, which has at best an extremely tenuous link to the concept of a military. Elshad (talk) 12:56, 18 February 2023 (UTC)[reply]