Template talk:Multiple image/Archive 3

Archive 1

Archive 2

Archive 3

Specifying page in a PDF

Hi, is it possible to specificy a page shown from within a PDF using this template? Dovi (talk) 09:12, 25 February 2019 (UTC)

this may work. Frietjes (talk) 16:33, 25 February 2019 (UTC)

Thanks Frietjes! Dovi (talk) 08:05, 26 February 2019 (UTC)

Can "Template:Multiple image" and "Template:Annotated image" work together?

I am struggling to figure out how to make Template:Annotated image work with Template:Multiple image. I have groups of images that work best when they are portrayed together and some need to be zoomed-in. Since I've not been able to figure out how to use these two templates together, I've been forced to crop and upload new versions of these images, which seems inefficient and wasteful to me. Does anyone know how to make the two templates work together? --McChizzle (talk) 17:14, 23 March 2019 (UTC)

Request to remove duplicate class

In Module:Multiple image I found line 216 added HTML class "tmulti-sandbox", which should be used only in sandbox page, and this class may cause conflict if this module is used in the test case page. I suggest removing this line from main module. Great Brightstar (talk) 14:07, 2 April 2019 (UTC)

 Done —TheDJ (talk • contribs) 07:22, 3 April 2019 (UTC)

Parameter syntax tweak

Is there a particular reason why |background color= in is the only multi-word parameter for this template which doesn't use an underscore? I asked Primefac about this at User talk:Primefac#Template:Multiple image, and it was suggested that it might worth getting this changed. It seems it would be best if the parameters were consistent (at least in this template) and might help avoid user errors. -- Marchjuly (talk) 01:49, 10 July 2019 (UTC)

Documentation change to reduce risk of non-standard unlinked images

I became aware of this issue when I couldn't click on an image in an article that uses this template. I first added links, before reading in the talk archives that deleting the |link= parameter altogether will use site-standard image links. This parameter works consistently with the general image syntax, so that's good. My only suggestion is to change the documentation so that people don't copy-and-paste the blank template with all the parameters, not knowing that one of those parameters suppresses default behavior.

I suggest a "default syntax" or "most commonly used parameters" section at the beginning (for example, {{Cite web}} documentation has this) that leaves out |link=. Then, where |link= is mentioned, it would be helpful to add an explanatory comment like there are on many of the other parameters. Benny White (talk) 18:44, 21 July 2019 (UTC)

Footer alignment

I noticed that the |footer_alignment= parameter doesn't work as expected, as you can see at Template:Multiple image § With background color. There, even though it is set to center, it still is aligned to the left. I believe it is because the trow class prevents the class to be properly centred. I think adding justify-content: and setting its value to either flex-start or flex-end or center depending on |footer_alignment='s value (left, right or center, respectively) to the div with the trow class solves this problem. --CaiusSPQR (talk) 03:28, 4 August 2019 (UTC)

The justify-content property is still at the W3C Candidate Recommendation stage, not yet a W3C Proposed Recommendation (the next step on the way to being adopted as a formal W3C Recommendation), so browser vendors need not support it, but if they do, it's done so as a means of testing implementation of the feature. In short: don't rely on it. --Redrose64 🌹 (talk) 07:04, 4 August 2019 (UTC)

@Redrose64: You can also say the same for display: flex, yet it is used for this template. So, why not use justify-content when flexbox is already being used? —CaiusSPQR (talk) 08:32, 4 August 2019 (UTC)

@Redrose64: Yet caption_align works on my browser (Firefox); how is that? Also, the template doc says footer_align not footer_alignment. Which is right? --Jorge Stolfi

@Redrose64: PS. I noticed that the Lua code fetches the caption_align parameter right away, but not the footer_align parameter. It appears further down, though. Is that correct? --Jorge Stolfi (talk) 23:23, 25 October 2019 (UTC)

Jorge Stolfi, the parameter is |footer_align= as there is no mention of |footer_alignment= in the code or in the documentation. Frietjes (talk) 23:49, 25 October 2019 (UTC)

CaiusSPQR, it's because the content is smaller than the cell width. Can also fix by using "box-sizing: borderbox; width:100%;" on the .thumbcaption — Preceding unsigned comment added by TheDJ (talk • contribs) 16:31, 5 August 2019 (UTC)

@TheDJ: If that works, I think it's the best solution. —CaiusSPQR (talk) 20:19, 18 August 2019 (UTC)

Location maps

I'm trying to use this template to have maps of Denmark and Greenland side by side for List of World Heritage Sites in Denmark, but it seems the simple syntax does not work for more complex components. Any suggestions? Thanks in advance! --Tone 21:17, 4 August 2019 (UTC)

Tone, this only works with standard images. I would suggest using {{stack}} instead, which _should_ automatically adjust for narrow screens. Frietjes (talk) 17:03, 5 August 2019 (UTC)

That gets the job done, thanks! :) --Tone 17:38, 5 August 2019 (UTC)

Center alignment of vertically directioned images and transparent frame

Hi guys. I was working on Vojvodina Infobox settlement template (version [1]), and the idea was to have two flags and two coat of arms there as, somehow, this settlement has both of these in official use and is advised that both be shown. When using Multiple image template, Is there any way to center the images within a frame when vertical direction is used (i.e. so that images don't go next to the left frame line - as is the case with coat of arms in this article currently)? Also, is there any way to have "frameless" frame when this template is used (i.e. not to have visible frame lines).--AirWolf ^talk 10:36, 21 October 2019 (UTC)

AirWolf the |border=infobox can be used when embedding in an infobox. this template enforces a minimum box width of 100, which is why the 74px wide shields are not centered. the simplest solution is to use {{image array}} which doesn't have the 100px min-width restriction. Frietjes (talk) 14:50, 21 October 2019 (UTC)

@Frietjes: Thank you for the info and fix on the page as well!--AirWolf ^talk 17:13, 21 October 2019 (UTC)

Modifying the background border?

I have ported this template (and the supporting module and templates) over to my own wiki, and it works fine. However I want to be able to modify the background frame and image borders. Specifically, I want to add a border-radius to both the individual images as well as the surrounding frame to have rounded corners.

I have managed to get decent work arounds for the other image templates, such as on this page, but this one, because it uses the multiple image module, is a complete mystery to me on how to modify. The template .css page, doesn't really get me there at all, and I can figure any of this one out.

How can I do this?

Any help would be greatly appreciated. — Lestatdelc (talk) 04:55, 2 December 2019 (UTC)

Lestatdelc, you could start with [2] this page and try adding your css there. if you want to try to style _all_ images on your site and not just the ones that are pushed through your [3] template, you can try adding rules for .thumb to [4]. putting templates or other content in [5] will help show you the classes being used by the various elements. for example, pushing through a standard thumb image like [[File:Ortsschild Eisingen DIN-Breitschrift.jpg|thumb|Sign]] with "raw html" returns

<div class="thumb tright"><div class="thumbinner" style="width:302px;"><a href="/wiki/File:Ortsschild_Eisingen_DIN-Breitschrift.jpg" class="image"><img alt="" src="https://upload.wikimedia.org/wikipedia/commons/thumb/c/cb/Ortsschild_Eisingen_DIN-Breitschrift.jpg/300px-Ortsschild_Eisingen_DIN-Breitschrift.jpg" width="300" height="234" class="thumbimage" srcset="https://upload.wikimedia.org/wikipedia/commons/thumb/c/cb/Ortsschild_Eisingen_DIN-Breitschrift.jpg/450px-Ortsschild_Eisingen_DIN-Breitschrift.jpg 1.5x, https://upload.wikimedia.org/wikipedia/commons/thumb/c/cb/Ortsschild_Eisingen_DIN-Breitschrift.jpg/600px-Ortsschild_Eisingen_DIN-Breitschrift.jpg 2x" /></a>  <div class="thumbcaption"><div class="magnify"><a href="/wiki/File:Ortsschild_Eisingen_DIN-Breitschrift.jpg" class="internal" title="Enlarge"></a></div>Sign</div></div></div>

which tells me that you can style the outer container with rules for .thumb and the inner container with rules for .thumbinner and the image with rules for .image etc. you would want to put these css rules in [6] similar to the format you see for other entries. Frietjes (talk) 20:40, 2 December 2019 (UTC)

Thanks Frietjes for the response. I managed to get a useable workaround going. The .thumbinner class is (counter intuitively) the outer box for image frames (why it is named "inner" I have no idea). I could directly round the border-radius of non-multiple images (i.e. those not formatted with the {{multiple image}} template) via the skin CSS class (Vector in my case) tags. But for some reason it would not work when altered in the Common CSS. I assume this is because the skin CSS overrides the common one.

That said, I could not change the individual border-radius for those formatted with the {{multiple image}} template via the vector, common or the template specific CSS sub-page definitions. Not sure if it was something within any of those which was overriding it (because of order of cascade maybe?) or some inherited style from somewhere that was mucking it up.

That said I had previously made a wrapper template called "rounded" which, when placing the entire {{multiple image}} call, would round the corners of individual images within the multiple image template call. So I have a temporary work-around. Ideally I would I would like to sort it all out simply with the master CSS page definitions and not have to use custom template wrapper(s) to do this (which I ended up doing in order to round the frames of tables on my wiki). But this will do for now.

Needless to say, I personally have found the Frankenstein of the CSS handling within MediaWiki to be a challenge at times. – Lestatdelc (talk) 00:15, 4 December 2019 (UTC)

Does not show in an article

Moved to Talk:Visual pollution § Old revision is shown for logged out users

 – issue not with template, but with the page Visual pollution itself. —⁠andrybak (talk) 16:31, 31 March 2020 (UTC)

shortcut

Could someone add the T:MI shortcut to the page.-TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 04:47, 19 April 2020 (UTC)

Well, that's confusing. Template:MI is already used for {{multiple issues}}. But T:MI redirects to this template. I didn't realize the two could be different. Surely they should both point to the same place? —David Eppstein (talk) 05:07, 19 April 2020 (UTC)

@TonyTheTiger and David Eppstein:, because T:MI is in the article namespace (T is a pseudo-namespace), it is not used for transclusions. It is used to link to the template, however, only 43 times (44 with this message). —⁠andrybak (talk) 07:51, 19 April 2020 (UTC)

These are both long-standing redirects.

T:MI (edit | talk | history | protect | delete | links | watch | logs | views) was created in January 2010 by TonyTheTiger (talk · contribs) and originally pointed to Template:Multiple image. It was sent to RfD in December that year by Cymru.lass (talk · contribs) as part of a batch nomination and subsequently kept.

Template:MI (edit | talk | history | links | watch | logs) was created in July 2011 by Rich Farmbrough (talk · contribs) and originally pointed to Template:Multiple issues. A WP:BOLD (undiscussed) repurposing by CFCF (talk · contribs) to point to Template:Multiple image took place in September 2015, but wasn't reverted until March 2018 by Frietjes (talk · contribs).

An RfD in December 2013 considering both of these redirects together was started by WOSlinker (talk · contribs) as a result of which they were kept as they were. Given that, and the fact that both are more than eight years old, it means that any change to either one will require a fresh WP:RFD. --Redrose64 🌹 (talk) 13:43, 20 April 2020 (UTC)

My point was that we seem to have a stasis with T:MI pointing to this template. I was asking if someone could put the {{shortcut}} template on the page, since editing is restricted.-TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 02:00, 24 April 2020 (UTC)

No it's not. --Redrose64 🌹 (talk) 18:30, 24 April 2020 (UTC)

T:MI was one among a small set of such redirects I was just examining; strange to see it being discussed the very same day. This type of pseudo-namespace shortcut is deprecated, it clashes with uses of "t:mi" in articles, and as far as I can see from the small sample of incoming links I've checked – TonyTheTiger, you appear to be the only editor using it. It's probably better deleted, but even if kept, this, and similar, templates should never be advertised in the documentation as shortcuts because they can't work the same way that template shortcuts do. – Uanfala (talk) 02:00, 25 April 2020 (UTC)

I've now nominated the shortcut for deletion, see Wikipedia:Redirects for discussion/Log/2020 April 25#T:MI. – Uanfala (talk) 02:43, 25 April 2020 (UTC)

Attn: Redrose64, This is what I see when I try to edit the template page:This page is currently protected so that only template editors and administrators can edit it.-TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 16:26, 25 April 2020 (UTC)

Then you're trying to edit the wrong page. {{Template shortcut}} (n.b. not {{shortcut}}) goes in the documentation, which isn't protected - and never has been. --Redrose64 🌹 (talk) 22:14, 25 April 2020 (UTC)

Absolute image sizes

MOS:IMGSIZE states that a fixed width in pixels may only be specified, "Where absolutely necessary." What is the "good reason" or the "absolute necessity" for this template to fail to respect users' default image size preferences? What does "upright=scaling factor" mean and how does one use it on this template? [Comment on the doc page by Hyacinth at 10:01, 26 January 2020 moved here. Peter coxhead (talk) 10:05, 26 January 2020 (UTC)]

Hyacinth makes a good point. Elsewhere, e.g. in taxoboxes, absolute image sizes specified by parameters like |image_width= have been replaced by relative image sizes specified by parameters like |image_upright=. It seems to me that this should apply here too, preferably with an alias that allows a more sensible parameter name rather than the historical upright used to specify the scale factor applied to the user's preferred image size. Peter coxhead (talk) 10:09, 26 January 2020 (UTC)

(P.S. This should also apply to the use of the gallery tag, but that's not under our control. Peter coxhead (talk) 10:13, 26 January 2020 (UTC))

I think in the case of this template the good reason is technical: we can only use the |upright= parameter to relatively-size an image when we are using the |thumb= parameter, and this template needs to format images without thumbs, so it has no easy way to access the Wikimedia relative-sizing machinery. I would certainly be happy with a variant of this template that allowed relative rather than absolute sizing but I don't know whether that is possible and if so how. —David Eppstein (talk) 19:17, 26 January 2020 (UTC)

correct. I would be happy to work on this if I had a way to access a user's thumb size settings. this is probably a topic for WP:VPT or another more general technical page (like MediaWiki talk:Common.css). Frietjes (talk) 19:32, 26 January 2020 (UTC)

I request that someone kindly add 'thumb' support to this template. There's no reason not to, though I also don't know why there are multiple image gallery templates. Shouldn't they all be consolidated into one, and support 'thumb'? Thank you. — Smuckola(talk) 22:17, 10 June 2020 (UTC)

Smuckola, I thought I explained why this can't be done? since you think there is "no reason not to", please make the needed changes to the sandbox. Frietjes (talk) 00:04, 11 June 2020 (UTC)

Lua bug; totalwidth x total_width

@Frietjes: @Galobtter: I get this bug when trying to use the "total_width" parameter:

Lua error in Module:Multiple_image at line 163: attempt to perform arithmetic on local 'totalwidth' (a nil value).

--Jorge Stolfi (talk) 04:43, 11 May 2020 (UTC)

Please post some simple wikitext (perhaps between <pre> and </pre> tags) that illustrates the problem. Or at least spell out exactly what total_width parameter you entered. Johnuniq (talk) 05:09, 11 May 2020 (UTC)

Jorge Stolfi, the value should be a positive integer, without any px or other units. I have seen that error when people try to write |total_width=600px instead of |total_width=600, or if there are some invisible control characters in there. Frietjes (talk) 13:30, 11 May 2020 (UTC)

@Frietjes:Ah, that must be it. However, would it be hard to accept both "600" and "600 px"? Editors now have to remember which templates want dimensions with "px" and which ones don't -- and will get mysterious errors if they get it wrong. Also, shouldn't the name of that Lua variable have an underscore too, like the template argument? --Jorge Stolfi (talk) 08:11, 12 May 2020 (UTC)

Jorge Stolfi, we could add this line which would remove anything after the first numeric part of that input. this would also make it so any completely nonsense input would result in code ignoring that parameter. to have the code issue an additional error message would require another few lines of code (check to see if the value before the input cleaning is the same as the value after the input cleaning). having the lua variables match the input variables would be useful in cases where the user may see the internal lua errors, but wouldn't be a problem if we added our own error checking. Frietjes (talk) 13:41, 12 May 2020 (UTC)

I haven't looked at the code recently but it would be easy to strip px before processing the number, something like totalwidth:match('(.*)px$') or totalwidth. Johnuniq (talk) 23:48, 12 May 2020 (UTC)

Module:Location map uses something similar, but isn't specific that it has to be px (e.g., width = tonumber(mw.ustring.match(tostring(width),"%d*")) or 0 at one point in the code). Frietjes (talk) 00:13, 13 May 2020 (UTC)

But as you said that's not a good idea because people might expect that units other than px would work, and it would silently give incomprehensible results if something other than px were used. I think modules should do reasonable checks and report bad input to avoid junk accumulating. Johnuniq (talk) 04:24, 13 May 2020 (UTC)

sure, we can basically do whatever we want at this point since I don't think there are actively any pages using anything other than sane values (otherwise they would show up in the script error category). Frietjes (talk) 14:45, 13 May 2020 (UTC)

now added. Frietjes (talk) 14:58, 13 May 2020 (UTC)

Template-protected edit request on 16 July 2020

		-- add the footer
		if( isnotempty(footer) ) then
			local falign = string.lower(pargs['footer_align'] or args['footer_align'] or 'left')
			falign = (falign == 'centre') and 'center' or falign
			div:tag('div')
				:addClass('trow')
				:css('display', (falign ~= 'left') and 'flow-root' or 'flex')
				:tag('div')
					:addClass('thumbcaption' .. (falign == 'center' and '-center' or ''))
					:css('text-align', (falign ~= 'left') and falign or nil)
					:css('background-color', pargs['footer_background'] or 'transparent')
					:wikitext(footer)
		end
		return tostring(root)

In current version, unexpected behaviour will occuied when displaying the "footer" text, if the "footer-align" != "left". So I modified the "display" parameter of the "trow" element so that it could properly display the footer when "footer-align" parameter equals to "center" or "right". Stang 09:19, 16 July 2020 (UTC)

Stang, could you please implement the suggested changes in Module:Multiple image/sandbox and add a test case to Template:Multiple image/testcases demonstrating the change in behavior? —⁠andrybak (talk) 11:08, 16 July 2020 (UTC)

andrybak, thanks for your advice! I think it works now... I modified two testcases. Stang 11:32, 16 July 2020 (UTC)

Stang, which testcase(s) did you edit? I'm not seeing any differences in any of them between the main and sandbox. Primefac (talk) 02:07, 2 August 2020 (UTC) (please do not ping on reply)

see test_1b.Stang 02:54, 2 August 2020 (UTC)

 Done Primefac (talk) 01:21, 11 August 2020 (UTC)

How to get vertical images to take up multiple rows?

The vertical image of the U.S. Capitol at top right is giving me trouble.

@Datumizer and Redrose64: I've come across the same problem you discussed back in 2010. I'm trying to convert File:Washington Montage 2016.png to use this template, but I'm not sure how to incorporate the two-row picture of the U.S. Capitol. Could we adjust this template (or add an explanation to the documentation) to make this possible? {{u|Sdkb}} ^talk 08:05, 24 July 2020 (UTC)

Sdkb, as far as I understand, even the slightly more flexible with regard to layout template {{Photo montage}} does not support pictures spanning several rows. —⁠andrybak (talk) 22:30, 26 July 2020 (UTC)

Andrybak, hmm, in that case it's a feature I hope we can add at some point. Many of the non-template collages seem to use it often (e.g. London). {{u|Sdkb}} ^talk 22:33, 26 July 2020 (UTC)

Hmm, it seems converting Minneapolis to use this template would require this, too. {{u|Sdkb}} ^talk 10:58, 27 December 2020 (UTC)

Template-protected edit request on 30 August 2020

I made the implementation to make separate text alignments for elements with thumbcaption. On mobile phones, only the texts inputed with |footer= parameter aligned to center, other pieces remain unchanged. The new code is available at Template:Multiple image/sandbox/styles.css, also available at c:Template:Multiple image. -- Great Brightstar (talk) 08:51, 30 August 2020 (UTC)

 Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. Primefac (talk) 21:58, 30 August 2020 (UTC)

Oh I thought you can go to see the testcases page first. Anyway the new source codes are already available at the sandbox page, and you can view the test cases on your phone. If you don't have a good smartphone, you can copy this link into an online tester, which has an iPhone simulator to see what happened on mobile view. --Great Brightstar (talk) 02:17, 31 August 2020 (UTC)

The sandbox page has not been edited since 16:35, 16 March 2019. --Redrose64 🌹 (talk) 19:30, 31 August 2020 (UTC)

Sorry, the new source codes were made in it's TemplateStyle and Module pages. -- Great Brightstar (talk) 01:10, 1 September 2020 (UTC)

Then the positional parameters of the {{edit template-protected}} should have been filled in with the relevant page names. Otherwise, it defaults to the page for which this is the talk page, i.e. Template:Multiple image. --Redrose64 🌹 (talk) 19:24, 1 September 2020 (UTC)

Great Brightstar, at first glance this looks good to me. Looks like you've also inadvertently fixed, what appears to be a bug, center usage using the -center class, thus stopping global .content .thumbcaption styling from being applied. Will give this a closer look later today or tomorrow and (if all is good) merge, unless someone else does in the meantime. One comment, why change to .trow, .trow *? ProcrastinatingReader (talk) 18:37, 6 September 2020 (UTC)

OK, I've viewed the source codes before my change, I found the -center class broke font color and size for footer text while I saw the testcases on mobile devices, and there is already has a parameter using text-align for center usage, so I cleaned up some codes that used for text alignments for .thumbcaption to make the captions closely resemble the native output for thumbnail views, for example, while input center for image thumbnails ([[File:Example.jpg|thumb|center|Example]]), both image and caption are centered in its thumbnail frame, but left and right doesn't affect the caption. The footer text is still centered on mobile screen until you customise that with parameter. -- Great Brightstar (talk) 02:56, 7 September 2020 (UTC)

I also thanks for your digging up, I made a further test for .trow, .trow *, I assumed that rule would make all child elements centered within .tsingle elements even if the caption is longer, just depends on the width of elements, not affect text alignments. And I thought it's reasonable to use justify-content since the template is used flexbox layout mode. But during the test I found it was useless, so I removed .trow * now. --Great Brightstar (talk) 03:33, 7 September 2020 (UTC)

Gotcha, thanks! Curious, why was text-align: center; removed from .tsingle? It causes a slight alignment change on the images themselves, just wondering what the intention was behind that. ProcrastinatingReader (talk) 16:05, 7 September 2020 (UTC)

As I said, this change will make the template closely resemble the native output for thumb type, so I dropped text-align: center for mobile view, and the content works nice as expected while seen from Test 1 on mobile view. -- Great Brightstar (talk) 04:56, 8 September 2020 (UTC)

That particular property aligns the individual image I think, not so much the captions. On mobile all images are centre-aligned (in this and in native output). Natively that's handled by margin on thumbinner, but since we've multiple images here I'm thinking that align is a way to keep the alignment. Test 1 has a slight alignment issue when the property is removed - it's small but it's an imbalance of about 3mm on my screen to the left. I think aside from that this is probably fine, noting that captions are left-aligned natively even despite the forced centre alignment on mobile. So I think other than the points mentioned this change is fine, but I'll leave this for another TE to give it a once over. ProcrastinatingReader (talk) 15:49, 9 September 2020 (UTC)

note that @Thumperward: may wish to review this. ProcrastinatingReader (talk) 15:51, 9 September 2020 (UTC)

Is this ready to go live now? — Martin (MSGJ · talk) 12:33, 11 September 2020 (UTC)

See my comments above. text-align should be readded into the css, otherwise LGTM. I'd personally like to give a little while for Thumperward to take a look at this, if they want to, but another TE/admin is fine to merge it anyway. ProcrastinatingReader (talk) 13:38, 11 September 2020 (UTC)

Yes, text-align is already added into TemplateStyles, the relevant classes can be called by caption_align parameter if this parameter is used in the content, they should also be injected when header_align or footer_align parameter is used, but I was always failed to implement in the module page, anyone else get the solution would be better. -- Great Brightstar (talk) 15:46, 11 September 2020 (UTC)

 Done With some slight code changes. Regarding default footer alignment, it seems apparent forced centre alignment was originally intended (line 285), but it's not apparent why that would be desirable & no objections raised for two weeks, thus I think it's safe to make the change. Thanks for your contribution :) & TEs: feel free to revert if any problems. ProcrastinatingReader (talk) 19:42, 14 September 2020 (UTC)

Border parameter

Re this edit, @McChizzle: the border parameter has existed for presumably a long time and is used on tons of pages, e.g. Washington, D.C. I was trying to begin documenting it; why did you revert? {{u|Sdkb}} ^talk 02:52, 27 December 2020 (UTC)

As I explained in my edit summary, I tried it as you explained how to use the parameter and it did not work. All it did was force everything to center-justify. --McChizzle (talk) 03:13, 27 December 2020 (UTC)

McChizzle, are you objecting the existence of the parameter, then? If so, you need to explain how else we can get this to work with infoboxes. If not, it is standard practice to document all parameters and you should not be reverting it, especially if you are confused by it. The documentation I wrote was not at all complete, but it'd be better than nothing. {{u|Sdkb}} ^talk 10:57, 27 December 2020 (UTC)

I am not objecting to the perimeter. What I am objecting to is telling editors what to do without explanation or they will be just like me thinking it is broken or is bad code. If you are going to add new instructions on how to do something, editors need to be told what it does. After doing some additional experiments on this parameter, I think I figured out what it is supposed to do, so I reverted my edit and added a label explaining what I think it does. So please correct the label if it is wrong. --McChizzle (talk) 13:52, 27 December 2020 (UTC)

We should take the time and have a talk about this types of image spam in the city artcles.....as we have done with countries and ethnic groups. Horible to see all the city artcles being such a scrolling nightmare for mobile users.--Moxy 🍁 15:10, 28 December 2020 (UTC)

Infobox caption spacing

When this template is used in an infobox with a typical image_caption, there is extra spacing between the image set and the infobox caption (see left example). A related issue can be seen when using this template's footer parameter for the caption instead; an extra space shows up below the footer (see right example).

Maybe when the border parameter is set to infobox, a special case for spacing can be used. I primarily would like to see a fix for the case on the left, which seems like the more common/proper use of infobox captioning with this template. — Goszei (talk) 06:42, 11 February 2021 (UTC)

Wellington Capital city Clockwise from top: Waterfront along Wellington Harbour, Parliament Buildings, National Library, Cuba Street and its Bucket Fountain, Wellington Cable Car Country New Zealand

Wellington Capital city Clockwise from top: Waterfront along Wellington Harbour, Parliament Buildings, National Library, Cuba Street and its Bucket Fountain, Wellington Cable Car Country New Zealand

Discussion at Wikipedia talk:Manual of Style § Collage footer style

 You are invited to join the discussion at Wikipedia talk:Manual of Style § Collage footer style. {{u|Sdkb}} ^talk 23:40, 14 July 2021 (UTC)

Template-protected edit request on 14 August 2021

This template currently doesn't accept "centre" in the caption_align parameter – only the American spelling. I don't know what the cause of this is, as I've looked at the module page and can't see a problem myself. Is someone able to figure this out and fix it? Thanks, DesertPipeline (talk) 02:37, 14 August 2021 (UTC)

I don't see where, or if, the problem exists in the code, but I have created a test case using "centre" as the spelling. – Jonesey95 (talk) 13:45, 14 August 2021 (UTC)

If it's used as a value in a CSS declaration, only the center spelling is valid. --Redrose64 🌹 (talk) 20:50, 14 August 2021 (UTC)

It's was, originally, used as a value in a CSS declaration, however the code was then converted to use TemplateStyles in Special:Diff/889236723. This means that this could, in theory, be fixed by adding

.text-align-centre {
    text-align: center
}

to Template:Multiple image/styles.css. However, I see no reason why this template should have its own opinion about what values of |text-align= are valid instead of deferring to the CSS standard, and thus think this request should not be implemented. * Pppery * _{it has begun...} 21:13, 14 August 2021 (UTC)

User:Pppery: It's inconsistent with the "align" parameter though. That accepts centre as a value; "caption_align" doesn't. DesertPipeline (talk) 06:42, 16 August 2021 (UTC)

 Not done for now: please establish a consensus for this alteration before using the {{edit template-protected}} template. Elli (talk | contribs) 16:29, 16 August 2021 (UTC)

Background color?

We can set the background color of the template, but how do we remove the background colors of the images? E.g. if I set the background color to black, each image sits in a white square, even though the img itself has a transparent background. I'd like the imgs to display against the background color I choose. — kwami (talk) 03:27, 7 January 2022 (UTC)

Kwamikagami, not sure if you've solved this but setting the parameter image_style=background-color:black; should work. --Paul_012 (talk) 10:48, 7 March 2022 (UTC)

@Paul 012: Thanks! That helps. But even removing the border on the individual images, there's still the larger border in white. For example:

I'm not finding anything at Extended image syntax about this. — kwami (talk) 20:32, 7 March 2022 (UTC)

Disabling border leaves wide horizontal gap but not vertical

With default border

With border disabled

See the examples to the right. Setting image_style=border:none; results in the horizontal gap increasing by the width of the border, while vertically the image is shifted up two pixels leaving a narrower gap. Is there a way to address this discrepancy? --Paul_012 (talk) 12:29, 6 March 2022 (UTC)

Documentation bug in 'clockwise' captions

I'm referring to the 2x2 grid that appears as the example under 'Multiple rows'. When the page is rendered the four images image1, image2, image3, image4 are laid out as follows:

image1	image2
image3	image4

The example footer says 'Clockwise from upper left' and lists four captions. This implies the captions are given in the order image1, image2, image4, image3. However, the captions are written in the order image1, image2, image3, image4. In other words the captions are written in clockwise order, but the images are laid out like text in column-then-row order. The captions do not match the images.

I discovered this documentation bug because I found an example 'in the wild' of this problem: specifically, the info box on Genocide of Serbs in the Independent State of Croatia. I imagine it is widespread.

Thought number 1: the example in the template documentation needs to be fixed. Reordering the captions to the correct order would be a start. But beyond this I suggest the four example images are changed to something clearer like the yellow/red card example earlier in the page: I suspect the problem has gone undetected for so long because it is hard for a passing user who is not a surveying equipment enthusiast to detect the discrepancy between the captions and the images. Further I think there should be a clear note in the documentation that the column-then-row layout gives a different order from the clockwise caption order typically used in footers. Side note: the actual 2x2 image grid which the example was copied from on Surveying#Equipment has had its caption order corrected!

Thought number 2: there must be a lot of image grids out there on wiki pages which have this same error due to copy-and-paste.

Thought number 3: it's difficult for wiki editors to transform between the column-then-row order of the images and the 'clockwise from top' caption order. Could this template use the alt text to automatically generate the 'clockwise from top' style footer text in the correct order?

I don't have the privileges to edit the template page. Can someone with greater powers help?

Citruswinter (talk) 18:55, 13 April 2022 (UTC)

I think you ought to ask at the "Technical village pump" Kadwalan (talk) 19:11, 10 July 2022 (UTC)

Removing framing

Is it possible to remove the frame when this template is being used? The reason I'm asking is because someone used this template to create a three-image montage in the main infobox of Ethiopian Revolution and the infobox itself is sort of acting as a frame, which makes the one added by this template seem odd and redundant. -- Marchjuly (talk) 13:12, 19 September 2022 (UTC)

Marchjuly, fixed: Special:Diff/1111187312. I've updated the description of parameter "border" in TemplateData. Hopefully it's more clear now. —⁠andrybak (talk) 19:13, 19 September 2022 (UTC)

Thank you andrybak. -- Marchjuly (talk) 20:54, 19 September 2022 (UTC)

Alignment

Hi, I used this template on the UEFI article. How do I center an image within the frame? Thanks. The weird thing is that images are centered by default in the mobile interface. Is it a bug that this doesn't happen on the desktop interface? I would also prefer to have the caption spread out over the full length. PhotographyEdits (talk) 15:40, 11 December 2022 (UTC)

Text alignment issue for mobile view

In Amsterdam article I found the image captions always aligned to left on mobile phone, even if | caption_align = center is used. As my investigation, you should remove the following lines from styles.css page:

	.tsingle .thumbcaption {
		text-align: left;
	}

-- Great Brightstar (talk) 07:16, 17 April 2023 (UTC)

To editor Great Brightstar: that was specifically added in Sept. 2020 with [this edit] by editor ProcrastinatingReader. The es reads "(add default footer alignment)", so we should try to assess the need for that before we remove it. P.I. Ellsworth , ed. ^{put'er there} 21:34, 19 April 2023 (UTC)

This seems to be in response to Template_talk:Multiple_image/Archive_3#Template-protected_edit_request_on_30_August_2020, but that was 2.5 years ago (jeez, doesn't time fly!)

I can't remember the context entirely. Looking at the testcases using a responsive mode, the live and sandbox seems to be the same, but it's a bit deceiving because the CSS from the main one is being applied I think. If I disable that line of CSS in inspect element, captions all seem to be centre-aligned, which is a bit problematic and I think differed from normal behaviour. But disabling the CSS in inspect element may not necessarily give the same view as if the change was made to the live version. Probably the most accurate way to test is a separate page that only calls the sandbox version (without those 3 lines in styles.css), and seeing what happens. Ideally captions should not all be centre-aligned by default, which is what I think happens if those lines are removed, but I may well be wrong and I haven't spent long re-testing this now. ProcrastinatingReader (talk) 12:48, 5 May 2023 (UTC)

Cropping images

Is it possible to include cropped images in this template? I can crop an image using Template:CSS image crop, but I don't see an option to crop multiple images here. Jarble (talk) 19:36, 13 May 2023 (UTC)

Transparancy

This template replaces a transparent background with white. This is not desired, because the default background is gray so it shows a border that does not really exists. Can this be disabled so it shows the same color? I can hack around it by changing the entire background to white, but I would prefer not having to do this. PhotographyEdits (talk) 13:26, 12 December 2022 (UTC)

I see this was from a while ago, but if you're still struggling with this - try setting "image_style=background-color:yourcolorhere; border:none;". This is taken from the "with background color" section, specifically the part with the astrology symbols. (Or, even if you have figured this out, I suppose this might be helpful for anyone else looking). AnteaterStim (talk) 19:40, 8 August 2023 (UTC)

Issues with Vector 2022

Hi, this template works perfectly fine in the normal Vector version, but in Vector 2022, the center-aligned option creates large blank spaces in articles when there is an infobox to the right of the template. See Incheon Station and Napier MRT station, for example. Is this a fixable issue? Pinging @Frietjes and @Thumperward as I've seen you've edited this template in the past. :3 F4U (they/it) 23:32, 13 July 2023 (UTC)

I don't think there is anything special about Vector2022, centered multiple images, or infoboxes here except that these tend to make narrow margins, wide floating content, and wide non-floating content. This is just a MOS:SANDWICH issue: to avoid badness caused by wide floats (the infobox) and wide content elements (the centered image) being unable to fit side-by-side in narrow margins, don't write the article in a way that causes them to be side-by-side. —David Eppstein (talk) 00:57, 14 July 2023 (UTC)

Hmmm I think I get what you're saying, lemme do a thing. :3 F4U (they/it) 00:58, 14 July 2023 (UTC)

One way to check this is to make your browser window very narrow. When I do this in monobook on Incheon Station I get the same effect that I would with the narrower margins of Vector2022 on a wider window. —David Eppstein (talk) 01:00, 14 July 2023 (UTC)

I find that using <gallery>...</gallery> or {{gallery}} with |mode=packed is a better option in these cases. Frietjes (talk) 15:13, 14 July 2023 (UTC)

@Frietjes I'll try that out thank you~ :3 F4U (they/it) 17:01, 14 July 2023 (UTC)

Is there an option to add footers between rows of images?

I want to add footers in this template between each row of images instead of just one footer at the bottom; is this currently possible?

I don't see parameters like footer1 or footer2 in the documentation, so I wonder if there's another way to do this. Jarble (talk) 20:43, 17 July 2023 (UTC)

I can do this using an image frame, but the captions are too small:

Players are cautioned with a yellow card and sent off with a red card.

Players are cautioned with a yellow card and sent off with a red card.

But the captions display normally when I use this template outside the frame:

Players are cautioned with a yellow card and sent off with a red card.

Is it possible to put this template in an infobox or frame without changing the size of the captions? Jarble (talk) 16:05, 23 September 2023 (UTC)

Testing wrapping

I pulled this from another page to test whether it wraps. I couldn't tell there because it was under a wide table. Apparently, it does not wrap here. Why doesn't it wrap as the screen narrows? A better option may be Help:Table#Side by side tables and the following section. I have used it often. It wraps.

Life expectancy in world, according to estimation of the World Bank Group, 2019–2021

--Timeshifter (talk) 06:18, 23 September 2023 (UTC)

because it is designed to always put the images next to eachother. Its not a gallery, it's a composite. —TheDJ (talk • contribs) 12:24, 23 September 2023 (UTC)

In Windows 10 with Firefox and Monobook, resizing the window to about 736px or narrower causes the three images to be arranged vertically. Wider than that, they're all in the same horizontal row. --Redrose64 🌹 (talk) 16:40, 23 September 2023 (UTC)

alt & link

Parameters alt & link don't seem to runs well:

• In first doc example (red & gold cards), with alt and without link: alt doesn't show, but link to commons image description
• In mule & donkey example, the mule has alt and link: both of them runs well, it is, image links to mule and alt shows "mule" too. The donkey has alt and link without value: alt wrongly doesn't show and image correctly not link.

In summary: alt parameter only act when link is present and not empty.

Does somebody fix it?. Thanks Amadalvarez (talk) 15:31, 10 October 2023 (UTC)

Direction and image_gap

If direction is vertical, then image_gap should be applied to margin-bottom, not margin-right. Probably needs new if test and css adjustment just above line 265. Mathglot (talk) 09:38, 8 December 2023 (UTC)

Is it possible to align the footer to the left?

@Frietjes: I tried to align an image footer to the left inside a frame, but it appears to be aligned to the center:

Life expectancy in world, according to estimation of the World Bank Group, 2019–2021

Is it possible to align this footer to the left side of the frame? Jarble (talk) 19:38, 4 January 2024 (UTC)

Jarble, it should work now, although, I prefer moving the caption to the {{image frame}} in that case. Frietjes (talk) 20:37, 4 January 2024 (UTC)

Wrong font size inside infobox

The template has a border correction for using it inside infoboxes, but it doens't adjust the font size appropriately. Namely, it reduces the font size (for the captions) that has been already reduced by the surrounding infobox, which results in vioulation of MOS:SMALLTEXT. For example, see Baltimore, where the current default skin produces 94% (.thumbcaption) × 94% (div.thumbinner) × 88% (.infobox) = 78% font size (10.886px), well below the acceptable 85% lower limit (11.9px). As far as can I see from the documentation, there's currently no option to correct this manually, but in principle it would be nice to implement this correction automatically (either by using something like |infobox=yes to correct both the border and the font size, or by using the font size relative to the document instead of the parent). — Mikhail Ryazanov (talk) 21:52, 5 December 2023 (UTC)

An ugly hack would be to wrap the call in the article in <div style="font-size:110%">...</div>. But this search shows 2800 calls with border = infobox: hastemplate:"Multiple image" insource:"border = infobox". That's impractical for a wrapper in every article. I suggest the module automatically adjusts the size for border = infobox. There might be an optional override to not adjust the size. PrimeHunter (talk) 01:45, 11 December 2023 (UTC)

@Frietjes: Could Module:Multiple image be modified in order to correct this? Jarble (talk) 17:05, 22 December 2023 (UTC)

Jarble and PrimeHunter, okay, now added to the module here. Frietjes (talk) 16:03, 2 January 2024 (UTC)

@Frietjes, PrimeHunter, and Mikhail Ryazanov: But now the font size is too large for when the template is used in collage mode (ex: New York City). Chronus (talk) 02:37, 5 January 2024 (UTC)

Now (in the default skin) it's only slightly larger than the infobox font (12.7389px instead of 12.32px). I don't know where did PrimeHunter got these "110%", but it apparently doesn't match anything even in the default skin. If Frietjes wants to work on this, I would suggest, instead of trying to counter-adjust the font, simply to remove addClass('thumbcaption') (here) and thumbinner (here), the latter of which also adds unnecessary padding; then all the captions should use the regular infobox font. Hopefully, these classes are not needed for anything besides messing up the appearance. — Mikhail Ryazanov (talk) 03:25, 5 January 2024 (UTC)

Mikhail Ryazanov, okay, I removed those classes but only when |border=infobox. is that better? Frietjes (talk) 17:02, 8 January 2024 (UTC)

Frietjes, thanks, it's definitely better. Yes, "only when |border=infobox" is exactly what's needed. But for some reason the captions are still wrapped in <div class="thumbcaption text-align-center"> instead of <div class="text-align-center">, even though this shouldn't add the thumbcaption class for 'infobox'. Any ideas? — Mikhail Ryazanov (talk) 22:26, 8 January 2024 (UTC)

Mikhail Ryazanov, that was an oversight, I wasn't passing border to the function. is that better? Frietjes (talk) 22:48, 8 January 2024 (UTC)

Indeed. :–) Yes, now the captions use the same font as everything else in the infobox. Thanks a lot! — Mikhail Ryazanov (talk) 22:56, 8 January 2024 (UTC)

Additional shortcode

Border of template can also be removed using the following shortcode:

|border = none

Add to description, — Andrew Pertsev (talk) 12:35, 7 January 2024 (UTC)

New feature

As translatable SVG files come around, it would be great if this module can support different languages of a SVG file. Tipically you can call a file with a language switch with [[File:image.svg|thumb|lang=es]] (the svg file is in english but with spanish data stored and can be called using this "lang=" code). The module don't support any code more from "image.svg" so I can't call the desired language version. I don't know how to start to get this. Thanks Manlleus (talk) 01:12, 18 January 2024 (UTC)

Cropping images

@Frietjes: I wish we had an option to include cropped images in groups of multiple images. Could this feature be implemented using {{CSS image crop}}? Jarble (talk) 17:54, 23 January 2024 (UTC)

probably possible, but a lot more code. will see if anyone else has an opinions. Frietjes (talk) 21:48, 23 January 2024 (UTC)