Template talk:Multiple issues

AI-generated tags

Please do not add the AI-generated template into this. The reason=y parameter, which people find extremely important to be visible, is not preserved when you do. Gnomingstuff (talk) 14:03, 8 May 2026 (UTC)

I think it should be added. If an AI generated article has so many tags that the article needs a {{Mi}} template to collapse them, that would result in two long tags. Editors can just see the reason in the source code and, besides, I've never actually seen anyone use the |reason= parameter on that template, it's not commonly provided. FaviFake (talk) 18:06, 20 June 2026 (UTC)

It didn't used to be, but now it's used pretty much all the time. Tbh I came here to see whether there was anything we could do to make the reason show in this template. Pinging @Chaotic Enby who might know a trick? Kowal2701 (talk, contribs) 14:10, 5 August 2026 (UTC)

There is a way, yes. See the discussion at WT:AFDTODO § Multiple {{Merge from}} templates from different AfDs FaviFake (talk) 14:18, 5 August 2026 (UTC)

There was some parallel discussion at Wikipedia:Village pump (policy)/Archive 212#c-Gnomingstuff-20260508141900-Maltazarian-20260508093100 that included some ideas on how to avoid the reason being hidden or on how to allow people who care to unhide it. Anomie⚔ 14:19, 5 August 2026 (UTC)

The point is that people specifically told me to add it or else they will just remove the tag no questions asked, and so I have been adding it, but if it's just going to be hidden then I might as well have not (which gives said people carte blanche to just remove the tag no questions asked) Gnomingstuff (talk) 18:58, 11 September 2026 (UTC)

Change the color of Multiple issues to match the color of the most severe issue template listed

{{Multiple issues}} currently uses a standard orange tag. This is even the case if all the issues are yellow tags or if there is a red tag.

I'm not sure how technically feasible this is, but considering that tag colors are somewhat important (for instance a red tag signals immediate attention and is for stuff like copyright or undisclosed payments, while yellow tags are less important than orange tags and are even somewhat ignored at places like WP:ITN), I would like to suggest automatically setting the tag color of {{Multiple issues}} to the most severely-colored tag. So if its all yellow tags, set it to yellow, if there's at least one orange tag, set it to orange, and if there's at least one red tag, set it to red.

I would like to see some feedback for this idea. — Knightoftheswords 05:08, 27 July 2026 (UTC)

I have no idea about the technical feasibility, but I strongly support implementing this if it is possible. Thryduulf (talk) 09:09, 27 July 2026 (UTC)

Although templates like {{Orphan}}, {{POV}} and {{One source}} can look "outside" to see if they are wrapped inside a {{Multiple issues}} and so vary the message that is displayed, they are essentially black boxes - wrapper templates like {{Multiple issues}} can't look inside their contents to see what they are displaying. --Redrose64 🌹 (talk) 18:23, 27 July 2026 (UTC)

Should be possible. These templates emit classes that go with their color, which a wrapping template will have access to if one uses Lua. Izno (talk) 15:56, 28 July 2026 (UTC)

Same with Thryduulf, I strongly support this. EatingCarBatteries _{(contribs | talk)} 07:43, 28 July 2026 (UTC)

Strongly support. Made a demo implementation at my sandbox here and the Lua for it here. Note: It won't properly display when called due to being in my userspace. I did try moving it temporarily to the module sandbox and it seemed to work properly though. FlammablePizza (talk) 17:39, 28 July 2026 (UTC)

I've moved it to module space at Module:Sandbox/FlammablePizza which is the standard location so people can see it work. :) Izno (talk) 22:00, 28 July 2026 (UTC)

Thanks, wasn't quite sure of the best place to keep it. The template now works properly when called. FlammablePizza (talk) 23:48, 28 July 2026 (UTC)

Sounds reasonable to me. —Myceteae‍🍄‍🟫 (talk) 21:29, 28 July 2026 (UTC)

I've implemented this at Template:Multiple issues/sandbox using a drastically simplified version of @FlammablePizza's script. --Ahecht (TALK
PAGE) 18:47, 30 July 2026 (UTC)

Yeah, your version there is a lot more efficient. I did make a small tweak to it by making the script start from the most severe template class and returning immediately when it finds one instead of running through every template class, updating a variable each time, and returning at the end. Doesn't really matter though, given how minimal it is. FlammablePizza (talk) 19:30, 30 July 2026 (UTC)

 Done. I went ahead and implemented it in the live template based on @FlammablePizza's most recent version. --Ahecht (TALK
PAGE) 13:53, 31 July 2026 (UTC)

First of all, I'd like to thank Ahecht and the other participants for unknowingly resolving one one of the many pending tasks at WP:AFDTODO (the one called "Improve display of {{multiple}} {{merge from}} templates"). Us PAM editors (specifically Oklopfer and I) were trying to do a similar thing at WT:AFDTODO § Multiple {{Merge from}} templates from different AfDs, but we never figured it out. Today, I was so delighted to discover that the merge templates inside {{mi}} (example) looked amazing, almost as we had imagined!

I have a couple of questions since we're on the topic:

• I was wondering if there's an easy way to change the "rename" icon in {{mi}} to a "merge" icon when the |type= is "move". It is very common to see several merge templates on an article at the same time, but this never happens for requested moves, so a simple change to the default icon should do the trick.
• Also, unfortunately, the {{mi}} box can be become a little unwieldy when there are multiple {{merging from}} templates, such as in this example. Is there an easy way to trim part of the text without radically rewriting the {{being merged from}} template? (note that we cannot rewrite the template based on {{Ambox}} because it's also used outside mainspace.) I know this isn't really related to this specific proposal, but I figured you may have another solution we didn't consider!

[Example removed, see the diff links above instead]

Thanks!

FaviFake (talk) 10:54, 12 September 2026 (UTC)

Your example doesn't work here, because it's only {{Ambox}} that works with this template and {{Merging from}} uses {{Mbox}} which produces a {{Tmbox}} on talk pages. Is there an easy way to trim part of the text without radically rewriting the {{being merged from}} template? Put the parts you don't want visible in an element with class hide-when-compact. Anomie⚔ 18:46, 12 September 2026 (UTC)

Omg I love you, this is perfect! I was able to make the message 5 times shorter just by wrapping parts of it inside <span class="hide-when-compact"> and the result is still intelligible! Is there something similar that can only show text when it's in compact form (i.e., hide the text when not compact)?

Someone needs to add this to the doc of {{mi}}, I can't believe the fix was so easy! FaviFake (talk) 19:38, 12 September 2026 (UTC)

There's no "show-when-compact". If you really wanted to try making something like that, it would probably be better placed in a Template:Being merged/styles.css rather than Template:Multiple issues/styles.css, as it would need to be active on every page with {{Being merged}} (to hide the text by default) versus hide-when-compact that only needs styling with {{Multiple issues}} (because "show" is already the default behavior). Anomie⚔ 21:40, 12 September 2026 (UTC)

Thanks! I think the current implementation is fine then!

Since you didn't reply to it and you know everything, I'm assuming there isn't an easy way to change the default icon used by {{mi}} if the |type= of the most severe notice inside it is "move"? FaviFake (talk) 13:15, 13 September 2026 (UTC)