Template talk:TemplateBox

From Wikimedia Commons, the free media repository
Jump to: navigation, search
Info non-talk.svg Template:TemplateBox has been protected indefinitely because it is a highly-used or visible template. Use {{Edit request}} on this page to request an edit.

Not enough for {{Ship}}[edit]

{{Ship}} has over about 32 parameters, so this template’s 30 is not enough. --AVRS (talk) 17:20, 9 April 2012 (UTC)

what the... {{Ship}} seems like a Wikipedia infobox template, not a Commons template. Rd232 (talk) 19:03, 9 April 2012 (UTC)
Please store large quantities of structured data at Wikidata. Thank you. -- Rillke(q?) 18:42, 21 June 2013 (UTC)
Now the template supports as many parameters as Lua will be able to deal with. -- Rillke(q?) 18:27, 17 August 2013 (UTC)

Category:Template documentation pages[edit]

Why are most /docs suddenly being categorised into Category:Template documentation pages (which doesn't exist) instead of Category:Template documentation (as before, which does)? I feel TemplateBox must be the reason, but I can't see how, never mind why. Rd232 (talk) 22:45, 26 July 2012 (UTC)

I guess this was responsible for the unexpected results // Template talk:Documentation#Import for en.wikipedia -- Rillke(q?) 00:07, 27 July 2012 (UTC)
Maybe, but I couldn't find any categorisation there either... Did you fix something? All the /docs are suddenly back in the old category again! Rd232 (talk) 00:17, 27 July 2012 (UTC)
Template:Documentation subpage. There was a switch in it so it was hard to find. -- Rillke(q?) 00:26, 27 July 2012 (UTC)
Well it helps if you're looking at the right template! :) Rd232 (talk) 02:22, 27 July 2012 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. Rillke(q?) 18:43, 21 June 2013 (UTC)

example (3)[edit]

{{edit request}} I suppose to add a parameter example-value, for an alternative result for the example:

== {{{msg-example|}}} ==

<nowiki>{{</nowiki>{{#if: {{{name|}}} | {{{name}}} | {{PAGENAME}} }}{{!}}{{{example}}}<nowiki>}}</nowiki>

<div style="border: 1px solid black; background-color: #ffffff; width: 90%; padding: 1.5em;">
{{{example-value|{{{{#if: {{{name|}}} | {{{name}}} | {{PAGENAME}} }}|{{{example|}}}|category=}}}}}
}}{{#if: {{{example2|}}} |<nowiki/>

So it would be possible to use examples with more than one parameter by setting example=Param1{{!}}Param2{{!}}Param3 and example-value={{Exampletemplate|Param1|Param2|Param3}}. Even named parameters would be possible (example=Whatever=value | example-value={{Exampletemplate|Whatever=value}}). -- F-scn (talk) 12:56, 25 November 2012 (UTC)

This requires editing all language subpages to forward the new parameter to the layout template, correct? -- Rillke(q?) 14:14, 27 May 2013 (UTC)
Now it's a lot easier editing all subpages. One click, and FuzzyBot the changes every language subpage. Demo at Special:Permalink/98614170. -- Rillke(q?) 18:24, 21 June 2013 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. Rillke(q?) 18:59, 21 June 2013 (UTC)

Documentation page categorized because of included example[edit]

Hi all, it seems I don't get something here: I just used {{TemplateBox}} for Template:Trimming/doc. The problem is that the documentation page is now categorized into Category:Images requiring trimming probably because of the example I included. As a result also the template {{Trimming}} itself is categorized into the same category. Am I doing something fundamentally wrong? -- Patrick87 (talk) 21:36, 6 April 2013 (UTC)

✓  Done . Yes, the inclusion of the example is triggering the autocategorisation. The solution is to prevent the autocategorisation based on the Namespace − I did that using {{iffile}}: the autocat is only applied when the template is used in the File: namespace. Jean-Fred (talk) 21:45, 6 April 2013 (UTC)
Thanks! Just one little follow-up question (since I'm alway curious to learn something new): Is this the default solution for such a problem or is there an alternative/better way to include a category that maybe prevents the problem from the start making such a workaround unnecessary? -- Patrick87 (talk) 23:02, 6 April 2013 (UTC)
You’re welcome. Yes, as far as I know, this has always been how it is done − I do not think there is any other way. <noincluide> and <includeonly> tags can only control whether the category is used on transclusions, on the page itself or both. It just happens that templates which autocategorize are used elsewhere (as category headers, to be discussed in talk pages, etc.), so filtering based on the namespace makes sense. Jean-Fred (talk) 23:38, 6 April 2013 (UTC)
Another common approach is wrapping the category in {{{category|…}}}. -- Rillke(q?) 18:00, 21 June 2013 (UTC)

new parameters[edit]

{{edit request}} Jarekt added new parameters (param. 31, 31d, … and 32, 32d, …) to the main template and English subtemplate. Please add it to the other language templates and (only 32) layout template. tacsipacsi (talk) 16:01, 7 June 2013 (UTC)

(edit conflict) I added all of them just before your request. But you could have done most of them, as most language subtemplates are not protected. --Jarekt (talk) 16:35, 7 June 2013 (UTC)

When someone does so, they can also do #example (3). -- Rillke(q?) 16:17, 7 June 2013 (UTC)

The default value for "name" should be {{BASEPAGENAME}}
And how about an additional parameter setsclass ? sarang사랑 06:45, 14 June 2013 (UTC)
What should this additional parameter exactly do? -- Rillke(q?) 17:46, 21 June 2013 (UTC)
Some templates set a CSS class. Like categories set by a template can be documented with setscats=, it might be useful to specify in a similar way the class if set by a template. sarang사랑 16:16, 28 June 2013 (UTC)
While I agree that this sounds useful, it would be also useful to document if a template sets an ID. The issue I see here is that we document details that technical-experienced users can extract their own very speedily and non-techs will not even understand why we documented them. Also, compared to categories, which are really set, there can be multiple containers/nodes in the template with different classes or even just a style and a class attribute that is reused by another template. Is it worth to document all of them? Don't we run in danger to run out of sync with the content when templates are updated? If, at all, I would label this parameter containerclass… or something better. And it should be documented for which reason this class attribute was set. A few (specific) use cases would be helpful. -- Rillke(q?) 16:57, 28 June 2013 (UTC)
After this discussion, I don't think anymore that classes should be documented as I had the idea. Compared to categories which are much more essential and noteworth, information about class[es], if thought necessary, are better to be mentioned otherwise, e.g. by usage-notes or something else. Thank you, sarang사랑 04:42, 29 June 2013 (UTC)

TemplateBox should expose TemplateData[edit]

to avoid adding redundant information and it should ensure that valid JSON is exposed. -- Rillke(q?) 20:44, 16 June 2013 (UTC)

I will start working on this very soon. Thanks to Ricordisamoa, we have Module:JSON and with LUA, the layout template will shrink a lot. It is great that we have such a structured template here at Commons. Kudos to those who set it up und who used it. -- Rillke(q?) 10:48, 9 July 2013 (UTC)

Great --Jarekt (talk) 13:49, 9 July 2013 (UTC)

Work in progress[edit]

I am currently migrating this template so it can take one of the benefits of the translate-Extension: With just one click, you can order FuzzyBot to change all language templates. This will ease further development of this template as the hassle of having to change all language templates individually will be resolved. -- Rillke(q?) 22:28, 19 June 2013 (UTC)

Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. Rillke(q?) 16:58, 28 June 2013 (UTC)

Fix [edit] link[edit]

After the changes in MediaWiki regarding section editing links, and update for this template is needed, too. Currently the [edit] link is shown above the "Documentation" heading of the TemplateBox.

The edit link has to be placed in a span next to (right of) the heading, and the class name of this span has to be changed from the old editsection to the new mw-editsection. --Patrick87 (talk) 22:59, 21 June 2013 (UTC)

✓  Done at Template:Documentation/layout. -- Rillke(q?) 23:52, 21 June 2013 (UTC)
Sorry, not completely resolved yet: Right now we have the [edit] button (which is fixed now and works as intended) but we have additionaly the (edit | history | purge) buttons. They should probably be incorporated into the span of the [edit] button (and one of the surplus edit buttons has to be deleted). Anyway, thanks for the really fast reaction! --Patrick87 (talk) 00:08, 22 June 2013 (UTC)
This is like how it was implemented before: Special:Permalink/63871702. The [2] is also an edit link. I look how one can improve it today or you just do it (it's not protected). -- Rillke(q?) 08:02, 22 June 2013 (UTC)
Sorry, it's still protected (beacause of cascading protections), so I can't fix it myself. I'd propose something like this:
<div class="template-documentation" style="margin-top:1em; clear: both; border: 2px dotted #666666; padding: 0.6em; background-color: #ECFCF4;">{{#ifeq:{{{heading|}}} | false | | <div style="padding-bottom:3px; border-bottom:1px solid #aaa; margin-bottom:1ex;"><span style="font-size:150%">{{#if: {{{heading|}}} | {{{heading}}} |[[File:Template-info.png|50px|link=|alt=Documentation icon]] {{{documentation|Documentation}}} }}</span><span class="mw-editsection plainlinks" id="doc_editlinks">{{int:editsection-brackets|[{{fullurl:{{#if: {{{1|}}} | {{{1}}} | {{SUBJECTPAGENAME}}/doc }}}} {{{view|{{int:vector-view-view}}}}}]}} {{int:editsection-brackets|[{{fullurl:{{#if: {{{1|}}} | {{{1}}} | {{SUBJECTPAGENAME}}/doc }}|action=edit{{#ifexist: {{#if: {{{1|}}} | {{{1}}} | {{SUBJECTSPACE}}:{{SUBJECTPAGENAME}}/doc }} ||&preload=Template:Documentation/preload}}}} {{{edit|{{int:vector-view-edit}}}}}]}} {{int:editsection-brackets|[{{fullurl:{{#if: {{{1|}}} | {{{1}}} | {{SUBJECTPAGENAME}}/doc }}|action=history}} {{{history|{{int:vector-view-history}}}}}]}} {{int:editsection-brackets|[{{fullurl:{{#if: {{{1|}}} | {{{1}}} | {{SUBJECTPAGENAME}}/doc }}|action=purge}} {{{purge|{{int:Code-rev-purge-link}}}}}]}}</span></div>}}
''<small>{{{text|text parameter not translated in [[Template:Documentation]]}}}</small>''
{{#if: {{{1|}}} |{{{{{1}}}}}|{{{{SUBJECTPAGENAME}}/doc}}}}<div style="clear:both;" /></div>{{#ifeq:{{SUBPAGENAME}}|sandbox|[[Category:Sandbox templates]]}}
It's a little heavier than before but better fits default editsection links. Additionally this style would match the Englisch en:Template:Documentation.
Two question you can maybe help me with:
  • The span with the links included the class "dablink" as well as the id "template_doc_page_transcluded". Are they still needed? There were at least no styles applied to the class and I don't know if the id is used somewhere.
  • I tried to unify the translations. Do you know why I can't use ⧼Purge⧽ although translatewiki:MediaWiki:Purge/en seems to be available?
--Patrick87 (talk) 13:44, 22 June 2013 (UTC)
1) The proposal is identically to the current state Did you copy the wrong text? 2) Don't know; requires history digging and poking users 3) don't know, something to ask Raymond or Siebrand. -- Rillke(q?) 20:00, 22 June 2013 (UTC)
1) Oh damn, actually I copied the wrong code. I updated it above. 2) It was there from the start but it seems to be a leftover that was imported from English Wikipedia (there was a Template:Dablink once, which has been deleted). I searched Commons for the strings and I think it's not needed anymore. Let's remove it and just see if somebody complains (I don't think so). 3) OK, thanks. I'll see what I can do, never actively used translatewiki before, so I still have to learn about everything a bit. --Patrick87 (talk) 20:29, 22 June 2013 (UTC)
Thank you. Template code updated. -- Rillke(q?) 23:19, 24 June 2013 (UTC)

Surplus line break below "See also" heading[edit]

When specifying related templates with the seealso parameter, an unnecessary line break is put after the heading and before the links. --Patrick87 (talk) 01:03, 23 June 2013 (UTC)

✓  Done . My fault. -- Rillke(q?) 23:06, 24 June 2013 (UTC)
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. Rillke(q?) 23:06, 24 June 2013 (UTC)

Shorthand or redirects[edit]

How do I add more than one shorthand or redirect? See Template:Cat see also/doc and Template talk:Cat see also/doc.

These all redirect to Template:Cat see also. --Timeshifter (talk) 06:14, 1 July 2013 (UTC)

I figured out how to add more than one shorthand redirect to Template:TemplateBox. See example templates, and their documentation pages that use {{TemplateBox}}:
Template:Cat see also
Template:Cat see also/doc
--Timeshifter (talk) 07:19, 26 July 2014 (UTC)

Dropping "This part of the template is only available in some languages"[edit]

Do we need that message telling the obvious? Or is there something behind it? -- Rillke(q?) 18:05, 17 August 2013 (UTC)

Minor improvements[edit]

Thanks for all the great work done on this template. Several issues I had with the old template were fixed. As I am looking at the new format of this template, I was noticing many things that could be improved. Some of them are new and some are leftovers from the old template. All should be treated as suggestions open for discussion, if controversial.

  • In Parameter table aliases should be listed one per line, otherwise it looks like you have parameter names with commas.
    • ✓  Done -- Rillke(q?) 13:58, 22 August 2013 (UTC)
  • Parameter table have an empty column on the left. It looks like it is for the new "1label" and "1set" parameters. May be it should disappear if they are not used, which is in most cases at the moment. Also I think the Parameter code and aliases column should be first and the short label should be column one of the description.
    • ✓  Done -- Rillke(q?) 13:58, 22 August 2013 (UTC)
  • Localization section for mediawiki-msg case says "This template is localized by utilizing MediaWiki namespace messages. These can be translated at translatewiki.net (current translations)." with "current translations" usually having a dead link to nonexisting page. See {{Artwork}} or {{Information}}. May be we can overwrite this default location somehow.
  • i18n-method often used is {{LangSwitch}} block in some other i18n template like subtemplates of {{I18n}} or sub templates like {{Artwork/i18n}}. Some of those could and should be moved to translatewiki, but at the moment are kept here.
  • I always have problems filling Enumerated type parameters like namespace, usergroup or i18n-method, since many templates do not fall into any of the single categories. For example {{Creator}} template is is intended to be used in "File" and "Category" namespace or {{Artwork}} is localized using translatewiki and {{Artwork/i18n}} subtemplates. May be we can allow lists of enums.
  • Usage section provides block of code which can be cut and copied as a whole but not in pieces. I often like to copy parts of the template to add to existing pages. Can we go back to allowing that?
    • A "copy button" would be handy. Also the current "feature" is somewhat fancy as not supported by most browsers, except FF. Let me think a bit about this. -- Rillke(q?) 13:58, 22 August 2013 (UTC)
    • ✓  removed select-all-with-one-click as it is counter-intuitive and not well-supported. -- Rillke(q?) 16:09, 5 December 2013 (UTC)
  • Usage section can be either in one-line or multi-line format. Can we add an option of multi-line with aligned "=" signs? That is often preferred formatting for infobox templates.
    • ✓  Done . print=infobox or simply type=infobox omitting print and lines. -- Rillke(q?) 13:58, 22 August 2013 (UTC)
  • Empty "1", "1d", "1d-en", "1def", "1stat", etc. should be treated the same as if they were not provided at all. For example Template:Documentation/preload is in Category:LangSwitch template without default version maintenance category because of empty "1d-en".

--Jarekt (talk) 13:03, 19 August 2013 (UTC)

I agree that users should be able to copy a portion of the "usage" code. It's very annoying to only be able to copy the whole thing. And if only FF users are getting this "helpful feature", I say disable it so everyone can highlight and copy the text they want in the usual way. - dcljr (talk) 10:33, 5 December 2013 (UTC)

How to get TemplateBox to properly generate a “Template data” section?[edit]

parameter order[edit]

Parameter order in Template:Artwork/doc seems to have little correlation with "1", "2" order. For example "accession number" is suppose to be between "notes" and "source". --Jarekt (talk) 17:52, 18 November 2013 (UTC)


Hi! New automatic categories have been made, but we already have similar ones:

Can they be merged? --tacsipacsi (talk) 18:24, 17 March 2014 (UTC)

We've implemented that this way because the categorization will be according to how the approach is documented, allowing to use, for example category intersections to spot errors in documentation. Category:Commons templates by documented internationalization approach is a maintenance category. -- Rillke(q?) 19:19, 17 March 2014 (UTC)

Suggestion for copy code[edit]

How about display automatically the source code (en) to copy (as it is often used before Autotranslate) for the new language subpage (for example Template:Apache/en)!?

|text=Copyright © {{#if:{{{2|}}}|{{{2}}}|{{#expr:{{CURRENTYEAR}}}}}} {{#if:{{{1|}}}|{{{1}}}|The author}}

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an <span style="text-transform: uppercase">"as is" basis, without warranties or conditions of any kind</span>, either express or implied. See the License for the specific language governing permissions and limitations under the License.
{{translated tag|license}}

And then mention that

- |lang=en
+ |lang={{subst:SUBPAGENAME}}

is to replace. -- Perhelion 21:41, 26 May 2014 (UTC)

Oh I see now the source code is automatically in the new subpage (so it's almost not needed). I've never done this. :-P But is it not possible to replace the static "en" to {{subst:SUBPAGENAME}}? -- Perhelion 21:54, 26 May 2014 (UTC)

If you tell me how, I'll do it. Apart from that, please create new templates using the translate extension for translation. -- Rillke(q?) 22:30, 26 May 2014 (UTC)

Explicit translatewiki.net link[edit]

{{editprotected}} Please replace:

These can be translated at <tvar|translatewikilink>[[:translatewiki:MediaWiki:{{#if:{{{i18n-mediawiki-msg|}}}|{{{i18n-mediawiki-msg|}}}|Wm-license-{{lc:{{BASEPAGENAME}}}}-text}}|translatewiki.net]]</>


These can be [[<tvar|twn-wm></>|translated at translatewiki.net]]

--Nemo 18:13, 3 July 2014 (UTC)

@Nemo bis: This will make the i18n-mediawiki-msg parameter superfluous. Is it intentionally dropped? -- Rillke(q?) 18:29, 3 July 2014 (UTC)
Yes and no, I'm not aware of substantial use of messages by templates on Commons other than those in the WikimediaMessages extension and linking MediaWiki namespace pages doesn't work very well anyway. However if you're not sure I'm too lazy to check hundreds templates and we can keep it, like
These can be [[<tvar|twn-wm>translatewiki:{{#if:{{{i18n-mediawiki-msg|}}}|MediaWiki:{{{i18n-mediawiki-msg|}}}|Special:Translate/ext-wikimediamessages}}|translated at translatewiki.net]]
--Nemo 17:27, 5 July 2014 (UTC)
So'll be it. Thank you. -- Rillke(q?) 19:19, 5 July 2014 (UTC)

Category:Pages using duplicate arguments in template calls[edit]

Rillke There is a problem with {{TemplateBox}} using "Example" variable as it shows up in Category:Pages using duplicate arguments in template calls for example {{TemplateBox|name=CopyvioOTRS|example=0000}} is enough to be added to that category. Is there a way to fix it? --Jarekt (talk) 13:01, 13 November 2014 (UTC)

Needs debugging. First we have to find out which template is called with duplicate arguments. -- Rillke(q?) 19:16, 13 November 2014 (UTC)
FWIW, Tdoc on Meta (a vintage 2010 {{TemplateBox}} simplified by Patrick) also puts lots of templates in this new tracking category. –Be..anyone (talk) 18:40, 26 December 2014 (UTC)


Hi, a second example won't show up whenever I try to use the example2 parameter here. What am I doing wrong? // WikiPhoenix [Talk] 00:33, 9 December 2014 (UTC)

Artefacts in template data[edit]

The template data shown for "status" contains three unescaped &nbsp;. Similar "translation method" contains three unescaped &#123;&#123;[[link]]&#125;&#125; constructs, apparently some escaped {{tl|autotranslate}} links. mw:Help:TemplateData mumbles something about "no wiki markup in JSON, svp", maybe these are copy and paste issues. There are more (similar) issues in the template data. –Be..anyone (talk) 18:25, 26 December 2014 (UTC)

i18n-method = module[edit]

Some of the internationalization pages are slowly moving from {{LangSwitch}} blocks in templates to tables in Lua, see [1]. We should probably have an i18n-method option that matches that. --Jarekt (talk) 20:50, 27 January 2015 (UTC)

Symbol support vote.svg  Support , needed. --Zolo (talk) 08:16, 29 January 2015 (UTC)
Would also require a specifier where the module can be found. -- Rillke(q?) 11:26, 19 March 2015 (UTC)
@Rillke:, Yes actually both LangSwitch blocks and lua based equivalents could use such parameter. --Jarekt (talk) 18:36, 23 April 2015 (UTC)

"Or use the shorthand"[edit]

It is what shows up in the shorthand spot. Could this be changed to:

  • Shorthand and redirects

People are deleting some info about redirects because some redirects are not always shorter names (shorthand). People create all kinds of redirects, both longer and shorter than the original template name. Anything that helps people remember and use the templates is a good thing. We all remember different things, different spellings (British, American, etc.), different phrasing, etc.. --Timeshifter (talk) 00:22, 5 February 2015 (UTC)

Symbol oppose vote.svg  Oppose based on my comment on your talk page. I have no problem at all with, say, {{igen}} as desirable shorthand for {{image generation}}, 4 vs. 16 characters. Not the same as {{CatCat}}, where a "see also" redirects is good enough to cover its "longhand" redirects. –Be..anyone (talk) 05:50, 5 February 2015 (UTC)
There is nothing to oppose. As I said, you obviously are clueless as to how many people actually use redirects concerning templates. They, like shorthand, are used for convenience and memory. The number of characters is not necessarily what makes a redirect convenient. It is the fact that one easily remembers certain redirects. This is the traditional reason many people use these template redirects on the Commons. I have created many template redirects, and many template shorthands. "Shorthand" in TemplateBox is just a one-word entry in the form. With one-word entries one must choose one word. Traditionally we have listed both redirects and shorthand in the documentation. TemplateBox is a more recent creation. Thus we need to align it with tradition by using my suggestion or something similar. Separating shorthand and longhand redirects in different parts of the documentation is just stupid. Spelling and punctuation variations are common reasons for template redirects. --Timeshifter (talk) 02:01, 6 February 2015 (UTC)
If you almost always want a "redirects" link (WhatLinksHere hiding links and transclusions) {{TemplateBox}} could almost always generate it and put it into its "see also" section or similar. The shorthand position is at the top of the documentation, it's for advertizing, same idea as {{shortcut2}}. But learning that {{MetaCat}} has an alias without camel-case, plus a link to check that this in fact the only redirect to MetaCat is a distraction from what's relevant, the syntax and parameters of {{MetaCat}}.
For {{CatCat}} it is similar, but it actually has some (longer) aliases, which might be interesting for users who don't want to click WhatLinksHere + hide links + hide transclusions. The construction of one link for this business is fun, but at the end of the day, how often do you plan to check all redirects to {{CatCat}}, and why must that be at the top of the documentation? –Be..anyone (talk) 02:30, 6 February 2015 (UTC)
{{shortcut2}} is not the same as the shorthand and redirects for templates. Most {{shortcut2}} shortcuts I see consist of the first letter of each word in the title of a page. Shorthand and redirects for templates consist of many variations of the template name. Both short and long. Separating them to different parts of the documentation page serves no purpose except to confuse users of templates. Users may create more redirects, not knowing what already exists. Some users may be less likely to use the templates. Because they can't remember the exact original name of the template. I think the "redirects" link (WhatLinksHere hiding links and transclusions) should be on all template pages. Automatically created by TemplateBox. Sometimes the "redirects" link (WhatLinksHere hiding links and transclusions) is added to a template page, but the additional redirects disappear because some clueless admin deleted the redirects, and then it seems like it serves no purpose. Some people go around changing the name of redirects on the pages where they are being used. A big mistake. Then it seems like the redirect is not being used. So it gets deleted. The person who created the redirect then stops contributing to the Commons, at least as concerns that template, because people are ruining their work, and they can no longer remember the name of the template. Many people don't know how to look for redirects. The point is to make it easy for users to use templates. The "redirects" link (WhatLinksHere hiding links and transclusions) makes using templates easier. --Timeshifter (talk) 08:38, 7 February 2015 (UTC)
FWIW: {{TemplateBox|shorthand={{redirects|Metacat}}}} should works as documented for {{redirects}}, and all bare {{TemplateBox|shorthand={{tl|Metacat}}}} constructs should be updated by a bot. Only the remaining cases should be kept as is. This will have your desired backlink effect on explicitly enumerated aliases, i.e., the alias gets a link from the /doc subpage.
I still doubt that listing {{ucfirst:{{lc:CamelCase}}}} is necessary, only a maniac would delete Camelcase. Example, there are three {{Cc-by-sa-3.0-igo}} spelling variations (invented by the ESA), all tagged as redirects to a license template. Counter-example, I created {{EmptyCatGood}} as redirect to {{empty category}}, because I like the funny mediawikiwiki name, but I'd have no objection to an import of the real thing. After all redirects can be expanded into separate pages in all namespaces. –Be..anyone (talk) 20:49, 9 February 2015 (UTC)
Redirects don't have anything to do with the template itself, and listing them doesn't provide users with any useful additional information. Therefore, they shouldn't be added to /doc pages, and this edit should be reverted.    FDMS  4    20:18, 16 February 2015 (UTC)
The docs have long had redirects. The template is a more recent invention. And shorthand redirects are still redirects. Shorter redirects are not necessarily easier to remember than longer redirects. And that is the point of all of these redirects, easy memory. --Timeshifter (talk) 00:13, 18 February 2015 (UTC)
I'm not going to use the {{esoteric}} {{TemplateBox}} in any past, present, or future shape anywhere, the "template data manager" i18n now passes "good enough" and is available on all WikiMedia projects. This also solves the "seealso=" conflict, without the {{TemplateBox}} abomination {{redirects}} works as designed. –Be..anyone (talk) 04:06, 18 February 2015 (UTC)

Empty parameters[edit]

Because the > 40 SVG created with ... templates have almost the same decription, it seems reasonable to have one and not > 40 documentations for them. This is done with the unified template documentation {{SVG created with/doc}}, kind of meta docu. So far, so good.

Unfortunateley they are not absolutely identical. Most are for only SVG, some create also PNG. About a dozen of them can show the code. And a few ones have the parameter IMPORTANT. It would be nice if these special cases can be handled with conditional decriptions.

At the moment I cannot see a possibility for a construct like |4={{#if:...}} because the template box module will in this case show the empty parameter 4.

|1d=description of 1{{exp|st}} parameter 
|2d=description of 2{{exp|nd}} parameter 


|4={{#if:{{{4|}}}|show parameter}}
|4d={{#if:{{{4|}}}|describe parameter}}
|4def={{#if:{{{4|}}}|describe default}}


The empty parameters 3 and 4 show up in "Usage" and in the table. {{edit request|technical=1}} The display of parameters without content in the parameter name should be suppressed. sarang사랑 13:45, 8 March 2015 (UTC)

Your example, or rather, {{TemplateBox}}, clobbered the section edit links on this talk page, and it took me some hours to fix this. Certainly not your fault, it might be a missing magic word __FORCEEDITSECTION__ to overrule a generated __NOEDITSECTION__. Your box also makes sense (for me) as <pre>-formatted code instead of an embedded <div>-example, therefore I picked s/div/pre/ to enable the edit links again.
Otherwise Symbol oppose vote.svg  Oppose , there are too many hopeless {{TemplateBox}} "features" for piecemeal patches. Your best option after not using {{TemplateBox}} at all might be useTemplateData=only, or simply use only the template data manager and not its {{TemplateBox}} predecessor. The template data manager is what everybody outside of commons + Meta will know, and meanwhile it supports i18n. If you don't want to document parameters 3+4 just klick on "remove" in the suggested parameters, or remove what you don't like in the generated JSON. –Be..anyone (talk) 03:38, 9 March 2015 (UTC)
  Not done — I don't think this a maintainable change to TemplateBox. —RP88 (talk) 06:16, 7 November 2015 (UTC)

add 1sort parameter[edit]

one of the most painful operations I seem to be performing a lot is adding new parameters to templates. The working with templates goes fast but adding new parameters to the documentation that already have 30 of them is quite painful, since it often involves need to reorder and rename parameters describing template parameters (1=, 1d=, 1stats, etc.). In the old days there were only 4 so it was not so bad but now with the translations we can have 10+ parameters per each of 30 template parameters, so there is potential to a lot of renames and a lot of manual mistakes. I would like to propose 1sort, 2sort, ..., etc. which by default would be 1, 2, ..., etc. but 1sort=2 and 2sort=1, would swap the displayed order of the fields. --Jarekt (talk) 02:33, 16 March 2015 (UTC)

I'd prefer having a script that does re-ordering over adding another confusing parameter. -- Rillke(q?) 11:28, 19 March 2015 (UTC)

example (4) - bug[edit]

Is it possible to remove please the default pipe "|" symbole from example value? In many examples there is no considerable display possible (see example). This could also be the reason for the bot doing by Leyo in fixing hundreds of templates (for example in Category:Pages using Information template with incorrect parameter) because the examples are wrong...

The description says “Example use (works with a single unnamed parameter only). I guess there is no possible without a bot to fix all existing usage of this bad awkwardness. User: Perhelion (Commons: = crap?)  10:41, 19 March 2015 (UTC)

Please provide a diff or the desired new version unless it's too complicated for you. -- Rillke(q?) 11:24, 19 March 2015 (UTC)

Is it possible to have a word (null, none, empty, ...) to indicate that the model has no parameter, and delete the | useless? thank you --Camulogene77 (talk) 13:18, 15 October 2017 (UTC)

Any of them is a valid parameter. It’s possible that omitting the |example= and using |example-value= would be a resolution, but why do we need it? If there are no parameters, just omitting the <includeonly> tags makes the template content appear above the documentation. --Tacsipacsi (talk) 13:57, 15 October 2017 (UTC)
The problem is in the documentation, the "example-value" field makes it possible to force the result of the example but if the "example" field is empty, the model does not show example. how to display an example without parameters in the "example" field. For example: {{Collective}}. --Camulogene77 (talk) 18:20, 15 October 2017 (UTC)
I know that it doesn’t work currently, I meant that it might be a solution to be implemented. However, as I said, I don’t see any point in just repeating what’s already visible on the top of the page. (Please don’t mark your comments as minor edits. They aren’t, and people might not notice them if you mark them as such.) --Tacsipacsi (talk) 11:35, 16 October 2017 (UTC)

msg-shorthand-params-possible translation[edit]

Please add msg-shorthand-params-possible translation.

|msg-shorthand-params-possible= <translate>
… parameters as described … </translate>

{{edit request}} Thanks in advance. --FRacco (talk) 12:05, 4 April 2015 (UTC)

✓  Done Awesome! Thank you! Rillke(q?) 12:45, 4 April 2015 (UTC)

Options for TemplateBox parameter "type"?[edit]

I am trying to create my first template, and as one might expect, am getting somewhat lost in meta-code-stuff and the parameter of the parameter level of complexity of it all. I am creating the /doc page for my template, and am stuck on what happens when I specify a particular "type" for one of my parameters under, for example, the 1type parameter (...which is confusing to even say never mind understand, but I do get it, so far, I think). I understand that I need to choose between number, string, string/wiki-user-name, string/wiki-page-name, and string/line (or ignore it and allow it to be the default value of unknown), but though I can guess what selecting certain values here will do— if I choose the value number for my 1type parameter, this will require the user of the template to use a number value for this parameter when actually using the template (will it reject other types of entries? With a warning of some kind?) and that using string will allow a user to enter text for that parameter— what are the effects of string/wiki-user-name, etc.? Do these enforce the use of the current template's user's name in the parameter? Do they only enforce the formatting of such a name? Or something else? And what is string/line supposed to do? Is there a place where I can get some explanatory documentation about these values? I've been looking up and down and just found nuthin' so far. Thanks! KDS4444 (talk) 10:44, 16 August 2015 (UTC)

I've changed the doc, is this more helpful? User: Perhelion (Commons: = crap?)  15:35, 17 August 2015 (UTC)
Yes, thank you! KDS4444 (talk) 07:48, 18 August 2015 (UTC)

New translation method needed:Wikidata[edit]

Parameter i18n-method should also take Wikidata parameter to indicate pages translated by using Wikidata, the way {{Authority control}} is and there are few other templates also using it. --Jarekt (talk) 18:22, 30 May 2016 (UTC)

Also Module:i18n subpages are missing. This may even be mixed with Wikidata, like Module:i18n/institution is. —Tacsipacsi (talk) 09:29, 19 May 2018 (UTC)

Another bug[edit]

The example {{Image generation/doc}} describes 27 parameters (number 7, 10 and 13 are left empty for future use). It concludes a lot of more descriptions, they are not so easy to insert due to restrictions and missing options in the TemplateBox.
After displaying the descriptions for parameters 1 to 16 the following descriptions are not in sequence, after 16 comes 27, then 17 and 18, then 24 and so on. Is there a possibility to correct the sequence? sarang사랑 08:45, 28 September 2016 (UTC)


The example seems misleading.


English: Abcdefghijklmnopqrstuwxyz
English: Abcdefghijklmnopqrstuwxyz
I think this is in Template:TemplateBox/layout. Perhaps it should look more like this:


English: Abcdefghijklmnopqrstuwxyz

Hyacinth (talk) 19:12, 7 June 2017 (UTC)

Fail on i18n-subpage[edit]

If this is empty, it gives a fail link to subpage: Template:/ As this value is default inserted on a new doc creation, this is a heavy undocumented error cause. -- User: Perhelion 14:14, 18 October 2017 (UTC)

✓  Done Its seems there was also an empty name parameter. -- User: Perhelion 19:24, 26 October 2017 (UTC)