Template:Infobox is permanently 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. Usually, any contributor may edit the template's documentation to add usage notes or categories.
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 Infobox template.
This template is within the scope of WikiProject Infoboxes, a collaborative effort to improve the coverage of Infoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes
Text has been copied to or from this page; see the list below. The source pages now serve to provide attribution for the content in the destination pages and must not be deleted as long as the copies exist. For attribution and to access older versions of the copied text, please see the history links below.
This edit request to Module:Infobox has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
There was a previous discussion with a similar request on the 28th of April in 2014 by Sardanaphalus. I'm also making a similar request as well.
Can someone please make the following edits to this template:
1. Can this template and {{#invoke:Infobox|function}} (be set to) use basestyle "à la" {{Navbox}} family..?
2. Also like the {{Navbox}} family, can class and style as alternative names for bodyclass and bodystyle be included, as well as |width= as an alternative to |bodystyle=width:...;..?
Oppose #2. There are various class and style parameters used. There is no need to introduce easily foreseeable errors. If a template creator can't take the time to write "bodyclass" then to be honest, they really have no reason to write one. Regarding #1, I don't understand the request. Gonnym (talk) 07:11, 17 July 2024 (UTC)[reply]
I think I can get behind the first part of #2, where "class" and "style" alias "bodyclass" and "bodystyle", respectively; the usage of "body" makes me think that it refers to the content in the <tbody> rather than the entire <table>. Widths should not be set in infoboxes. Rather, the width should be based on the content (usually the image size) on each page. Plus, infoboxes on mobile (afaik) are all fixed-width.
Could you clarify what #1 is supposed to mean? I'm with Gonnym, I don't understand either. Do you mean you want to add a parameter for "basestyle" like in Navbox? SWinxy (talk) 12:59, 17 July 2024 (UTC)[reply]
Regarding |width=, that will not be supported. If you would like to modify an infobox's width, you should do so with TemplateStyles via |templatestyles= in the appropriate media query so that these templates can be responsive at small resolutions. At some point it will be removed from {{navbox}} also.
I agree with Gonnym and Primefac about the other request in #2. We do not need to support additional aliases. Izno (talk) 21:35, 17 July 2024 (UTC)[reply]
URLs in image field
It's common to find URLs in the |image= field which of course does not work eg. Hemal Ranasinghe. These are trivial to detect (I think?) and could generate an error so they can be tracked and removed. The URLs are sometimes in square links. Other fields are |image_skyline= and |logo= and probably others. -- GreenC17:48, 19 July 2024 (UTC)[reply]
This revised search returned about 700 but regex times out. I suspect it's a lot more. I stumbled on this while looking for goo.gl links and found about 200 image links with that domain alone. -- GreenC19:48, 19 July 2024 (UTC)[reply]
This edit request to Module:Infobox has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Hi there I hope you are doing well! I would like to add an additional image from The [1]PBC Coat of Arms under the main image using the actual template. Precisely, I would like to edit as I want this page without prior demand or requirements. If you could include my tag-name in the allowed list, I would greatly appreciate it.
Best regards, Sir Watson SirlupinwatsonIII (talk) 05:03, 22 July 2024 (UTC)[reply]
Maybe it's just my computer, but I see the image in question inside of a white box (though when I go directly to the file page itself, it shows a transparent background). Primefac (talk) 20:24, 25 August 2024 (UTC)[reply]
Which do you see? A black background in the infobox, or a white background in the infobox? Just noting that both options have been indicated above. Primefac (talk) 20:48, 25 August 2024 (UTC)[reply]
I see the white background in the infobox and the transparent background on the file itself, which I interpreted to be the same as you — Martin (MSGJ · talk) 20:50, 25 August 2024 (UTC)[reply]
It cannot be done from the core styles today. (That might be possible later, I haven't decided. Feedback somewhere between fine and welcome.)
You will need to provide an appropriate class to the image row to indicate it holds an icon, and then you will need to add TemplateStyles to the infobox to make the image background always the light background. In order:
Add a class to the row. In infobox company's case, there is already a logo class, but I do not know from what this stems, so I will add to ib-company-logo
Save all the pages + protection for the TemplateStyles page.
IDK about MSGJ and Primefac. The relevant dark mode here is the WMF standard dark mode, which only now post-my-edit displays the image with a light background. Izno (talk) 20:58, 25 August 2024 (UTC)[reply]
Hi there, I hope this is a good place to ask. Does preprocessArgs({ {prefix = 'image', depend = {'caption', 'imagerowclass'}} }, 10) mean that for an image26 + caption26 to show up, we have to have an imagerowclass26, or something similar?
My problem is that {{Infobox mountain/sandbox}} refuses to render that, and there's no errors shown, so I'm at a loss. The logic over there is a fair bit convoluted - we want to shift indices in case a photo is present, and the photo can also be present at Wikidata, so we call {{#invoke:WikidataIB|getValue}} for the latter. But even if I set up image26 and caption26 statically, it's not rendered. How come?
Obviously, if all this is barking up the wrong tree and there's a simpler way to get the same result, I'm all ears.
To answer the first question, no, "depend" is the other direction: to have an imagerowclass or a caption you must first have an image. Izno (talk) 16:06, 8 October 2024 (UTC)[reply]
Thanks.
Is it possible that this dynamic row creation behavior of infobox mountain depends on preprocessArgs step, which in case of dataN can be 50 or so apart, but imageN can only be 10 or so apart, or something like that? --Joy (talk) 20:00, 8 October 2024 (UTC)[reply]
OK that should be it. I think I missed the fact that imageN is not supposed to be interleaved with dataN, but necessarily above them. IOW despite this content ultimately being an image, it'll have to be implemented through data rows? --Joy (talk) 20:31, 8 October 2024 (UTC)[reply]
I was fairly certain this was a restriction but wanted to see if anyone else piped up. Yes, images go at the top of the infobox, that's always where they've gone, and where other infoboxes support an image elsewhere it's with a data cell, no label, because they were shoehorned in. Izno (talk) 20:41, 8 October 2024 (UTC)[reply]
OK, makes sense. The only reason I went for the image+caption syntax was that it seemed logical for that separation of rows, but if there's no real difference between imageN+captionN and dataN+data(N+1), it's just fine to keep using the latter for this. --Joy (talk) 21:01, 8 October 2024 (UTC)[reply]
_-_The_Noun_Project.svg){kind=small}
![[1]](https://www.canada.ca/content/canadasite/en/parole-board/corporate/pbc-coat-of-arms-and-heraldic-badge-armorial-bearings/_jcr_content/par/img_5/image.img.jpg/1546027164147.jpg){kind=link}