![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 10 | ← | Archive 12 | Archive 13 | Archive 14 | Archive 15 | Archive 16 | → | Archive 19 |
I'm proposing to standardise the map parameter names in infoboxes; please see, and comment at, Wikipedia:Village pump (technical)#Standardising map parameters in infoboxes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:09, 28 August 2017 (UTC)
I want to add a labeltext, but cannot reach that through regular |label10=...
input. Is there a correct way to create it semantically correct (instead of just bolding it)?
Issue at hand: see {{
Infobox hydrogen}}, ~halfway there is
Spectral lines + an image (through
this subtemplate). I want the label "Spectral lines" to appear as a caption. Suggestions? (Creating an extra row with idle |data10=
is not ideal). -
DePiep (
talk)
11:25, 28 September 2017 (UTC)
I see redlinked Module:Infobox/i18n pop up in articles (42.000 transclusions). Is this by design (future deployment)? Anything I could learn? Of course, " i18n" stands for internationalisation. - DePiep ( talk) 20:50, 19 October 2017 (UTC)
/i18n
submodule. If it exists, its table replaces the enwiki i18n table that is in Module:Wikidata (actually, it is merged, so where specified, /i18n
values replace the corresponding English values). There are two really puzzling aspects of the code that I don't want to spend hours analyzing so I'll just mention them. First, Module:Wikidata refers to the global variable ...
and (if set) that variable is used to specify the title used for the subpage (if the title were "Module:Example", the subpage would be "Module:Example/i18n"). However, ...
is always nil in a module (I think) so the test is redundant. If running Lua on some other system (not a Scribunto module), the global variable ...
would be nil or a table of command-line arguments passed to the Lua script. If someone wants that for an off-wiki test system, better methods are available. Second, I'm pretty sure the code would not work because it is in a separate module (Module:I18n) and its attempts to set the i18n
table would not affect Module:Wikidata which would continue using the English values. Does anyone know of a place where the system has been tested?
Johnuniq (
talk)
03:27, 20 October 2017 (UTC)
I believe that there is a bug or incompatibility between the Monobook skin and the Infobox template. When I use Monobook, it messes up Template:Infobox. When I switch to another skin, the issue disappears.
— goethean 19:58, 22 November 2017 (UTC)
Would it be possible to add support for {{ url}} to those infoboxes that don't yet have it? I came across {{ Infobox stage production}}, which doesn't support it, and couldn't find any way to make it display without the initial "http" – which as I understand it should not appear in the website field of an infobox. It's kind of confusing to do stuff that works in many situations, and then find that it doesn't work in other, similar, cases. Consistency, anyone? Justlettersandnumbers ( talk) 21:38, 9 January 2018 (UTC)
|website=www.example.com
would give consistent results. {{
Url}} even copes with |website=
https://www.example.com
, but any such implementation would currently barf at |website={{
official site|www.example.com}}
. The
Module:Url could be modified to look for a url anywhere inside whatever is used as the value for |website=
, but I think it better to require at least a minimum standard of discipline from editors in how they supply values to infoboxes in articles.I have removed the infobox class when |subbox=yes
to help with the rendering on mobile. as far as I can tell, the class isn't needed when the box is a subbox since the class is set by the outer box. but, please let me know if this causes a problem.
Frietjes (
talk)
22:41, 24 January 2018 (UTC)
Could someone code something (I would, but don't know the first thing about LUA) that would make infoboxes automatically populate Category:Infobox templates?
In wikicode, that would be something like
{{#ifeq:{{str left|{{#titleparts:{{NAMESPACE}}:{{SUBPAGENAME}}|1}}|16}}|Template:Infobox|[[Category:Infobox templates]]}}
{{NAMESPACE}} would guarantee we're in the correct namespace, while {{SUBPAGENAME}} would guarantee we're not on a sandbox/doc page.
Headbomb { t · c · p · b} 01:54, 10 February 2018 (UTC)
- DePiep ( talk) 13:56, 10 February 2018 (UTC)
I've edited Template:Infobox element to make use of the /sandbox, and it works flawlessly. See Category:Infobox templates. And as a bonus, things sort nicely, and we get rid of the lot of the /sandbox /doc crap that clutters the category. Many hard-coded instances could be removed from the documentation pages. Headbomb { t · c · p · b} 14:05, 10 February 2018 (UTC)
I'm confused here. We're still on the building ideas/testing phase. No one's raised any objections yet, so I'm not sure where you claim there's "no consensus". As for {{ template other}}, that would not filter out /doc and /sandbox subpages. I'm also not sure what you mean by "Diffusion in the category is broken." AFAICT with my limited testing, it works exactly as intended. The infobox gets categorized, nothing else does. Lastly, PETSCAN would be useless, as the vast majority of infoboxes aren't categorized. Headbomb { t · c · p · b} 18:21, 10 February 2018 (UTC)
I've edited [[Template:Infobox element]]
note above (looked like going all live to me - sad face here). I'm sorry.See Wikipedia:Village pump (proposals)#RFC: Autopopulate Category:Infobox templates when we can. Headbomb { t · c · p · b} 12:45, 21 February 2018 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Given the lack of any solid reason against this, I say it's time to deploy. The edit protected request is simply to copy the sandbox version into the live version. The changes have been tested, and work.
Possible improvements to efficiency may possibly be done through LUA, but this is not something that would noticeably slow down pages as is. Headbomb { t · c · p · b} 21:18, 13 February 2018 (UTC)
class=infobox
qualify too).Please allow me to make a restart to make this fly. The two threads above introduce multiple issues and principles the earlier proposed sandbox change, possibly blocking an improvement unneccicarily. Therefor I take this approach: Let us first describe the intended Category. IMO once we have consensus on this, the "how-to" (populate the category) can be solved more gently.
Headbomb proposed automated population of Category:Infobox templates [1]. However, it appears that "automated" can not be achieved without causing issues. I understand the request to be along this line: "Make the category complete, and do automatically so".
1. Create new Category:Wikipedia infobox templates. It contains all infobox templates that appear in mainspace in its top level.
2. Populations rules are:
class=infobox
Current Category:Infobox templates has 15 (1-deep) subcategories, intended for WP:DIFFUSE ("Put a template in the most detailed subcategory/ies"). Would we add all infobox templates to the top category, the principle of diffusion would be broken. It would be a two-principled setup, wrong because of conflicting definitions. OTOH, simply re-defining the existing category, and removing all subcategories, would be breaking current usage and expectancies. Maybe a even a full WP:CfD would be required.
Also, the new requirement of completeness is hard to achieve when its original approach is still in place. What we need is a setup that guarantees that the category has all, and nothing more.
So I strongly propose to leave current category as it is, and create this new category.
1. Create new Category:Wikipedia infobox templates. It contains all infobox templates that appear in mainspace in its top level.
2. Populations rules are:
class=infobox
Indications:
Number of infoboxes transclused on enwiki: 3M.
Number of templates that invoke Module:Infobox: 2560 (per Johnuniq).
Number of templates that invoke Module:Infobox: 1208 (per this PETSCAN).
Number of templates in Category:Infobox templates (3-deep): 13640 PETSCAN (slow). This is huge also because of category tree effects (Example: Template:PBB/2239).
Once we agree on what to include and why, the how can follow.
Also, proposal improvements appreciated. - DePiep ( talk) 21:09, 15 February 2018 (UTC)
There's no Infobox templates ...: Misunderstanding. The prefix "Wikipedia" does not specify the templates, as you seem to read it. It is a prefix that distinguishes administrative pages from content pages.
for sake of tradition: no, extreme interpretation you are making here. Current structure is well established, contains extra information, and numerous (unknown) users & approaches can rely on it.
so lets do that- Again, let's do what? This is skipping over my main point: the category has not been redefined, so filling it with "that" is working backwards.
no issues- Yes there are, and I have pointed them out. These also include inconsistencies wrt conflating category definitions. (by claiming that
no one is proposing to remove any subcategories, you show that you did miss these contradictions, up to the point of even maintaining them in the future).
no reason to exclude- well, I did describe a reason (you did not care to refer to), and also I note that I exactly raised it as a question for consideration. Another example of blaming me for your bad reading?
Today, the 120 chemical element articles have a fine infobox that includes an "isotopes" table (e.g. uranium). Over at WikiProject talk:Elements I propose to break that table out into a new, separate infobox. That new infobox will be added into a section of the article. And also: the new infobox will be freshly added to the article isotopes of uranium.
Main question: Is it OK to use a straight infobox in an article section? What information, semantics, MOS, guidelines to keep in mind? (note: ideas are welcome, consensus forum is WT:ELEM). - DePiep ( talk) 18:56, 7 January 2017 (UTC)
Hello, Iam new and working on Wp/sat(incubator). I have read the template tutorials from wikipedia but when am using that template code, it doesn't shows like template. It displaying only the template title (e.g. Template:xxxx). So please help me how make infobox template like others page.
Thanks, Ramjit User:Ramjit Tudu 14:46, 4 September 2017 (UTC)
Per Wikipedia:Village pump (proposals)/Archive 145#!Vote (Infobox categorization), copy the sandbox version into the live version. The changes have been tested, and work. Headbomb { t · c · p · b} 00:58, 12 March 2018 (UTC)
template-editor
rights to edit, so, since you're a Template editor, you already have the rights to deploy the version in the sandbox. —
RP88 (
talk)
02:44, 12 March 2018 (UTC)
Hello, would it be possible to integrate Module:Check for unknown parameters to Module:Infobox itself. That would be great upgrade in my opinion. Capankajsmilyo ( talk) 19:12, 11 April 2018 (UTC)
When I try to test the settlement infobox sandbox in my own user sandbox, I get "Lua error in Module:Infobox/sandbox at line 206: attempt to index global 'dataCell' (a nil value)." I'ld rather not try and fix this myself, so perhaps someone with more lua knowledge can take a look? Fram ( talk) 11:33, 13 April 2018 (UTC)
See Template:Infobox settlement/testcases, which has the same error. The problem is not restricted to (my) user space but is more general. Fram ( talk) 11:41, 13 April 2018 (UTC)
{{infobox/sandbox}}
to {{infobox}}
.
Frietjes (
talk)
13:29, 13 April 2018 (UTC)
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 10 | ← | Archive 12 | Archive 13 | Archive 14 | Archive 15 | Archive 16 | → | Archive 19 |
I'm proposing to standardise the map parameter names in infoboxes; please see, and comment at, Wikipedia:Village pump (technical)#Standardising map parameters in infoboxes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:09, 28 August 2017 (UTC)
I want to add a labeltext, but cannot reach that through regular |label10=...
input. Is there a correct way to create it semantically correct (instead of just bolding it)?
Issue at hand: see {{
Infobox hydrogen}}, ~halfway there is
Spectral lines + an image (through
this subtemplate). I want the label "Spectral lines" to appear as a caption. Suggestions? (Creating an extra row with idle |data10=
is not ideal). -
DePiep (
talk)
11:25, 28 September 2017 (UTC)
I see redlinked Module:Infobox/i18n pop up in articles (42.000 transclusions). Is this by design (future deployment)? Anything I could learn? Of course, " i18n" stands for internationalisation. - DePiep ( talk) 20:50, 19 October 2017 (UTC)
/i18n
submodule. If it exists, its table replaces the enwiki i18n table that is in Module:Wikidata (actually, it is merged, so where specified, /i18n
values replace the corresponding English values). There are two really puzzling aspects of the code that I don't want to spend hours analyzing so I'll just mention them. First, Module:Wikidata refers to the global variable ...
and (if set) that variable is used to specify the title used for the subpage (if the title were "Module:Example", the subpage would be "Module:Example/i18n"). However, ...
is always nil in a module (I think) so the test is redundant. If running Lua on some other system (not a Scribunto module), the global variable ...
would be nil or a table of command-line arguments passed to the Lua script. If someone wants that for an off-wiki test system, better methods are available. Second, I'm pretty sure the code would not work because it is in a separate module (Module:I18n) and its attempts to set the i18n
table would not affect Module:Wikidata which would continue using the English values. Does anyone know of a place where the system has been tested?
Johnuniq (
talk)
03:27, 20 October 2017 (UTC)
I believe that there is a bug or incompatibility between the Monobook skin and the Infobox template. When I use Monobook, it messes up Template:Infobox. When I switch to another skin, the issue disappears.
— goethean 19:58, 22 November 2017 (UTC)
Would it be possible to add support for {{ url}} to those infoboxes that don't yet have it? I came across {{ Infobox stage production}}, which doesn't support it, and couldn't find any way to make it display without the initial "http" – which as I understand it should not appear in the website field of an infobox. It's kind of confusing to do stuff that works in many situations, and then find that it doesn't work in other, similar, cases. Consistency, anyone? Justlettersandnumbers ( talk) 21:38, 9 January 2018 (UTC)
|website=www.example.com
would give consistent results. {{
Url}} even copes with |website=
https://www.example.com
, but any such implementation would currently barf at |website={{
official site|www.example.com}}
. The
Module:Url could be modified to look for a url anywhere inside whatever is used as the value for |website=
, but I think it better to require at least a minimum standard of discipline from editors in how they supply values to infoboxes in articles.I have removed the infobox class when |subbox=yes
to help with the rendering on mobile. as far as I can tell, the class isn't needed when the box is a subbox since the class is set by the outer box. but, please let me know if this causes a problem.
Frietjes (
talk)
22:41, 24 January 2018 (UTC)
Could someone code something (I would, but don't know the first thing about LUA) that would make infoboxes automatically populate Category:Infobox templates?
In wikicode, that would be something like
{{#ifeq:{{str left|{{#titleparts:{{NAMESPACE}}:{{SUBPAGENAME}}|1}}|16}}|Template:Infobox|[[Category:Infobox templates]]}}
{{NAMESPACE}} would guarantee we're in the correct namespace, while {{SUBPAGENAME}} would guarantee we're not on a sandbox/doc page.
Headbomb { t · c · p · b} 01:54, 10 February 2018 (UTC)
- DePiep ( talk) 13:56, 10 February 2018 (UTC)
I've edited Template:Infobox element to make use of the /sandbox, and it works flawlessly. See Category:Infobox templates. And as a bonus, things sort nicely, and we get rid of the lot of the /sandbox /doc crap that clutters the category. Many hard-coded instances could be removed from the documentation pages. Headbomb { t · c · p · b} 14:05, 10 February 2018 (UTC)
I'm confused here. We're still on the building ideas/testing phase. No one's raised any objections yet, so I'm not sure where you claim there's "no consensus". As for {{ template other}}, that would not filter out /doc and /sandbox subpages. I'm also not sure what you mean by "Diffusion in the category is broken." AFAICT with my limited testing, it works exactly as intended. The infobox gets categorized, nothing else does. Lastly, PETSCAN would be useless, as the vast majority of infoboxes aren't categorized. Headbomb { t · c · p · b} 18:21, 10 February 2018 (UTC)
I've edited [[Template:Infobox element]]
note above (looked like going all live to me - sad face here). I'm sorry.See Wikipedia:Village pump (proposals)#RFC: Autopopulate Category:Infobox templates when we can. Headbomb { t · c · p · b} 12:45, 21 February 2018 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Given the lack of any solid reason against this, I say it's time to deploy. The edit protected request is simply to copy the sandbox version into the live version. The changes have been tested, and work.
Possible improvements to efficiency may possibly be done through LUA, but this is not something that would noticeably slow down pages as is. Headbomb { t · c · p · b} 21:18, 13 February 2018 (UTC)
class=infobox
qualify too).Please allow me to make a restart to make this fly. The two threads above introduce multiple issues and principles the earlier proposed sandbox change, possibly blocking an improvement unneccicarily. Therefor I take this approach: Let us first describe the intended Category. IMO once we have consensus on this, the "how-to" (populate the category) can be solved more gently.
Headbomb proposed automated population of Category:Infobox templates [1]. However, it appears that "automated" can not be achieved without causing issues. I understand the request to be along this line: "Make the category complete, and do automatically so".
1. Create new Category:Wikipedia infobox templates. It contains all infobox templates that appear in mainspace in its top level.
2. Populations rules are:
class=infobox
Current Category:Infobox templates has 15 (1-deep) subcategories, intended for WP:DIFFUSE ("Put a template in the most detailed subcategory/ies"). Would we add all infobox templates to the top category, the principle of diffusion would be broken. It would be a two-principled setup, wrong because of conflicting definitions. OTOH, simply re-defining the existing category, and removing all subcategories, would be breaking current usage and expectancies. Maybe a even a full WP:CfD would be required.
Also, the new requirement of completeness is hard to achieve when its original approach is still in place. What we need is a setup that guarantees that the category has all, and nothing more.
So I strongly propose to leave current category as it is, and create this new category.
1. Create new Category:Wikipedia infobox templates. It contains all infobox templates that appear in mainspace in its top level.
2. Populations rules are:
class=infobox
Indications:
Number of infoboxes transclused on enwiki: 3M.
Number of templates that invoke Module:Infobox: 2560 (per Johnuniq).
Number of templates that invoke Module:Infobox: 1208 (per this PETSCAN).
Number of templates in Category:Infobox templates (3-deep): 13640 PETSCAN (slow). This is huge also because of category tree effects (Example: Template:PBB/2239).
Once we agree on what to include and why, the how can follow.
Also, proposal improvements appreciated. - DePiep ( talk) 21:09, 15 February 2018 (UTC)
There's no Infobox templates ...: Misunderstanding. The prefix "Wikipedia" does not specify the templates, as you seem to read it. It is a prefix that distinguishes administrative pages from content pages.
for sake of tradition: no, extreme interpretation you are making here. Current structure is well established, contains extra information, and numerous (unknown) users & approaches can rely on it.
so lets do that- Again, let's do what? This is skipping over my main point: the category has not been redefined, so filling it with "that" is working backwards.
no issues- Yes there are, and I have pointed them out. These also include inconsistencies wrt conflating category definitions. (by claiming that
no one is proposing to remove any subcategories, you show that you did miss these contradictions, up to the point of even maintaining them in the future).
no reason to exclude- well, I did describe a reason (you did not care to refer to), and also I note that I exactly raised it as a question for consideration. Another example of blaming me for your bad reading?
Today, the 120 chemical element articles have a fine infobox that includes an "isotopes" table (e.g. uranium). Over at WikiProject talk:Elements I propose to break that table out into a new, separate infobox. That new infobox will be added into a section of the article. And also: the new infobox will be freshly added to the article isotopes of uranium.
Main question: Is it OK to use a straight infobox in an article section? What information, semantics, MOS, guidelines to keep in mind? (note: ideas are welcome, consensus forum is WT:ELEM). - DePiep ( talk) 18:56, 7 January 2017 (UTC)
Hello, Iam new and working on Wp/sat(incubator). I have read the template tutorials from wikipedia but when am using that template code, it doesn't shows like template. It displaying only the template title (e.g. Template:xxxx). So please help me how make infobox template like others page.
Thanks, Ramjit User:Ramjit Tudu 14:46, 4 September 2017 (UTC)
Per Wikipedia:Village pump (proposals)/Archive 145#!Vote (Infobox categorization), copy the sandbox version into the live version. The changes have been tested, and work. Headbomb { t · c · p · b} 00:58, 12 March 2018 (UTC)
template-editor
rights to edit, so, since you're a Template editor, you already have the rights to deploy the version in the sandbox. —
RP88 (
talk)
02:44, 12 March 2018 (UTC)
Hello, would it be possible to integrate Module:Check for unknown parameters to Module:Infobox itself. That would be great upgrade in my opinion. Capankajsmilyo ( talk) 19:12, 11 April 2018 (UTC)
When I try to test the settlement infobox sandbox in my own user sandbox, I get "Lua error in Module:Infobox/sandbox at line 206: attempt to index global 'dataCell' (a nil value)." I'ld rather not try and fix this myself, so perhaps someone with more lua knowledge can take a look? Fram ( talk) 11:33, 13 April 2018 (UTC)
See Template:Infobox settlement/testcases, which has the same error. The problem is not restricted to (my) user space but is more general. Fram ( talk) 11:41, 13 April 2018 (UTC)
{{infobox/sandbox}}
to {{infobox}}
.
Frietjes (
talk)
13:29, 13 April 2018 (UTC)