Module talk:Infobox military conflict

See also: Template_talk:Infobox_military_conflict

Useful links

• Link to Template:Infobox military conflict
• Link to Template:Infobox military conflict/doc (Documentation)
• Link to Template:Infobox military conflict/testcases (Testcases)

Regarding strength of only one belligerent

If information on only one belligerent is available and not the second one or strength of second one is only partly available like strength under one of the commanders of second belligerent then how to write in Infobox? Whether remove strength column altogether for both or keep one blank or write N.A. in one? Sajaypal007 (talk) 15:53, 27 March 2022 (UTC)

I would need more information (ie a specific case with details) but we don't have to populate the strength fields in the infobox - particularly if there is any nuance to the information that is best left to prose. Cinderella157 (talk) 23:36, 27 March 2022 (UTC)

Campaignboxes causing infobox to stay above first paragraph

See Template talk:Infobox military conflict#Campaignboxes causing infobox to stay above first paragraph. At Battle of Bakhmut (for example) the mobile transform that moves the lead paragraph above the infobox is failing. Moving the campaignbox outside the infobox fixes the issue, so it doesn't seem to be the fault of either the campaignbox template or {{Military navigation}} but rather the problem lies here somewhere. Hairy Dude (talk) 01:34, 15 March 2023 (UTC)

Use of map_type= without coordinates causes script error to display instead of infobox

Resolved

Please 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

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:

• Channel Dash
• Operation Pokpung
• Battle of Mullaitivu (1996)
• Fall Rot
• October 1992 Turkish attack on Hakurk Camp
• Operation Steel
• Battle of Sarikamish
• Battle of Damascus (2012)
• Operation Alberich
• Iraq War
• Malayan Emergency

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)