Template talk:Infobox/Archive 13

Archive 10

Archive 11

Archive 12

Archive 13

Archive 14

Archive 15

→

Archive 19

Is Jewish a religion?

This discussion belongs on Talk:Bernie Sanders
The following discussion has been closed. Please do not modify it.
I think that an edit of three days ago removing "Religion: Jewish" from the Bernie Sanders article runs contrary to the findings of the above RfC. The proposer of the above RfC, with an edit summary reading "not a member of any religion", removes "Religion: Jewish" from the Bernie Sanders article despite the press package of Bernie Sanders reading "Religion: Jewish". How is that edit reconcilable with the RfC above? Bus stop (talk) 19:41, 31 January 2016 (UTC) Both of you have provided at least a source. You want inclusion of something in an article. You should discuss this on Talk:Bernie Sanders.--Müdigkeit (talk) 20:19, 31 January 2016 (UTC) On the contrary no source says Bernie Sanders is not Jewish. And this edit was made by the editor that proposed the above RfC. Would not the proposer of the above RfC understand its implementation? You wrote above, in closing this RfC, "The determination if something is a religion or a non-religion should be based on reliable sources and not on the personal opinions of Wikipedia editors…" Has the above RfC resolved the question at the heart of this matter? No, it has not. Not only do numerous other sources tell us that Bernie Sanders is Jewish, but Bernie Sanders tells us himself, in his press package, that he is Jewish. Bus stop (talk) 20:41, 31 January 2016 (UTC) I've made this notification to Wikipedia talk:WikiProject Judaism. Bus stop (talk) 20:46, 31 January 2016 (UTC) Bus stop, on top of posting your grievances in the wrong place, (this belongs at Talk:Bernie Sanders), you have quoted me out of context. My edit summary did not say "not a member of any religion". it said "not a member of any religion. See [ https://www.washingtonpost.com/politics/bernie-sanders-finally-answers-the-god-question/2016/01/26/83429390-bfb0-11e5-bcda-62a36b394160_story.html ]." I wouldn't have made the edit without a source to back it up. As for your question "How is that edit reconcilable with the RfC above?" The RfC covers this exact question: "Jew/Jewish" is a special case. The word has several meanings, so the source cited needs to specify the Jewish religion, as opposed to someone who lives in Israel or has a Jewish mother. The Washington Post source[1] specifies exactly that. If you have a source that says that does specify the Jewish religion, post it on the article talk page. The RfC specifically declines to say what "Jewish" means on a particular page. and thus this is completely off-topic here. Please stop trying to WP:FORUMSHOP and discuss this on the article talk page where it belongs. --Guy Macon (talk) 21:30, 31 January 2016 (UTC) (edit conflict) FFS, how many times is this going to be discussed? Sanders is Jewish. See Talk:Bernie Sanders/Archive 2#Is Sanders "Jewish" and does he have dual-citizenship? and Talk:Bernie Sanders/Archive 2#Religion: Jewish and Talk:Bernie Sanders/Archive 3#Jewish, again and Talk:Bernie Sanders/Archive 3#Religion and Talk:Bernie Sanders/Archive 4#"Religion: Judaism". No, this should not have to be discussed de novo every time a troll decides to vandalize the article. — Malik Shabazz Talk/Stalk 21:35, 31 January 2016 (UTC) Guy Macon—there is something called transparency. The above RfC has been a waste of everyone's time. I doubt that many of the participants could have anticipated that it would be misused this way. Bus stop (talk) 22:16, 31 January 2016 (UTC) {{hidden archive bottom]}}

Closure of RfC

I thought that an RfC could only be closed by an administrator? Müdigkeit isn't an admin. Could someone confirm this? Also the reason given is simply about numbers and doesn't mention anything about consensus. Gaia Octavia Agrippa ^Talk 10:14, 1 February 2016 (UTC)

No, an RfC can be closed by anyone who's uninvolved. Curly Turkey 🍁 ¡gobble! 10:26, 1 February 2016 (UTC)

Off-topic material, unrelated to Template:Infobox.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  13:31, 24 March 2016 (UTC)

To expand on the above a bit, there are two ways an RfC can be closed; based on rough consensus and based on policy. (The closing can and often does involve both.) Here are the relevant pages: Wikipedia:Requests for comment#Ending RfCs Wikipedia:Closing discussions#How to determine the outcome Wikipedia:Closing discussions#Challenging other closures Wikipedia talk:Requests for comment/Archive 12#Review This RfC closing involved both. First, it affirmed the overwhelming consensus that the proposition passed, then made it clear that no matter what the consensus here is, the determination if something is a religion or not should not be made by Wikipedia editors, but rather by following the sources as specified in our core content policy WP:No original research. That's the policy part of the closing. I fully agree; that's a proper application of existing policy. --Guy Macon (talk) 13:11, 1 February 2016 (UTC) There hasn't been a consensus formed here: "Consensus can be most easily defined as agreement" and "Consensus is not determined by counting heads". If anything, this needs more time to have a proper discussion (rather than arguing back and forth) and to come to some sort of agreement as a whole. One side having more people doesn't mean that that group automatically holds the consensus sign. Gaia Octavia Agrippa Talk 13:49, 1 February 2016 (UTC) Support votes stated that something that isn't a religion shouldn't be labeled as religion. They also say that in all those cases of no religion, or something that is not a religion being sourced as important, the information could be put somewhere else. You say that information should be presented in the infobox part of religion, because none would be a valid answer. The arguments presented seem to have equal quality(apart from those arguments about neutrality and NOR regarding what a religion is)... well, it comes down to numbers. And those are in favor of the supporters.--Müdigkeit (talk) 15:52, 1 February 2016 (UTC) Thank you Müdigkeit for the explanation. I had hoped that if the discussion had returned to being more civil then a compromise could have been reached. But the RfC has been closed and it is unlikely that I would be able to have it restarted. Gaia Octavia Agrippa Talk 19:31, 1 February 2016 (UTC) The RfC ran for the standard 30 days, and there was exactly one !vote in the last 7 days it ran. More time would be extremely unlikely to result in a different result. You are free to challenge the closure (link with instructions in my comment above) but unless you successfully challenge the closure, by definition we have a consensus and you are required to abide by that consensus whether you agree with it or not. Failure to do so will result in you being blocked from editing Wikipedia. --Guy Macon (talk) 20:25, 1 February 2016 (UTC) I've been around along enough to not do things that will get be blocked but thank you for the slightly threatening reminder. I wasn't questioning the closure because I disagree with it, I questioned the closure because the reason given was the number votes (which goes against "Consensus is not determined by counting heads"). As stated above, I had hoped that reasonable discussion would have eventually resulted in some kind of universally supported result. Gaia Octavia Agrippa Talk 20:58, 1 February 2016 (UTC) I apologize if what I wrote sounded threatening. I just wanted to make it clear that questioning the closure is OK but disobeying it is not. I believe that you may have a misconception about "counting heads". The relevant explanation is at Wikipedia:Closing discussions#How to determine the outcome: "...after discarding irrelevant arguments: those that flatly contradict established policy, those based on personal opinion only, those that are logically fallacious, those that show no understanding of the matter of issue [...] the closer is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it." That's exactly what the closer did in this case, and I predict that if you challenge the close the result will be a finding that the close was done properly and accurately reflects the consensus. --Guy Macon (talk) 21:16, 1 February 2016 (UTC) Apology accepted. I won't be challenging it, as it seems to be very hard to get a RfC reopened, and I certainty won't be running around adding atheist to a bunch of infoboxes out of spite. However, I'll remember to loudly suggest to keep the next one I'm involved in open if more more discussion is needed. Gaia Octavia Agrippa Talk 21:33, 1 February 2016 (UTC)

Citations in Infobox zodiac

I am improving Template:Infobox zodiac to correct the generated dates. I would like to include a citation in the infobox that would have a superscript within the infobox that leads to the article's list of references. However, different articles have different citation styles. What approaches have been tried to make a citation in an infobox compatible with various citation styles? Jc3s5h (talk) 17:38, 24 March 2016 (UTC)

Using data from wikidata

Could we make it any easier to use wikidata on infobox templates? For example, rather than including the following code on the infobox template:

|data2     = {{#invoke:Wikidata|getValue|P123|{{{parameter_name|FETCH_WIKIDATA}}}}}

would it be possible to just define the following:

|data2     = {{{parameter_name|}}}
|property2 = 123

and then this template would do the business of obtaining the data from the relevant property if the parameter was undefined? — Martin (MSGJ · talk) 15:23, 31 March 2016 (UTC)

MSGJ, this would be possible, but easier to implement if the syntax were

|data2     = {{{parameter_name|FETCH_WIKIDATA}}}
|property2 = 123

assuming you want the functionality to be unchanged. Frietjes (talk) 15:35, 31 March 2016 (UTC)

Okay, is that to make it possible to explicity define the parameter to be blank and not use Wikidata? I suppose that is a valid editorial choice and should be respected. In which case your proposed implementation is still slightly easier than the current setup. — Martin (MSGJ · talk) 15:39, 31 March 2016 (UTC)

correct, we need some way to distinguish between omitted and blank. Frietjes (talk) 16:50, 31 March 2016 (UTC)

Okay, well let's see if anyone else is interested in doing this. Nice to have a technical discussion on this talk page for once ;) — Martin (MSGJ · talk) 18:20, 31 March 2016 (UTC)

This seems like a little bit more of a complex request than not. What about qualifiers and references? --Izno (talk) 18:59, 31 March 2016 (UTC)

I don't know, please explain more. But I've seen the simple implementation described above in several templates, so I thought it worth exploring ideas here. Generally it is good to move as much technical code to the meta-template as possible to simplify creation and maintenance of the separate templates. — Martin (MSGJ · talk) 10:14, 5 April 2016 (UTC)

See Help:Qualifiers. Let's take the case of spouse. This property has a required qualifier of start time (and another for end time). How would the module handle these? What about cases where the qualifier isn't mandatory for a particular claim, but is necessary for that particular claim on that particular item, because it is differentiating the claim from another, (possibly valid) claim? --Izno (talk) 11:54, 5 April 2016 (UTC)

I recognise the complication. So is it your opinion that this idea is not worth pursuing? — Martin (MSGJ · talk) 15:37, 6 April 2016 (UTC)

It's probably something that needs a lot of testing if pursued here. My inclination is that indeed, this template is the wrong location (right now) for this kind of handling. We still don't have a lot of infoboxes pulling Wikidata, so at a later date when such is common place, we might consider reviewing how the various templates are coded. --Izno (talk) 15:41, 6 April 2016 (UTC)

Protected edit request on 7 April 2016

Add his religion to infobox as he was a very religious man. Vikramadityachandel (talk) 18:07, 7 April 2016 (UTC)

 Not done

First we have no idea whose article this is about. Even if we did this is not the place for the request. The talk page of the article is. MarnetteD|Talk 18:19, 7 April 2016 (UTC)

Protected edit request on 9 April 2016

Hello! I noticed there were a few typos in the info box at the top of the page. I.E. it says "news editor" and there are several, as well as "managing editors" and there is only one. Additionally, Laura Johnston is not an opinion editor, she's a senior editor. If you could please give me permission to approve this request that would be great! I work for the Columbia Missourian and the editor in chief, Tom Warhover, asked me to edit and correct this page. Thanks.

Lc sherman (talk) 00:07, 9 April 2016 (UTC)

@Lc sherman: this isn't the correct place to request a change to the text of an article. This is the talk page for discussing changes to {{infobox}}. I think you want to make your request on Talk: Columbia Missourian instead. Imzadi 1979 → 00:49, 9 April 2016 (UTC)

Example infobox (in section Examples) uses File:Example.png

It should probably be using File:Example-serious.jpg 10:39, 26 April 2016 (UTC) — Preceding unsigned comment added by 217.119.235.14 (talk)

The example infobox was in Template:Infobox/doc, which is not protected. I have changed the picture as suggested. —  crh ₂₃  (Talk) 10:09, 9 May 2016 (UTC)

RfC: Wikidata in infoboxes, opt-in or opt-out?

Wikidata has begun to be automatically imported into infobox fields. Should this be opt-in or opt-out? Please take part in the discussion at Wikipedia:Village pump (policy)#RfC: Wikidata in infoboxes, opt-in or opt-out?. Curly Turkey 🍁 ¡gobble! 01:18, 16 May 2016 (UTC)

The title in mobil devices

It seems as if the title of some infoboxes, for instance the on organizations, are reproduced a bit strange on mobile devices. The normal titles is aligned to the left, whereas the native title seems to be aligned at the center. Is that by purpose? Chicbyaccident (talk) 08:40, 3 June 2016 (UTC)

I reported this in March, but nobody seemed interested in fixing it. – Jonesey95 (talk) 13:48, 3 June 2016 (UTC)

That might need to be reported at Phabricator. We could fix it in Mediawiki:mobile.css but I don't see any particularly infobox-specific stuff in there, which leads me to believe the fault is mostly in the non-wiki file loaded by the mobile website/app. --Izno (talk) 14:33, 3 June 2016 (UTC)

Image field

Why does Template:Infobox person use filename only in the "image" field, but Template:Infobox uses full image syntax? I can never remember which takes what and have to look it up. Kendall-K1 (talk) 13:34, 25 June 2016 (UTC)

Use of thumbnails in Infobox

I am working on cleaning out the maintenance category Category:Pages using infoboxes with thumbnail images and I'm curious if there is a way we can use the Infobox template/module to help prevent NEW occurrences of thumbnails. Is there a way for the infobox to throw an error in preview when someone tries to add a new thumbnail? --Zackmann08 (^{Talk to me}/_{What I been doing}) 19:00, 15 July 2016 (UTC)

Template:Infobox restaurant

I’ve noticed a problem with this template. Posting here also as it’s talk page is relatively inactive, and the problem may be related to this template or its module. The thread is Template talk:Infobox restaurant#Map not working.--JohnBlackburne^words_deeds 14:37, 16 July 2016 (UTC)

Conditional header

Hello! The documentation for template:infobox says (quote) "Ideally, the Lua module supporting this template should now support a new way to make each header row autohideable by detecting if there is at least one non-empty data row after that header row" (unquote).

I think that is a great idea, so I thought about an easy way to implement that. The result is the altered Lua module in Module:Infobox/sandbox. Here is a diff from the current version.

The new version should not change anything at all for current infoboxes, but it introduces a new series of parameters, called condheader(n) for conditional header. A condheader will work exactly as a normal header if it is followed immediately by a data row in the infobox. But if the next row is not a data row, the condheader will be suppressed. I have a modified Template:Infobox bridge which uses condheader(n) in my personal sandbox together with a redirection to Module:Infobox/sandbox, so the new code can be tested for bridge articles using Special:TemplateSandbox with User:Dipsacus fullonum/sandbox as sandbox prefix.

I hope you will like the idea too! It could make many infoboxes simpler to code and maintain. Best regards, Dipsacus fullonum (talk) 20:34, 8 August 2016 (UTC)

Genral RfC on Infoboxes?

At Talk:Noël_Coward#RfC: Should an Infobox be added to the page?, there's been some assertions that an RfC needs to be performed here in order to address issues raised in the RfC for an infobox at Noël Coward. I don't understand this myself, but maybe someone more familiar with maintaining this template can discern what this is about? In that (rather long) discussion, there are several links to this talk, Template Talk:Infobox, that mention this possible general RfC. (The first is mine, where I thought I understood this, but I get much less sure with each of the following ones.) Thanks in advance. --A D Monroe III (talk) 17:23, 21 August 2016 (UTC)

Line-break bug in data values

foos	foo1 foo2 foo3 foo4 foo5 foo6 foo7 foo8 foo9

When <br> is used to create a multiline |dataN= value, the template/module displays with a stray blank line in the middle (between "foo6" and "foo7" at right). According to the raw HTML source, it's lumping the first few lines in one <p> and then a separate <p> for the later lines, which is wrong both semantically and for display purposes. It seems to happen at whichever location is the last newline in the source. DMacks (talk) 18:38, 31 August 2016 (UTC)

Code used is:

{{Infobox
| label1 = foos
|  data1 = foo1
<br>foo2
<br>foo3<br>foo4
<br>foo5
<br>foo6
<br>foo7<br>foo8<br>foo9}}

-- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:21, 31 August 2016 (UTC)

Can we have a simpler Infobox?

Hello,

To be honest, I found the current infobox module really confusing and hard to understand considering how messed up when it have CSS and HTML code nested in the lua codes... So, I'm wondering if it's possible to have a more simpler module without any of CSS and HTML code lines? it will be usefull for every new user of mediawiki and please, add the comments that explain how each function works.

Thank you very much and enjoy your day!

Allaze-eroler (talk) 22:36, 6 September 2016 (UTC)

Need help crafting a new infobox.

I have been creating lists of presidential elections by state, an example being United States presidential elections in New York. I would like to craft a custom infobox for these 51 pages containing a location map of the state, state flag/seal, and blanks for the set of parameters set forth at Draft:Template:Infobox elections by state‎. Any help with the wiki-fu for this would be appreciated. Cheers! bd2412 T 02:26, 16 September 2016 (UTC)

I recommend taking a look at other infobox templates, like {{Infobox mountain}}, to see the de facto standard used in naming parameters. Capital letters in parameter names will cause you nothing but trouble. – Jonesey95 (talk) 03:45, 16 September 2016 (UTC)

Thanks for the advice. I assume that there is some workaround where the parameter name differs from the display name, when the display name needs to display a capitalized term. bd2412 T 04:29, 16 September 2016 (UTC)

(Also, to be clear, when I say "I would like to craft a custom infobox" I really mean "can someone who knows how please make this infobox). Cheers! bd2412 T 12:43, 16 September 2016 (UTC)

Remove the "testing purposes" label for the "assume args are being passed directly in" case in module

Some infobox modules such as Module:Infobox_road and Module:Infobox_settlement calls the Infobox module and feeds it with arguments in testing mode. A few Module:Infobox derivatives are used this way as well, sometimes by more commonly-used modules like Module:Infobox gene. This unofficial usage makes sense as writers would have to copy the whole template and modify it otherwise.

As more and more infobox templates are being converted to Lua module, it seems necessary to convert the testing-only status for directly argument-passing usage to a normative one. This change would help module writers write modules more confidently by declaring a previously testing-only interface stable.

--Artoria2e5 emits crap 14:02, 13 October 2016 (UTC)

{{dead link}} embedded in infobox

Is it possible to leave a {{dead link}} inside an infobox? See example Footnote #1 the rendering is messed up. -- GreenC 19:11, 10 November 2016 (UTC)

It usually works. It fails in that example because the undocumented {{Infobox Syrian settlement}} assumes the parameter pop_ref_cbs only contains a url. Some templates make operations on some parameters which fail if the parameter doesn't have the expected type, e.g. a pure number or url. PrimeHunter (talk) 21:55, 10 November 2016 (UTC)

Thanks. Do you see a solution so that this and other infobox's don't break when adding dead link tags? -- GreenC 22:22, 10 November 2016 (UTC)

There is no general solution. Templates with type restrictions on some parameters is an issue which also affects other templates than infoboxes and other additions than {{dead link}}, e.g. trying to add a reference to a parameter which can only hold a number because calculations are performed on the value. Affected templates can add additional parameters for other types of content but this requires extra coding, and users of the template must know to use the other parameters. PrimeHunter (talk) 23:16, 10 November 2016 (UTC)

In mobile view: title less prominent than above text?

See Template:Infobox#Examples. First example has

|title        = Test Infobox
|above        = Above text

I notice that in mobile view, the title text is both smaller that the above text, and is left-aligned. This seems counter-intuitive, since the title should have more prominence, and be presented centered as a title. Any background for this? -DePiep (talk) 09:44, 6 December 2016 (UTC)

This was also brought up about ten months ago. See this discussion, which did not go anywhere. – Jonesey95 (talk) 13:58, 6 December 2016 (UTC)

Sure it did not go anywhere: "Q: This title does not work as expected" - "A: But something else does". -DePiep (talk) 14:24, 6 December 2016 (UTC)

PrimeHunter can you expand a bit? Is it a bug, or some design feature? -DePiep (talk) 14:26, 6 December 2016 (UTC)

I guess it's just a sign of less attention being paid to mobile. {{Infobox}} places title in <caption>...</caption>. I have limited CSS knowledge but think the desktop size is larger because of this in MediaWiki:Common.css:

.infobox caption {
    font-size: 125%;
    font-weight: bold;
    padding: 0.2em;
}

MediaWiki:Mobile.css doesn't have such code. I don't know what controls centering, and don't know enough CSS to edit site-wide CSS pages. PrimeHunter (talk) 14:47, 6 December 2016 (UTC)

Infoboxes – optional plural parameters – removing (s) from labels

Hi all, I've started a discussion at WP:VPR#Infoboxes – optional plural parameters – removing (s) from labels about the possibility of removing "(s)" from the end of labels, and would appreciate your thoughts there! ‑‑Yodin^T 20:30, 29 December 2016 (UTC)

overimage, overcaption, overimagerowclass and header/label/data(n)style

Could we add these new parameters into Module:Infobox?

• overimage: the image to display at the top of the template, between above and subheaders (differ from image(n), those are at the bottom of subheaders).
• overcaption: Text to put underneath the overimage.
• overimagerowclass: This parameter is inserted into the class attribute for the infobox's overimage cell.
• header(n)style: Individual header styles.
• label(n)style: Individual label styles.
• data(n)style: Individual data styles.

I've added a new version to the sandbox, and also added some test cases at Template:Infobox/testcases#Overimage / overcaption, Template:Infobox/testcases#Individual header/label/data styles. Thanks. --Dabao qian (talk) 07:36, 24 December 2016 (UTC)

Can you describe the need for overimage? What usage advice would come with it? -DePiep (talk) 09:51, 6 January 2017 (UTC)

Stray elements from embedded infobox

Hi! When I exported the template:infobox page from here to my wiki, I've noticed something rather strange happen, I noticed that stray <td>, <tr> and <th> elements would appear in articles that used embedded infoboxes, and I'm not sure why. Image example of this happening: One example . Another Example I've tried deleting and reimporting the Template:Infobox, but that doesn't appear to solve anything. I've also changed my theme from DarkVector to the vanilla Vector, and it doesn't fix anything either. Any advice on how to get rid of them? Running Mediawiki 1.27.1

Edit: I noticed that only the |child element would cause this, and not the |embed element. I'm still unsure how to fix this.

Edit2: Wow, I'm an idiot, I forgot to enable $wgUseTidy. I guess this problem is solved now.

MalevolentArcana (talk) 06:37, 24 January 2017 (UTC)

Adding previous/next params

So I've been doing a number of Infobox conversions (i.e. converting templates to use {{Infobox}} as a base). One thing I've noticed is that there is very little consistency with how previous/next links are displayed at the bottom of infobox. Some user →/←, some use </> etc. Could we explore adding adding a previous and a next param to the base infobox so that rather then having to feed a big cluster into {{{param}}}, we could feed stuff into {{{previous}}}/{{{next}}}? --Zackmann08 (^{Talk to me}/_{What I been doing}) 03:49, 6 January 2017 (UTC)

I'm not sure why this required an RfC instead of a regular discussion. Have you attempted at doing so in the template's sandbox, and do you have an example of this to provide? Alex|The|Whovian^? 04:38, 6 January 2017 (UTC)

Looks like a styling issue, not exactly an infobox issue. Make a {{prev-next}} metatemplate that would fit in infoboxes, successionboxes, and more? {{navbar}}, {{key press}}, {{button}} come to mind. -DePiep (talk) 12:36, 6 January 2017 (UTC)

That sounds like a good idea to me. Enterprisey (talk!) —Preceding undated comment added 05:43, 9 January 2017 (UTC)

@AlexTheWhovian: I totally would but I am clueless when it comes to writing code for Modules. @DePiep: I like that idea! That is what I'm going to run with. --Zackmann08 (^{Talk to me}/_{What I been doing}) 18:55, 17 January 2017 (UTC)

Maybe a module is not required, but css settings are ;-) I can not spend too much time on sandboxing btw. -DePiep (talk) 19:07, 17 January 2017 (UTC)

Yes please add a "next" and "previous" parameters in the infobox. I was checking the recent Miss Universe 2016 and it is extremely frustrating that it isn't included especially when one needs to manually make changes to the URL or venture to the bottom page to see a collapsed template just to get to the previous year. This feature should not be exclusive for sports team. I am just wondering if there is a good reason as to why it was never included, as I am sure there might be but I agree that this should be discussed further. Savvyjack23 (talk) 16:18, 30 January 2017 (UTC)

I'm not sure how relevant this is, but with regards to Template:Infobox film the feeling at WT:FILM was that "Next" and "Previous" were more trouble than they were worth, as they led to a number of contentious discussions with regards to the "proper" order of prequels/sequels/etc. Would adding this functionality here allow editors to start using it there? If so, I think that would resurrect a problem that we'd managed to happily bury. DonIago (talk) 19:52, 2 February 2017 (UTC)

I don't think this will happen. (This is rousing interest in these discussions at Film though). -DePiep (talk) 23:53, 2 February 2017 (UTC)

@AlexTheWhovian, DePiep, Enterprisey, Savvyjack23, and Doniago: Can I get some of the interested parties to take a look at User:Zackmann08/Prev-next and leave some comments? I want to get some additional input before I generate a working template. I want to make sure this isn't a one man show, plowing ahead with what I think should be law... Really want a community effort and consensus. I'm happy to do the grunt work of creating the template! Just want community input on the layout. --Zackmann08 (^{Talk to me}/_{What I been doing}) 18:27, 3 February 2017 (UTC)

Personally, Style 2 is laid out much better, since Style 1 is pretty asymmetric. Enterprisey (talk!) 19:14, 3 February 2017 (UTC)

So... Funny story... Frietjes beat me to the punch here and created Template:Succession links which I think is perfect. :-) --Zackmann08 (^{Talk to me}/_{What I been doing}) 20:18, 3 February 2017 (UTC)

Protected edit request on 9 February 2017

Could you please let me copy the code of this infobox template because I really need it for a project I have in school. I am a student from Albania and I study at Epoka University. I have an assignment to create a wiki page and I really need this infobox template. 79.106.109.152 (talk) 19:41, 9 February 2017 (UTC)

Just click https://en.wikipedia.org/w/index.php?title=Template:Infobox&action=edit. Jo-Jo Eumerus (talk, contributions) 21:11, 9 February 2017 (UTC)

Template-protected edit request on 17 February 2017

I would like a copy of the Infobox template. I am creating a private wiki, and the steps to import the Template:Infobox do not seem to be working for me. CSchrieb (talk) 00:04, 17 February 2017 (UTC)

Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format. GeoffreyT2000 (talk, contribs) 01:41, 17 February 2017 (UTC)

Show/Hide subboxes

Main 1
Main 2
Sub 3-1 Sub 3-2 Label 3-3 Data 3-3
Label 4-1 Data 4-1
Label 5	Data 5
Main 6

Is it possible to show/hide subboxes? LA (T) @ 03:14, 20 February 2017 (UTC)

Do you mean like at Frank Sinatra or Canada -Moxy (talk) 03:45, 20 February 2017 (UTC)

I think they mean like sections of infoboxes. I've seen this, but I can't think of an example ... Curly "JFC" Turkey 🍁 ¡gobble! 03:47, 20 February 2017 (UTC)

I am talking about Template:Infobox#Subboxes where a show/hide link is by the subox's first header. LA (T) @ 14:37, 20 February 2017 (UTC)

User:Lady Aleena, example with subboxes posted above. the show/hide will occupy the first table header and everything within that subbox will be collapsed. Frietjes (talk) 14:50, 20 February 2017 (UTC)

Thank you Frietjes. Have a nice day! LA (T) @ 14:59, 20 February 2017 (UTC)

Canada |ethnic_groups = {{Collapsible list .--Moxy (talk) 04:48, 20 February 2017 (UTC)

Sub boxes and the usage of the infobox class

Hi, I've become aware that subboxes emit the infobox class. This seems incorrect to me. Is there a specific reason to do so ? —TheDJ (talk • contribs) 21:05, 27 February 2017 (UTC)

I can't think of any reason why it would be needed. Frietjes (talk) 22:25, 27 February 2017 (UTC)

Subboxes

Main 1
Main 2
Sub 3-1 Sub 3-2 Label 3-3 Data 3-3
Label 5	Data 5
Main 6

foo

coloured row

Is it possible to have a subbox with the header width the same as a regular infobox header? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 15:41, 23 March 2017 (UTC)

Jc86035, you might have some luck if you increase the width of the subboxes. Frietjes (talk) 19:44, 23 March 2017 (UTC)

if that doesn't work, you could try increasing the magnitude of the negative margins for the subbox (e.g., margin:-4px). Frietjes (talk) 19:45, 23 March 2017 (UTC)

@Frietjes: The problem is that this would need to scale with differing widths for {{Infobox station}} and {{Infobox rail line}}, due to differing image and route diagram widths (and the infobox getting wider when the route diagrams are uncollapsed). I've tried faking the header (in preview) using divs with extra borders to the left and right, but it's problematic because of the minimum two necessary divs so that the text stays in the centre with the [show/hide] button and the height being different in mobile and desktop due to table padding. Do you think a structure with NavFrames would work better? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 05:19, 24 March 2017 (UTC)

Jc86035, you could try adding a width that's over 100%, but I don't know how different browsers would react, or what would happen if the box gets stretched more than usual. as far as I can tell, the problem is that the enclosing data table cell is adding padding, and the subbox is removing the padding using a negative margin. but, the '100%' for the width for the subbox is calculated without the padding. you will definitely have better luck using tables for collapsed content vs. divs since the infobox is a table. if you want to give me some concrete examples in a sandbox, I can work on it. Frietjes (talk) 13:22, 24 March 2017 (UTC)

@Frietjes: Never mind. It seems it's easier to just inject padding:0 into the infobox using Module:String [2].

Do you think it would be a good idea to allow styling for individual parameters (e.g. |data42style=) in Module:Infobox, or is it not worth adding? Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 14:18, 24 March 2017 (UTC)

Jc86035, could be useful. we have resisted some per-cell styling to reduce the number of rainbow coloured infoboxes, but there are definitely cases like this one where the subbox really wants to be in a zero-padded cell. one compromise could be to have an option to turn off the padding for a data cell, but a more generic |datastyleX= would be useful for other situations. for {{infobox3cols}} we have |rowcellstyleX= which allows you to style all the table cells in a row. so, if there is only one cell (e.g., data without labels) you get what you want. so, we could import that feature here which would have the advantage of keeping the syntax the same between the two templates. Frietjes (talk) 14:28, 24 March 2017 (UTC)

your Module:String looks fragile, and may break for very large route diagrams ... Frietjes (talk) 14:30, 24 March 2017 (UTC)

@Frietjes: sounds like a good idea. I've added a spade to the function (for now) so that it doesn't accidentally modify something else. I don't think anyone is going to try to include East Coast Main Line diagram in the infobox, although that does stop the infobox from rendering. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 14:37, 24 March 2017 (UTC)

Jc86035, okay, I have made a proposal below, will see if there are any objections/issues. Frietjes (talk) 17:59, 24 March 2017 (UTC)

Adding rowcellstyle

per the thread above, are there any objections to this change? it adds an optional |rowcellstyleX= parameter which allows you to pass CSS for styling the cells in that row. this style applies to both the labels and the data fields, and follows the same syntax used in module:infobox3cols. this will allow us to use |rowcellstyleX=padding:0 for rows containing subboxes so we don't need to use the negative margin trick for the subbox. let me know if you see any problems with the proposed addition. thank you. Frietjes (talk) 15:57, 24 March 2017 (UTC)

@Frietjes: probably safe to merge, given there are 212 editors who watch this page and it's a relatively minor change. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 05:18, 4 April 2017 (UTC)

Jc86035, okay, done. Frietjes (talk) 05:39, 4 April 2017 (UTC)

MOS

Is there any MOS for infoboxes? Should we have one? I guess spaces and capitals in defining params in infoboxes should be done away with. I would like to invite comments from others on this. -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 06:23, 21 April 2017 (UTC)

@Capankajsmilyo: Wikipedia:Manual of Style/Infoboxes. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 12:00, 21 April 2017 (UTC)

Thanks -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 04:45, 28 April 2017 (UTC)

Align subbox header

How to center subbox header? Example is Frank Sinatra. Show/hide takes space on the right and pushes title to the left; if we use margin-left:1em or something like that, then in mobile view (where collapsible things are uncollapsed and show/hide buttons removed) title goes from center 1em to the right in this case.

I mean to make it like it is in {{Infobox station}}, so that header text does not jump left-right when clicking show/hide (this could be done in Module:Navbar or collapsible class to fix all show/hide instances: center them, and stop them moving left-right).--Obsuser (talk) 13:45, 8 May 2017 (UTC)

@Obsuser: Fixed in {{Collapsed infobox section begin}}. A div with a left/right margin is required for the show/hide text not to be calculated in the header centring (I don't think this could be fixed easily with a CSS class). Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 15:13, 8 May 2017 (UTC)

Thank you.

BTW, how to center "Transport for London rail lines" content in https://en.m.wikipedia.org/wiki/Waterloo_%26_City_line? Sometimes div style centering and margin:0 auto is not working for files, some tables or complicated content; how to force floating in the center?

Also, I've noticed extra vertical space above first header in https://en.m.wikipedia.org/wiki/Frank_Sinatra. /I see it on PC, Win7, Chrome./

And {{Collapsed infobox section begin}} does not work in its /doc example if image caption is not defined, don't know why.--Obsuser (talk) 15:56, 8 May 2017 (UTC)

@Obsuser: {{London metro lines}} was fixed by Frietjes (by add min-width:100% to override mobile CSS). In some places there just isn't any margin/text-align CSS because the maximized width negates the need for it. Could you give any other examples of where it's not working? I don't think there's an easy solution for the extra vertical space without playing with the mobile CSS (since any formatting could also unintentionally affect the desktop layout).

If the |image_caption= text were to be deleted then the table code inserted by {{Collapsed infobox section begin}} would have been treated as part of |image= and wouldn't have displayed properly. I don't think this is a problem since there's almost always a caption parameter in infoboxes. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 06:37, 9 May 2017 (UTC)

Position of the infobox in mobile version of Wikipedia

I have noticed for two days now that the infobox appears after the first paragraph of the leading section of any article. This affects all the articles I have gone through in this period; from Television season articles, television series articles, a persons article etc. Isn't the infobox supposed to be at the beginning of the in the mobile version of Wikipedia articles? Please, someone help fix this. Nyanchoka : talk 2 me 18:06, 25 May 2017 (UTC)

User:Nyanchoka, please see the thread at VPT. Frietjes (talk) 18:51, 25 May 2017 (UTC)

Module:Infobox/sandbox

At WT:Lua I was invited to comment on Module:Infobox/sandbox. All I can manage at the moment is to examine the changes from the main module and comment on any peculiarities—the logic of what the changes achieve is a blur that I can't take time to examine. I am moderately sure the new code is robust and will do what is expected and I only have trivia to report. My first point is that it is best to retain the existing style of a module (unless that style is horrendous). For example, change the first of these to the second:

    for i=2,#s do
    for i = 2, #s do

It would be nice if the first edit to the main module (without any other changes) was to change all the spaces used for indents to tabs per current conventions, but that is not needed.

I have been using %S (matches non-whitespace) for a while and this tweak could be made:

local function notempty( s ) return s and s:match( '^%s*(.-)%s*$' ) ~= '' end
local function notempty( s ) return s and s:match( '%S' ) end

I guess there is a reason marker is used twice in the following. Please don't explain as I can't digest it now but I thought I would mention anything I noticed.

    return marker .. tostring(root) .. marker

Johnuniq (talk) 05:44, 28 May 2017 (UTC)

Johnuniq, thank you for the comments. I have made some changes to partially address your suggestions. I avoided changing any spaces to tabs in any places that would increase the diff. The double markers are intentional so that we can split into a table and assume that (a) all the even items are child infoboxes, and (b) all the odd items are not child infoboxes. the sandbox2 version does something less complicated. Frietjes (talk) 16:05, 28 May 2017 (UTC)

Flag icons in infoboxes

Re: "Avoid flag icons." (WP:INFOBOXUSE) and "Flag icons should not be used in infoboxes" (WP:INFOBOXFLAG), I am considering removing flag items from a large number of infoboxes such as Notre-Dame de Paris, United States Navy SEALs, and Iberian Peninsula. Are there any other guidelines, policies or RfCs I should be aware of that might guide me as to pages that are exceptions? --Guy Macon (talk) 09:39, 30 June 2017 (UTC)

@Guy Macon: Given that there are a very large number of {{Infobox settlement}} transclusions (likely as many as a hundred thousand) which contain national flags, it could be better to change the policy to reflect actual practice. I'm not sure, though. Jc86035 (talk) Use {{re|Jc86035}}
to reply to me 10:08, 30 June 2017 (UTC)

Jc86035, I think I would partially agree with you. I don't think the flags add anything to Notre-Dame or the SEALs but where there is a list in the infobox such as the Iberian Peninsular they visually break up the box into its components. Guy, perhaps you need to start an RfC running on WT:MOSINFOBOX? Martin of Sheffield (talk) 10:27, 30 June 2017 (UTC)

Wikipedia talk:Manual of Style/Infoboxes#Pre-RfC: Flag icons in infoboxes. --Guy Macon (talk) 15:45, 30 June 2017 (UTC)

RfC: Allow private schools to be characterized as secular as well as religious?

This RfC, which directly concerns and affects {{Infobox school}} which is a child of this a template, is here: Wikipedia:Village pump (policy)/Archive 136#RfC: Allow private schools to be characterized as non-affiliated as well as religious, in infobox?. Herostratus (talk) 18:52, 25 June 2017 (UTC)

The above RfC is an attempt is being made to overturn two infobox RfCs, one from less than six months ago and another from a year ago.

Specifically, this new RfC asks that "religion = none" be allowed in the infobox.

The first RfC that this new RfC is trying to overturn is:

• 15 June 2015 RfC: RfC: Religion infobox entries for individuals that have no religion.

The result of that RfC was "unambiguously in favour of omitting the parameter altogether for 'none' " and additionally found that "There's no obvious reason why this would not apply to historical or fictional characters, institutions etc.", and that nonreligions listed in the religion entry should be removed when found "in any article".

The second RfC that this new RfC is trying to overturn is:

• 31 December 2015 RfC: RfC: Religion in infoboxes.

The result of that RfC was that the "in all Wikipedia articles, without exception, nonreligions should not be listed in the Religion= parameter of the infobox.".

--Guy Macon (talk) 06:35, 26 June 2017 (UTC)

The above-mentioned RfC has been snow closed. At 8 Yes, 48 No, the Wikipedia community has decided, once again, that without exception, nonreligions should not be listed in the 'Religion=' parameter of the infobox on any article anywhere on Wikipedia. --Guy Macon (talk) 15:49, 30 June 2017 (UTC)

Former Names and Former Administrative Divisions

For a lot of cities/towns in Europe, like Danzig or Straßburg, they've belonged to a number of countries over the years. Can we add a 'former name' and 'former administrative divisions' section as an optional section? So, for example, Suckow an der Ihna, now Żukowo would show something like:

Żukowo Former Name: Suckow an der Ihna Former Country: German Empire (1871-1945)

• Member State: Prussia
  • Province: Pomerania
    • Regierungsbezirk: Stettin
      • Kreis: Saatzig

(stars representing intented)

--James (talk) 12:10, 6 July 2017 (UTC)

@James: Maybe you meant to post your question on Template talk:Infobox settlement? --Izno (talk) 12:27, 6 July 2017 (UTC)

Improvement

Is it possible to add code for tracking category with pages containing various Infoboxes with unknown parameters to this template itself, rather than to each infobox separately? -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 19:54, 25 August 2017 (UTC)