Template talk:Infobox

Hello I'm admin of Polish Mc Wiki and I tried to copy/paste English templates and modules, so they will work the same but I don't know if I mmessed something up or these pages work only with eng wiki, but I would really appreciate if you could help me do this. First of all - what pages and CSSes do I need to make it work? Matik7 (talk) 09:41, 10 May 2015 (UTC)

From what I can tell, you need to update your css from MediaWiki:Common.css (just use  +  and search "Template:Infobox", and copy everything below until you reach "Template:Navbox" ), and your version of {{infobox row}} is outdated. –KnightMiner ^t/_c 23:11, 10 May 2015 (UTC)

english instead of lua wont work because it is made in lua and english insead of any coding languge like python, java script, c#, c++, binary, ect. will not work because computers cant understand it. ~2026-MuleHillsSculk6350 (talk) 14:23, 29 March 2026 (UTC)

i know how to code :) ~2026-MuleHillsSculk6350 (talk) 14:25, 29 March 2026 (UTC)

While all pages that directly use this infobox have the ability to use the inventory image feature, I believe the feature should be changed to being optional instead. Because it just came up on Discord that whenever this template is used directly without the invimage parameter specified, it will automatically infer an image filename for File:Grid {{BASEPAGENAME}}.png, which becomes a wanted page, unless invimage=none is specifically set. Although this feature is used for specific implementations like {{item}} and {{block}}, which do always require an inventory image, the image itself basically has nothing to do with this generic infobox template.

So I suggest to change this template such that it by default assumes invimage=none, and specific implementations like {{item}} and {{block}} that do need one, specifically override this to the behaviour as if they were themselves by default assuming invimage={{BASEPAGENAME}} or something similar. Personally I don't know Lua so I can't suggest changes to the module, and I don't know how this suggestion would work if at all, and there may be other suggestions that would have a similar effect to solving the undesired wanted pages from listing, but this is just my 2cents and anyone else's input is also very appreciated. – Jack McKalling [ 👁 Image
👁 Image
] 12:15, 4 February 2019 (UTC)

Just removed the check for grid since no page is using it anyway. –Majr ᐸ Talk
Contribs 04:34, 6 February 2019 (UTC)

Thanks a lot! – Jack McKalling [ 👁 Image
👁 Image
] 10:17, 6 February 2019 (UTC)

I noticed this in the CSS:

.infobox-rows>tbody>tr>th{
text-align:left;
white-space:nowrap;
}

And I think that white-space should be set to normal instead. --Simanelix ^(T|C) 15:59, 12 June 2025 (UTC)

The white-space: nowrap; is required to ensure the field names can take the space they need. Setting it to normal would result in field names breaking after every short word (like Mob <br>type) as soon as a field value exists in the infobox with more content, which is very common, especially on mob pages. -- 👁 Image
MarkusRost (talk) 16:05, 12 June 2025 (UTC)

I was thinking {{nowrap}} could be used to solve this problem for most of the field names. And that some field names could be allowed to split into 2 lines. Like Catches fire from lava being split into Catches fire and from lava. There are benefits and downsides to this solution. --Simanelix ^(T|C) 19:28, 12 June 2025 (UTC)

nowrap would need to be added to the field names on the template, but the default breakpoints depend on the length of any field value on the article. This would make it hard to ensure they are always displayed properly and we would end up with having to add nowrap to most field names anyway (which is basically what the css already does). For long field names, linebreaks should be added manually using <br> as is already done on most cases like "Knockback resistance" and "Natural equipment" on entity pages. -- 👁 Image
MarkusRost (talk) 19:39, 12 June 2025 (UTC)

Okay. That makes sense and sounds like the simplest solution to me. --Simanelix ^(T|C) 20:45, 12 June 2025 (UTC)

why dosent show the result of a infobox. also pepole dont really know what the coding language lua is ~2026-MuleHillsSculk6350 (talk) 14:16, 29 March 2026 (UTC)

The raw infobox template by itself is really just used in userpages for more customization. If you need something more specific, you could try checking other templates that transclude the raw infobox. RedX (talk) 14:31, 29 March 2026 (UTC)

So, the other day I was editing my infobox on my user page, but I entered the parameter "image2size". I wanted to change the scaling of my logo picture, but I found out it was "2-1size" (in group 2 and picture 1). Can you somehow fix the code and replace "imageNsize" with "N-nsize" with text like "Changes the size of picture n using px." please? 👁 Image
(talk | contribs) 14:04, 31 May 2026 (UTC)

imageNsize works when done with imageN. 2-1size works when done with 2-1.  Nixinova  T ⁄ C  14:25, 31 May 2026 (UTC) Actually I think image2size should work with 2-1... what exactly was the code?  Nixinova  T ⁄ C  14:31, 31 May 2026 (UTC)

The parameters imagesize, image2size, etc do not apply to images in groups. imagesize only applies to an image set by image, image2size to image2 etc. Likewise, 1-1size is used for 1-1, 2-1size for 2-1 etc. Basically, if an image is set by a parameter XYZ, its size is configured by XYZsize. There is also *-1size for setting sizes to first images in all groups (overriden by 1-1size etc), and so on. — BabylonAS 16:07, 31 May 2026 (UTC)