Module talk:Infobox military conflict
Today, we want to delve into the fascinating world of Module talk:Infobox military conflict. Whether you are a history buff, a technology enthusiast, or simply someone curious to discover new perspectives, we are sure that this article will captivate you from the beginning. Immerse yourself with us on a journey that will span from the origins of Module talk:Infobox military conflict to its impact on modern society, exploring its cultural, scientific and emotional implications. Join us as we explore the different aspects of Module talk:Infobox military conflict, unraveling its importance and relevance in today's world.
| This is the talk page for discussing improvements to the Infobox military conflict module. |
|
Archives: 1, 2, 3, 4, 5Auto-archiving period: 3 months  |
 | This module does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||
| ||||||||||||||||||||
 | Module:Infobox military conflict is permanently protected from editing as it is a heavily used or highly visible module. 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.
|
| Related pages |
|---|
Use of map_type= without coordinates causes script error to display instead of infobox
ResolvedPlease see this test case for an example of the infobox being replaced entirely by a script error when |map_type= is used without coordinates. That condition should result in an error-tracking category, not a giant red error message. – Jonesey95 (talk) 01:02, 9 May 2024 (UTC)
- Never mind, I fixed it by adjusting the if statement to check for both map_type and coordinates before rendering a map. Why is this talk page separate from the Template's talk page? That is not the usual practice. – Jonesey95 (talk) 04:02, 9 May 2024 (UTC)
native_name
 | This edit request has been answered. Set the |answered= parameter to no to reactivate your request. |
Description of suggested change: Add native_name. Although I personally don't see how including a conflict's native name adds value to an infobox, many editors seem to disagree. As a result, the conflict parameter is often misused so as to include this. This new parameter is intended to prevent that.
Example: Template:Infobox military conflict/testcases#native_name
Code: Add from line 159:
if self.args.native_name then
builder:tag('tr')
:tag('td')
:attr('colspan', self.combatants)
:cssText(infoboxStyle.header_raw)
:wikitext(self.args.native_name)
end
Jay D. Easy (t) 16:26, 7 October 2024 (UTC)
Not done for now: please establish a consensus for this alteration before using the {{Edit template-protected}}template. @Jay D. Easy: Once consensus is established (or a reasonable amount of time has passed without objection), feel free to re-activate this edit request by changing it to|answered=no. --Ahecht (TALK
PAGE) 17:01, 7 October 2024 (UTC)- I judged this to be sufficiently uncontroversial as not to require consensus. But alright, RfC noticed WP:MILHIST. Jay D. Easy (t) 17:20, 7 October 2024 (UTC)
- Could you provide an example of previous disagreement or misuse of existing parameters? SamuelRiv (talk) 17:36, 7 October 2024 (UTC)
- Sure, here's a random few:
- Jay D. Easy (t) 18:03, 7 October 2024 (UTC)
|native_name=is typically accompanied by|native_name_lang=. See {{Infobox settlement}}, {{Infobox musical composition}}, and {{Infobox sheep breed}} for sample implementations. More examples are here. – Jonesey95 (talk) 05:03, 8 October 2024 (UTC)- I would have proposed adding
|native_name_lang=were it not for the fact that this infobox is Lua-based and the suggested change is the current extent of my code scavenging ability. Jay D. Easy (t) 15:19, 11 October 2024 (UTC)
- I would have proposed adding
- Sure, here's a random few:
- Could you provide an example of previous disagreement or misuse of existing parameters? SamuelRiv (talk) 17:36, 7 October 2024 (UTC)
- I judged this to be sufficiently uncontroversial as not to require consensus. But alright, RfC noticed WP:MILHIST. Jay D. Easy (t) 17:20, 7 October 2024 (UTC)
check for unknown parameters missing
We should add Module:Check for unknown parameters here. --Joy (talk) 21:54, 22 October 2025 (UTC)
- @Joy: funny story... I just did that in the template. Still working out the bugs. Obviously feel free to migrate it to the module instead. I'm less familiar with implementing it via LUA then I am will doing it in the template code.... Zackmann (Talk to me/What I been doing) 20:03, 26 October 2025 (UTC)
mapframe implementation
So my initial tests of mapframe here were based on not touching anything at all if map_type is set, but not through mapframe onByDefault. Then I ran into a couple of articles where both mapframe and location map were added by editors, but mapframe=yes gets ignored. So I utilized onByDefault to get that to work, and it did, but everything else broke horribly. That change is now reverted.
I also have an issue of not knowing how to set variable defaults in this context - I want to move mapframe-zoom from the default 10 to 7 (cf. sandbox), but it's just not budging. --Joy (talk) 22:03, 22 October 2025 (UTC)
Embed/child
So I just came across Battle of Lyman's Wagon Train which tries to embed this infobox... Neither |child= nor |embed= seem to work. Is this something that can be added? Zackmann (Talk to me/What I been doing) 02:52, 28 October 2025 (UTC)
- I will note that per the Param Report this is the ONLY instance of
|embed=or|child=in over 23,000 transclusions... So if it cannot be easily done, maybe it isn't worth fixing. Zackmann (Talk to me/What I been doing) 03:17, 28 October 2025 (UTC)