Template talk:Infobox/Archive 8

Archive 5

Archive 6

Archive 7

Archive 8

Archive 9

Archive 10

→

Archive 15

Direct passing of parameters

I noticed that the ability to pass parameters directly to the module is for testing purposes. Will this ability be permanently retained? I think it will be needed when individual infobox templates, such as {{Infobox road}}, are converted to Lua. -happy5214 08:49, 3 July 2013 (UTC)

Yes, it will stay this way. Saying "for testing purposes" was probably a bad choice of words - really it should be something like "for accessing from the debug console or from other Lua modules". — Mr. Stradivarius ^{♪ talk ♪} 08:42, 10 July 2013 (UTC)

Below parameter newlines

data1

some below text

data1

some below text

it looks like {{infobox}} is adding <p>...</p> around anything pass to the below parameter. my guess is that there is an extra newline in there. I know this is a bit tricky, since we want bullet lists to work, but the same problem doesn't happen for the data fields. Frietjes (talk) 23:42, 9 July 2013 (UTC) — Preceding text originally posted on User talk:Mr. Stradivarius (diff)

probably could just remove the second newline in the below? Frietjes (talk) 23:44, 9 July 2013 (UTC) — Preceding text originally posted on User talk:Mr. Stradivarius (diff)

Yep, the module inserts two newlines to mimic the behaviour of the old template. That's the part of Module:Infobox that goes:

                .newline()
                .wikitext(args.below)
                .newline()

Compare this to the part of Template:Infobox/old that goes:

-->{{#if:{{{below|}}}|<tr><td colspan="2" class="{{{belowclass|}}}" style="text-align:center; {{{belowstyle|}}}">
{{{below}}}
</td></tr>}}<!--

As far as I'm aware, we wouldn't break anything by removing the second newline - it's just in there because that's what the old template did. I'll try removing it in the sandbox and seeing if anything interesting happens at Template:Infobox/testcases. — Mr. Stradivarius ^{♪ talk ♪} 08:24, 10 July 2013 (UTC)

I've tried it, and it shortens the infobox in most cases. Nothing appears to be broken, though. If people could test the sandbox with more infoboxes, that would be very useful. Also, bear in mind that at present the sandbox also contains the changes I mentioned in the #Please help with Eurozone section above. — Mr. Stradivarius ^{♪ talk ♪} 08:36, 10 July 2013 (UTC)

I don't see any problems with removing the second newline either, and it would eliminate the problem. using a div for the caption also seems sensible. Frietjes (talk) 14:45, 10 July 2013 (UTC)

I've gone ahead and updated the module. Let me see if you spot any issues. — Mr. Stradivarius ^{♪ talk ♪} 14:35, 11 July 2013 (UTC)

even/odd headerstyles

it occurred to me that the striping used by template:infobox MLB player would be much easier if we had even/odd headerstyles (see, for example, the testcases). does anyone else think this would be a good idea? I was able to hack it using child boxes, but it would have been less convoluted if we had the ability to define more than one headerstyle. Frietjes (talk) 17:23, 13 July 2013 (UTC)

I've added a new version to the sandbox. You can now specify styles for individual headers with the |headerstyle1=, |headerstyle2=, etc. parameters. It is also possible to specify styles for odd or even headings using the |oddheaderstyle= and |evenheaderstyle= parameters. (This is calculated from the total number of headers in the infobox, not from the number of the header itself.) The |headerstyle1=, |headerstyle2=, etc. parameters take precedence over all the other header style parameters, and the |oddheaderstyle= and |evenheaderstyle= parameters take precedence over the existing |headerstyle= parameter. Have a play around with it and see if it does what you need. If everything looks ok, I can update the main module for you. Best — Mr. Stradivarius ^{♪ talk ♪} 07:59, 14 July 2013 (UTC)

I've also added some test cases at Template:Infobox/testcases#Individual header styles. — Mr. Stradivarius ^{♪ talk ♪} 08:13, 14 July 2013 (UTC)

I seem to recall there was a reason for not allowing that much specificity for the styling, which is why I was being cautious by only suggesting even/odd. but if there are no objections, I suppose I see no problem with it either. it's probably less of an issue here as it is with {{navbox}} where editors come up with all kinds of crazy rainbow schemes. Frietjes (talk) 14:59, 14 July 2013 (UTC)

If there was even/odd row styles (not just headers) then Template:Infobox video game could be converted to an infobox. Although the even/odd would have to work when some rows didn't have any data. -- WOSlinker (talk) 20:36, 14 July 2013 (UTC)

Should the order of the even/odd row styles be independent of the headers, or should the first row after every header start with the odd row style? — Mr. Stradivarius ^{♪ talk ♪} 01:38, 15 July 2013 (UTC)

Infobox video game doesn't use headers but if it did, they would need to be included in even/odd if it was named as a global even/odd parameter. If data1, header3 & data5 were the only rows to display something then data1 would be odd, header3 would be even & data5 would be odd. The even/odd doesn't depend on the numbers. -- WOSlinker (talk) 06:37, 15 July 2013 (UTC)

I got the part of the even/odd being independent of the numbers - that's how the headers work in the sandbox (see this test case). I'm not quite sure of how the rows should interact with the headers though. I can think of three possibilities:

Possibility 1 - even/odd row numbering reset after headers

• Header 1 - blue
• Data 2 - white
• Data 3 - grey
• Data 4 - white
• Header 5 - blue
• Data 6 - white
• Data 7 - grey
• etc.

Possibility 2 - even/odd row numbering independent of headers

• Header 1 - blue
• Data 2 - white
• Data 3 - grey
• Data 4 - white
• Header 5 - blue
• Data 6 - grey
• Data 7 - white
• etc.

Possibility 3 - even/odd numbering includes headers

• Header 1 - grey
• Data 2 - white
• Data 3 - grey
• Data 4 - white
• Header 5 - grey
• Data 6 - white
• Data 7 - grey
• Header 8 - white
• etc.

I'm not sure which of these we need to choose, or whether we should create some code that means any of these options can be chosen. — Mr. Stradivarius ^{♪ talk ♪} 08:34, 15 July 2013 (UTC)

If you go for the 3rd option and apply the odd/even style before any headerstyle then I think that would be fine. -- WOSlinker (talk) 08:40, 15 July 2013 (UTC)

@Frietjes: I'd have no problem with taking the individual header styles out if there has already been a consensus found for it. I thought it was just an oversight that they were left out, but if there was a good reason to do so then I certainly wouldn't be against it. Do you have a link to the discussion, by any chance? — Mr. Stradivarius ^{♪ talk ♪} 01:38, 15 July 2013 (UTC)

And also, if someone really wants to create a crazy rainbow scheme, it's not all that hard to do even with the present template. :) — Mr. Stradivarius ^{♪ talk ♪} 08:34, 15 July 2013 (UTC)

yes, it is possible, although to extend this to multiple labelstyles and multiple datastyles and multiple headerstyles requires a bit more effort. I will see if I can find a specific thread about this (so far all I found was this), but as I said, I don't have any serious problem with it. the likelihood of significant deviations is far less here than it is for navboxes. Frietjes (talk) 17:33, 15 July 2013 (UTC)

One of the reasons that there wasn't separate styles for each item before was because it would have made the template code a lot larger and that there's only a few infoboxes that would have a need for the use of it anyway. Since it's now in Lua, the code size is not as much of an issue. -- WOSlinker (talk) 17:51, 15 July 2013 (UTC)

Predecessor/successor fields in officeholder infobox

A discussion has been started here regarding the "predecessor" and "successor" fields in {{infobox officeholder}}, and whether the usage should be changed or the fields should be removed entirely. —Designate (talk) 22:40, 16 July 2013 (UTC)

Make rowclass work for headers

Make these changes. This makes the rowclass parameter apply to headers. Jackmcbarn (talk) 00:47, 10 August 2013 (UTC)

Done. Thanks for the fix! — Mr. Stradivarius ^{♪ talk ♪} 03:32, 11 August 2013 (UTC)

Odd body text when using infobox

I've just imported the Infobox module into my personal wiki, and after some customizing of Template: Infobox basketball biography I'm getting a strange artifact in the body of every page that calls out the template.

</th></tr></th></tr>

I can get rid of it if I remove the references to the awards and past seasons, which are the only parts of the template that have embedding in them. But if there's a reference to 'child = yes' the same text above appears in the body of my article. Any idea where I might look to get rid of this?

Jmateobaker (talk) 03:10, 5 September 2013 (UTC)

do you have the HTML tidy extension installed? it also may be possible to fix it so tidy isn't needed (see here). Frietjes (talk) 14:53, 5 September 2013 (UTC)

AIATSIS bug

hi, I noticed today that *all* pages with Infobox now have a bug: a phantom footnote is created (always fn #2 I think) with a deadlink to AIATSIS. I see no way to remove it, it must be inserted by some script related to the infobox, and to Template:AIATSIS. Thanks, Womtelo (talk) 11:10, 7 June 2013 (UTC).

I think I've fixed it with an edit at Template:Infobox language. -- John of Reading (talk) 11:50, 7 June 2013 (UTC)

It would be good to change the touchParameters function so that it only looks at label params where there is something in the corresponding data param. -- WOSlinker (talk) 12:27, 7 June 2013 (UTC)

I don't think it is worth the extra complexity. It was easy enough to fix the template once I'd worked out what the problem was. -- John of Reading (talk) 21:17, 7 June 2013 (UTC)

agreed, that would match the prior functionality. note, there is an infobox problem being discussed at Template talk:Infobox NRHP, although I am still waiting for an example, so it could predate this template change. Frietjes (talk) 21:36, 7 June 2013 (UTC)

I've worked out the true cause of this bug, and it's not touchParameters(). Well, not just touchParameters(). The problem is that once a parameter that contains a reference is processed by Lua, that reference is included in the references section no matter what. In the current case, we have a reference that was included in one of the label parameters. It is actually processed twice, despite not being used in the infobox - the first time by touchParameters() and the second time by pairs(origArgs). Fixing the former use is fairly easy, and I have done it in this revision of Module:Infobox/sandbox, but fixing the latter use would be a real pain. It would require something like adapting touchParameters() to assign the parameters to the argument table, and would mean we would have to impose arbitrary limits on how far apart parameters can be numbered. — Mr. Stradivarius ^{♪ talk ♪} 04:11, 8 June 2013 (UTC)

Also, I've added a new test case for this bug at Template:Infobox/testcases#Orphaned references. — Mr. Stradivarius ^{♪ talk ♪} 04:13, 8 June 2013 (UTC)

There's a fix for this bug in Module:Infobox/sandbox now. Because we can't use pairs(), the fix requires us to set an arbitrary limit for how far apart parameters can be numbered. At the moment this number is set to 5 for the subheader and image parameters, and to 20 for the header, label and data parameters. This means that if there was only a |data20= and a |data40= parameter, they would both get picked up no problem, but if there was only a |data20= and a |data41= parameter, the latter would be skipped. I'm thinking that it might be better to set the number to 50 for the header, label, and data parameters, but it I'm not sure how much it would impact the performance of the module. Does anyone have any good advice? — Mr. Stradivarius ^{♪ talk ♪} 16:26, 8 June 2013 (UTC)

I've put the fix up live now, so we shouldn't see any more phantom reference problems. If you do, please let me know. — Mr. Stradivarius ^{♪ talk ♪} 08:01, 9 June 2013 (UTC)

Bumping to prevent archival (I have a plan to fix this in a slightly better way at some point). Jackmcbarn (talk) 18:08, 8 September 2013 (UTC)

Bold for data cell?

How do I set "data11" in Template:Infobox holiday to bold? Sample: On La Tomatina, it would make "August 28" for 2013 stand out.

I tried adding "class11=toccolor", but the result wasn't ideal. Is there a class that adds bolding? Otherwise I guess I have to add it to data11 directly. -- 签名 _sig at 16:54, 22 September 2013 (UTC)

check MediaWiki:Common.css for bold classes. I added bold tags for the moment. Frietjes (talk) 17:19, 22 September 2013 (UTC)

Thanks, it seems to work. I had a look at the css before, but wasn't sure what to pick. -- 签名 _sig at 17:31, 22 September 2013 (UTC)

MediaWiki:Common.css is a non-starter. Only five of the rules defined there use the declaration font-weight: bold; - these are as follows:

#interwiki-completelist {
    font-weight: bold;
}
.hlist dd:after,
.hlist li:after {
    content: " ·";
    font-weight: bold;
}
.infobox caption {
    font-size: 125%;
    font-weight: bold;
}
#wpSave {
    font-weight: bold;
}
div.NavFrame div.NavHead {
    height: 1.6em;
    font-weight: bold;
    background-color: #ccf;
    position: relative;
}

Of these, two (the first and fourth) cannot be used since their selectors do not specify classes but ids; the second and fifth have other effects besides bold, which we don't want to do in an infobox (for example, the second is used to put the dots into a WP:HLIST); and the third is only effective on the <caption>...</caption> element, as seen at London Paddington station - the word "Paddington" above the infobox is a caption element. An infobox can only have one caption element, and it's always shown at the very top, above the border. --Redrose64 (talk) 19:02, 22 September 2013 (UTC)

I'm considering proposing an edit to Module:Infobox to add datastyle11 (etc.), which would allow you to do datastyle11 = font-weight: bold; and be done with it. Jackmcbarn (talk) 19:16, 22 September 2013 (UTC)

Thanks for the detailed explanation about the css. If the addition to module solves it, this sounds good to me. -- 签名 _sig at 05:41, 23 September 2013 (UTC)

Okay. I'll try to get around to doing it today at some point. Jackmcbarn (talk) 14:27, 23 September 2013 (UTC)

Define values for a series of fields of Template:Infobox

At Template:Infobox holiday/sandbox, I tried to add a rule based on the field "date".

If it matches the rule, it would use Template:Infobox holiday/1, otherwise it would use the standard output at Template:Infobox holiday/0.

Ideally, I would have left them on the main template page. For those knowing Lua, it's probably easier to move the thing directly into a Lua module.

Is there a good sample I could use? -- 签名 _sig at 04:34, 24 September 2013 (UTC)

the idea can work, but the method won't work. to make it work, you need to add both sets of labels to the main infobox, but with different numbering. then, for each data field, check the rule, and if it is true, pass the data, if not pass nothing. for example:

| label1 = September
| data1 = {{#if:{{{september|}}}| some text if September rule is a match | }}
| label2 = Not September
| data2 = {{#if:{{{september|}}}| | some text if September rule is not a match }}

I don't entirely understand what you are trying to accomplish in the sandbox, or I would help you fix it there. Frietjes (talk) 15:38, 24 September 2013 (UTC)

Have a look at Template:Infobox holiday, I got to work the first step. -- 签名 _sig at 03:06, 26 September 2013 (UTC)

I see. I moved the repeated switch statements to a subtemplate, but it should still function the same, but makes the code a little more readable (at least more readable for me). Frietjes (talk) 20:25, 26 September 2013 (UTC)

Thanks, indeed it is. Much less redundant as well. It's also easier to test it. I added test cases to, e.g. Talk:First_Day_of_Summer#Testcases. -- 签名 _sig at 03:47, 27 September 2013 (UTC)

Capitalization

I just noticed that capitalization was missing somewere. I checked another page to see what was appropriate and it also used lower case (but also upper case). I see here that it seems uppercase should be used. I just wander if it would be possible or desirable to do stuff like this automatically in the template? comp.arch (talk) 10:50, 25 November 2013 (UTC)

Capitalisation of what? Template names, parameter names, parameter values, or something else? --Redrose64 (talk) 14:03, 25 November 2013 (UTC)

Data reference

Feature suggestion. Would it be viable to add a numbered parameter that can contain the reference for a datan, and is handled as such? In boilerplate:

| label11 = Boiling point
| data11= 100<!-- defined to be in °C -->
| dataref11 = <ref>{{cite book|ref=Haynes|editor=Haynes, William M.|year=2011|title=CRC Handbook of Chemistry and Physics |edition=92nd ed.|publisher= CRC Press|isbn=1439855110|pages=4.121-4.123}}</ref>

Producing

Boiling point

100 °C 37 °F[1]

References:

^[1]Haynes, William M., ed. (2011). CRC Handbook of Chemistry and Physics (92nd ed. ed.). CRC Press. pp. 4.121–4.123. ISBN 1439855110. {{cite book}}: |edition= has extra text (help)

The issue is in play in {{infobox element}}, where data-input is processed and so ref's cannot be entered correctly with the datan value. I guess that it would also be a support for referencing wikidata too, at least as a babystep. -DePiep (talk) 13:25, 26 November 2013 (UTC)

Wouldn't it be simpler to add a "boiling point ref" parameter to Template:Infobox element than to do this? Also, that template doesn't currently use Template:Infobox, so that wouldn't help here anyway. Jackmcbarn (talk) 17:07, 26 November 2013 (UTC)

The fact should be repeated in the article's prose,and the reference located there. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:45, 26 November 2013 (UTC)

Re Jack: yes, you are right and that is the route we'll go for now. But my question was more generic. Also, we cannot use the "no data, no row" mechanism in cedrtain circumstances.

re Pigs: not quite that. -DePiep (talk) 16:28, 3 December 2013 (UTC)

No, "we" will not got with that route unless there is consensus for it; there is not. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:51, 3 December 2013 (UTC)

bug in image caption?

User:Pete Hobbs at Template talk:Infobox glacier/doc reported that image captions did not work for {{Infobox glacier}}. I took the example Infobox at Template:Infobox glacier/doc and expanded it into its underlying {{infobox}} and found that the caption was being fed to Module:Infobox, but no caption was showing up in the resulting HTML. See User:Hike395/sandbox for the call to {{Infobox}}. I believe this means there is a bug in the handling of captions in Module:Infobox, but I cannot figure out the Lua code. Can someone help? —hike395 (talk) 06:32, 10 January 2014 (UTC) Never mind: found the bug in {{infobox glacier}} code. Sorry for the false alarm. —hike395 (talk) 06:37, 10 January 2014 (UTC)

Multiple infoboxes within Lua impossible

The use of a module-local variable in the module to store infobox data seems to preclude the creation of multiple distinct infoboxes within a single Lua invocation. My plan for rewriting {{Infobox road}} includes multiple submodules parsing data, with many of those using child infoboxes to display that data in the main infobox. Is there a way this can be addressed, or do I need to change my design to use a single infobox? -happy5214 09:05, 17 January 2014 (UTC)

Hmm, that's odd. Child infoboxes are supported in the current module, otherwise many existing infoboxes would have broken when we made the switch from the old template. I think I would need an example to see what's going wrong - can you give me a link? Also, there's a planned Lua extension for writing infoboxes that should be appearing quite soon, so you might want to consider using that instead of Module:Infobox. The page is at mw:Extension:Capiunto, but it might be best to look at the code directly, as it is still being written and proper documentation is yet to come. Although I have to say, the idea of using child infoboxes inside a main infobox never really made sense to me. I always thought that people only used child infoboxes to get around technical limitations in the old infobox template, whether that was the 100-row limit, or the fact that you could only have one heading style, etc. What made you think of child infoboxes as a design choice? — Mr. Stradivarius ^{♪ talk ♪} 09:29, 17 January 2014 (UTC)

I figured with the submodules, it would be easier to create and return the contents of a child infobox from the submodule than it would be to pass around a single data table and remember/hardcode the parameter count. Also, I thought that I'd be able to allow an unlimited number of sections without going over the gap limit of 50. I'm using child infoboxes right now with my partial deployment, and they work just fine. But I wouldn't be able to create an infobox in each submodule and one in the main module without data being trampled over. -happy5214 09:56, 17 January 2014 (UTC)

Both of those problems will disappear with the Capiunto extension. It gets rid of data1, data2, etc. parameters, and instead uses something like infobox:row('a label', 'some data'):row('another label', 'some more data'). Using that it should be easy to get your submodules to return just the data, and to leave the actual rendering of html to the main module, without worrying about parameter numbers or the gap limit of 50. — Mr. Stradivarius ^{♪ talk ♪} 10:15, 17 January 2014 (UTC)

Is there a ETA for the extension? I am having the same issue as well with multiple Infoboxes on the same page. You can see at https://en.wikipedia.org/wiki/User:Zolotkey/sandbox The repair sub box only displays data 2 but skips data1 and data3. Zolotkey (talk) 20:44, 30 January 2014 (UTC)

Strange apostrophe bug

Resolved

 – This was not really a bug.

I noticed a small but weird bug at Template:Infobox medical specialty. The code had this:

| label3  = {{#if: {{{subdivisions|}}} | Subdivisions }}
| data3   = ''{{{subdivisions| }}}''

I noticed that if the subdivisions parameter was provided but left blank (as in: | subdivisions = ), a single apostrophe appeared on the place of data3. If the subdivisions parameter was not provided at all, this didn't happen. Here is a screenshot.

In a random attempt to fix it, I changed the code to this:

| label3  = {{#if: {{{subdivisions|}}} | Subdivisions }}
| data3   = {{#if: {{{subdivisions|}}} | ''{{{subdivisions|}}}'' }}

This worked (after purging cache). I have reproduced the bug at Template talk:Infobox medical specialty/sandbox. Cheers, theFace 12:40, 3 February 2014 (UTC)

Yes, that's the correct thing to do, although the if could be removed from label3 as it's not needed. -- WOSlinker (talk) 13:02, 3 February 2014 (UTC)

| label3  = Subdivisions
| data3   = {{#if: {{{subdivisions|}}} | ''{{{subdivisions|}}}'' }}

That's not a bug. It's working as intended. Jackmcbarn (talk) 13:28, 3 February 2014 (UTC)

Yes, when you have wikicode in a template like ''{{{subdivisions| }}}'' and |subdivisions= is blank or absent, what you get is '''' which renders as ' - notice how it displays a single apostrophe before turning boldface on; therefore, the second through fourth apostrophes are being interpreted as "boldface on", instead of the whole group being interpreted as a pair of "italics on/italics off". --Redrose64 (talk) 13:55, 3 February 2014 (UTC)

Ok, thanks for the help guys! Just figured out how Mediawiki does it. This had me puzzled, but indeed it's not a bug. Cheers, theFace 14:37, 3 February 2014 (UTC)

PS: woah... just been renamed! :-) Manifestation 14:56, 3 February 2014 (UTC)

Here's a slightly better demo of how the apostrophes are handled. --Redrose64 (talk) 15:18, 3 February 2014 (UTC)

Thank you! It seems logical that MediaWiki automatically closes such tags at the end of a paragraph if no end tag is given. It does not do so with other tags, however. Cheers, Manifestation 18:15, 3 February 2014 (UTC)

there is a difference between html tags, and wikimarkup. for html tags, the syntax used for closing is different from opening. for wikimarkup, frequently the closing syntax is the same as the opening syntax, and there is even more ambiguity when it comes to bold and italics. for example, four consecutive apostrophes could either mean open and close italics, with nothing inside, or open bold plus apostrophe, or apostrophe plus close bold. Frietjes (talk) 21:17, 3 February 2014 (UTC)

Change image caption from a div to a paragraph

Right now the main image caption is stuck in a div right below the image with no padding or margins. This causes the text to run right up against the image. Compare our infobox in Großer Nickus with the German version. This can easily be fixed, however, by simply changing the div tag into a paragraph tag (<p></p>). Paragraph tags automatically inherit top and bottom margins from the skin stylesheets (in Vector: 0.4em top; 0.5em bottom). An alternate suggestion would be to specify a default margin for the div tag. Thoughts? Kaldari (talk) 04:42, 5 February 2014 (UTC)

Captions are not displayed with Infobox programming language

Hi,

As you can see it on Fortran or C (programming language), the caption is not displayed whereas the "caption" parameter is given.

Someone familiar with the source code could there take a look?

Regards, Automatik (talk) 17:13, 6 February 2014 (UTC)

fixed. Frietjes (talk) 17:22, 6 February 2014 (UTC)

Use of list markup in the title section

Example 1

• One
• Two

Three Four

Example 2

• One
• Two

Three Four

I'm guessing this is a known problem, but list markup does not work in the |title= field? this came up after it was noted that Pigsonthewing's suggestion to use {{plainlist}} in the |native_name= field in infoboxes. unfortunately, this does not work when the native_name is appended to the name in the title field (see the code in the example). Frietjes (talk) 15:56, 8 February 2014 (UTC)

okay, I now see that this is a more fundamental limitation, since it doesn't work in html either, so I guess we will have to find and correct these errors :( Frietjes (talk) 16:02, 8 February 2014 (UTC)

I've explained this before (in navbox). This is the result of HTMLTidy kicking the list out of the table caption because it does not allow any block elements (the list) to live inside any inline elements (the table caption). There is no fix for this, save disabling HTMLTidy. — Edokter (talk) — 17:51, 8 February 2014 (UTC)

"inline" should be changed to "block-inline" and it should then work properly. If it still does not work, check the HTMLTidy configuration file. A lot of things, especially HTML5 and CSS3 new items are turned of by default in the configuration file (or an old website is just using an old configuration file). But this might be something that needs to handled on the code level and not something that a general editor can fix. — Preceding unsigned comment added by Zzmonty (talk • contribs) 13:31, 7 March 2014 (UTC)

@Frietjes: What is the use case for using a list in the title parameter in this way? Do you have an example? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:40, 8 February 2014 (UTC)

It's a change in the spec between HTML 4 and HTML 5. Under HTML 4, the <caption>...</caption> element could only contain inline content (the A ABBR ACRONYM B BDO BIG BR BUTTON CITE CODE DFN EM I IMG INPUT KBD LABEL MAP OBJECT Q SAMP SCRIPT SELECT SMALL SPAN STRONG SUB SUP TEXTAREA TT VAR elements), which did not include lists. But under HTML 5, a <caption>...</caption> element can now contain flow content; and a list (whether <ul>...</ul> or another type) is a type of flow content, so it should be permitted. --Redrose64 (talk) 23:19, 8 February 2014 (UTC)

Blame Tidy. I checked its history, and came to the conclusion that Tidy hasn't been maintained since June 2008, long before HTML5 was even conceived. So updateing that dinosaur is not an option. Should we disable it, or search for a new HTML sanitizer? — Edokter (talk) — 10:34, 9 February 2014 (UTC)

@Pigsonthewing: I fixed the most recent case here. if you notice, the 'native_name' field was in the title= field. if you check Arab people, you will see there is a list of names in the title section, delimited by <br> tags. this cannot be simply changed to a plainlist. however, it can be moved inside the box, and changed to a plainlist. Frietjes (talk) 14:29, 9 February 2014 (UTC)

Tagging Changeover to Lua

This might be too late in the game, or maybe somebody with access to the actual database can handle this. But for each template that now uses "Lua", there should be a consistent tag to mark exactly when that changeover took place. Or even a version number. Some examples could be:

• Template changeover to Lua
• Now using Template 2.0

Also, all of the Infobox templates should have a snapshot export that is easily accessed. Or even taking a snapshot of the template and putting it in an Template old:Infobox location. I am not the only person who is having trouble getting Lua to work on a hosted system. And I don't really feel like wasting my time trying to back install all of the old templates instead of just being able to do the work I want to do. Does anybody know if a single person handled all of the changeover and who that person was, so somebody can just look for that person's name in the history? — Preceding unsigned comment added by Zzmonty (talk • contribs) 13:12, 7 March 2014 (UTC)

If you want pre-Lua versions, just look through the revision history to find them. Lots of people converted the templates. Jackmcbarn (talk) 19:38, 7 March 2014 (UTC)

Colour support

Hi please add colour support for background colours and support for colours around text. 90.219.225.13 (talk) 20:05, 13 March 2014 (UTC)

We already support that. Check the doc page for examples. Jackmcbarn (talk) 20:10, 13 March 2014 (UTC)

Template:infobox setup box template create

Hi can we create a new template called Template:infobox setup box please. It would have bits a peaces from infobox software and some other infobox on here. Reason we intergrated some of infobox software into the template is because some setup boxes have software which is then versioned and updated regular. I would like to to use the new template on Sky+ HD please. 94.2.129.149 (talk) 13:40, 19 March 2014 (UTC)

Shouldn't that be "set-top box", not "setup box"? Also, you don't need permission to create an infobox - just read the instructions and have a go yourself. You can use Template:Infobox software as an example. — Mr. Stradivarius ^{♪ talk ♪} 14:34, 19 March 2014 (UTC)

We already have {{Infobox information appliance}}; any extra parameters needed should be added, or requested in its talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:47, 19 March 2014 (UTC)

tracking bogus params?

At Help_talk:Template#how can I test for unsupported parameters?, User:Frietjes suggested it would be possible to write a generic module to track bogus parameters. I think this would be worth doing. {{Infobox language}}, for example, often contains ad hoc parameters that users unfamiliar with the template have added. Sometimes you can see them struggling to get them to display, only to give up, leaving the unsupported lines in the box. Often this should just be deleted, but sometimes it would be worth converting to a supported parameter. I have a tracking category for a few unsupported parameters that had been common in the past, but they almost never crop up any more (most of them were legacy names), and we could remove that code from the template if we had a general tracking module. — kwami (talk) 19:19, 11 March 2014 (UTC)

answered on your talk page, but for anyone else interested, see Module:Check for unknown parameters. Frietjes (talk) 19:04, 24 March 2014 (UTC)

@Frietjes and Kwamikagami: This module looks like a useful stop-gap fix, but the best solution would be to port the infoboxes to Lua and do the check inside the individual infobox modules. Ideally we would do this with mw:Extension:Capiunto, but I haven't heard any new developments from that recently. Perhaps I should try my own hand at writing a Module:Infobox builder and possibly integrate this functionality there. — Mr. Stradivarius ^{♪ talk ♪} 02:02, 25 March 2014 (UTC)

I'm happy to have this, it's working great, but I'll leave it to you to make any improvements. — kwami (talk) 02:10, 25 March 2014 (UTC)

Useful in non-infobox templates too. -DePiep (talk) 06:24, 25 March 2014 (UTC)

Even better: very useful for pre-Lua infoboxes! To analyse and clean up parameters before switching it to Lua (module:infobox or other). A central talk is at module talk:Check for unknown parameters. -DePiep (talk) 08:35, 25 March 2014 (UTC)

Actually, DePiep's suggestion that we move the list of parameters to a module data page has alleviated my concerns above to a great extent. I've made a more detailed comment on the module talk page. — Mr. Stradivarius ^{♪ talk ♪} 08:59, 25 March 2014 (UTC)

Creating infobox for mobile internet and mobile telephone

Hi can we create an infobox for mobile internet and mobile telephone please. I found one similer to what I am looking for but I am not sure if it could be used for mobile networks Template:Infobox telecommunications network. 86.135.250.172 (talk) 10:13, 3 April 2014 (UTC)

We already have {{Infobox mobile phone}}. If this is lacking in features, the place to discuss it is Template talk:Infobox mobile phone. --Redrose64 (talk) 11:23, 3 April 2014 (UTC)

That's for devices; I think the OP wants a box for networks, in which case {{Infobox telecommunications network}} is the one to use - but as you say, the relevant talk page is the place to request new parameters or other changes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:47, 3 April 2014 (UTC)

Default infobox image size

The default infobox image size seems to have changed from 220px to 200px. Was this an intended change, or is there a technical problem? Bede735 (talk) 10:02, 4 April 2014 (UTC)

Nothing has changed here. The infobox image never had a default. — Edokter (talk) — 11:34, 4 April 2014 (UTC)

headerclass

There doesn't appear to be a headerclass option... Is this correct? If so, any particular reason why..? Curious, Sardanaphalus (talk) 09:55, 7 April 2014 (UTC)

No... we seem to have aboveclass, subheaderclass, titleclass --Redrose64 (talk) 11:41, 7 April 2014 (UTC)

Correct, this was also true for the old template. The only way to change the class for headers is through the numbered class parameters. The classes were generally added to support microformats, where there wouldn't be a big need to add the same class to every header. However, this could be very useful for styling. Thanks! Plastikspork _―Œ^(talk) 14:16, 7 April 2014 (UTC)

• Then, do you (Plastikspork, Redrose64) or does anyone else watching this know how to add headerclass to the template, please? What I know about Lua is about the same as what that waiter from Barcelona knew... Sardanaphalus (talk) 15:01, 7 April 2014 (UTC)
  • Sure, I could add a headerclass parameter to the module, if there are no objections. I'm sure Mr. Stradivarius could do it even faster :) Do you have a particular application in mind? Thanks! Plastikspork _―Œ^(talk) 01:32, 9 April 2014 (UTC)
    • I've added it to the sandbox. Test it out with {{infobox/sandbox}}, and let me know if it does what you want. If everything looks good, I'll update the main module. — Mr. Stradivarius ^{♪ talk ♪} 05:23, 9 April 2014 (UTC)

• Apologies for the pause. I've just used Infobox/sandbox here and tested that here and first impressions are that all's working well (i.e. thanks to headerclass, the headings within the template all look to be navbox-abovebelow class). Sardanaphalus (talk) 02:35, 14 April 2014 (UTC)
  • Ok, I've added it to the main module. — Mr. Stradivarius ^{♪ talk ♪} 04:46, 14 April 2014 (UTC)
    • Thanks. If I spot any strange effects, I'll ping again. Sardanaphalus (talk) 08:54, 14 April 2014 (UTC)

Articles which use infobox templates with no data rows

There are now 24,160 members of the above hidden category. Is there a way to stop articles being added to this category when using an infobox based template? ► Philg88 ◄ ^♦talk 09:55, 14 April 2014 (UTC)

Educate them? I looked at the first entry in Category:Articles which use infobox templates with no data rows, it's 39th Infantry Brigade Combat Team (United States)#Current units where several infoboxes seem to be used as a means of neatly arranging some military insignia. --Redrose64 (talk) 10:34, 14 April 2014 (UTC)

@Redrose64: Sorry, perhaps I should be more specific: I don't think that using {{Infobox Chinese}} to display traditional and simplified characters along with their romanisations should throw an exception –if that's what is is– about a missing data row when that is exactly what the template is supposed to do. Is that a problem with the infobox or the derivative? ► Philg88 ◄ ^♦talk 10:44, 14 April 2014 (UTC)

{{Infobox Chinese}} has three main subtemplates - {{Infobox Chinese/Header}} {{Infobox Chinese/Chinese}} and {{Infobox Chinese/Footer}} which seem to operate in an overcomplicated way. They are using multiple instances of {{infobox}} to create single rows; it's not clear why a single all-enveloping {{infobox}} could not have been used. In the old (pre-Lua) days, if you wanted a template to create a single row in an infobox, you'd use {{Infobox/row}} - but I don't think that option is available any more. --Redrose64 (talk) 11:06, 14 April 2014 (UTC)

(edit conflict) {{Infobox/row}} should still work. But if just using one instance of {{infobox}} could also do the job, then that would be better. — Mr. Stradivarius ^{♪ talk ♪} 11:45, 14 April 2014 (UTC)

I found that of the three subtemplates, {{Infobox Chinese/Chinese}} pretty much always has data rows, but {{Infobox Chinese/Header}} and {{Infobox Chinese/Footer}} never do. I removed them one by one from an article, and previewed to see how it was categorised - and found that {{Infobox Chinese/Footer}}, when used alone or with {{Infobox Chinese/Chinese}}, doesn't put the page into Category:Articles which use infobox templates with no data rows but {{Infobox Chinese/Header}} always does, whether it's alone or with either or both of the others. I compared the header and footer, those being the two w/o data rows: and on the strength of that, I made this edit. --Redrose64 (talk) 11:41, 14 April 2014 (UTC)

Thanks for the edit but I'm still seeing the issue, for example, with this article. The rogue category remains despite there being data rows for t, s and p in {{Infobox Chinese/Chinese}}. Is it because that template includes an instance of {{Infobox Chinese/Header}}? ► Philg88 ◄ ^♦talk 12:48, 14 April 2014 (UTC)

All you need do with articles like Li Zhijian is wait for the job queue, which might take some days. If you can't wait that long, a WP:NULLEDIT to the article will fix it immediately - for that specific article. --Redrose64 (talk) 14:22, 14 April 2014 (UTC)

I can wait :). Your help is much appreciated, thanks. ► Philg88 ◄ ^♦talk 15:02, 14 April 2014 (UTC)

Protected edit request on 20 April 2014

Please change "function union(t1, t2)" to "local function union(t1, t2)". Jackmcbarn (talk) 23:20, 20 April 2014 (UTC)

Done — Mr. Stradivarius ^{♪ talk ♪} 07:04, 21 April 2014 (UTC)

Use mw.html instead of Module:HtmlBuilder

Hi!

Could someone migrate this module as Ricordisamoa did on these edits? Helder.wiki 14:44, 22 April 2014 (UTC)

I'm holding off on mw.html migration until we get Wikipedia talk:Lua/Archive 2#mw.html library nil behaviour sorted out. But after that, sure. — Mr. Stradivarius ^{♪ talk ♪} 14:58, 22 April 2014 (UTC)

Protected edit request on 25 April 2014

I wish to add the credit Sound design = Aza Hand Handocalbrisian (talk) 09:27, 25 April 2014 (UTC)

@Handocalbrisian: this is the talk page for a meta-template used to make infobox templates. It sounds like you would like to add a piece of information in an infobox in a specific article. Either you can edit that article directly, or you can make an edit request on that articles talk page. There's nothing we can do about it here. Imzadi 1979 → 09:42, 25 April 2014 (UTC)

Protected edit request on 28 April 2014

Can this template (be set to) use basestyle "à la" {{Navbox}} family..?

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:...;..?

Thanks, Sardanaphalus (talk) 09:18, 28 April 2014 (UTC)

Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. Jackmcbarn (talk) 12:03, 28 April 2014 (UTC)

• How?  Sardanaphalus (talk) 13:40, 28 April 2014 (UTC)

(1) open Module:Infobox/sandbox, (2) click edit, (3) make changes, (4) click save. or are you saying that you don't know how to program in LUA? Frietjes (talk) 14:48, 28 April 2014 (UTC)

Protected edit request on 29 April 2014

Aaraindhaseyal (talk) 18:10, 29 April 2014 (UTC)

Please kindly Edit the protected content and make it available for the normal use

what do you want changed? Frietjes (talk) 18:17, 29 April 2014 (UTC)

Re: User:Pigsonthewing/Direct calls to Infobox‎

May I ask you to please accept the direct use of this template as viable alternative to other templates? This is the most flexible and the most versatile infobox template we have. Only here, the individual features can be adjusted to meet unique needs for additional fields not covered by other templates. Take as an example the fields I created thanks to this template at the Holocaust train. No other infobox template would allow for it. So please keep it open for the desired use as well. Thanks a million, Poeticbent talk 21:30, 30 April 2014 (UTC)

Who has said that {{Infobox}} may not be used as a "viable alternative to other templates"? Please avoid FUD. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:27, 30 April 2014 (UTC)

This is because User:Nikkimaria suddenly began to delete {{Infobox}} templates en masse from articles unrelated to each other, with odd edit summaries like "rewrite" (sic). I thought it was because of your User:Pigsonthewing/Direct calls to Infobox‎ call. I might have been wrong, but the red flag for me was the one article I worked on, Franciszek Mączyński. Here are just a few other samples of other articles among many. Cheers, Poeticbent talk 23:21, 30 April 2014 (UTC)

• https://en.wikipedia.org/w/index.php?title=Poor_Susan&diff=prev&oldid=606529999
• https://en.wikipedia.org/w/index.php?title=Victor_Bedikian&diff=prev&oldid=606530715
• Character of the Happy Warrior
• Richard Harris (composer)
• https://en.wikipedia.org/w/index.php?title=Franciszek_M%C4%85czy%C5%84ski&diff=prev&oldid=606520427
• I Wandered Lonely as a Cloud
• Ernesto Köhler
• Blues dance
• https://en.wikipedia.org/w/index.php?title=Blues_dance&diff=prev&oldid=606514886
• https://en.wikipedia.org/w/index.php?title=Edgar_Ortenberg&diff=prev&oldid=606518687