Template talk:Db-meta

From Wikipedia, the free encyclopedia
  (Redirected from Template talk:Db-banned)
Jump to navigation Jump to search


The CSD that this template relates to was changed, and therefore the template was changed to reflect that, but I find the new wording clunky and potentially confusing:

" This template may meet Wikipedia's criteria for speedy deletion as either a page in the draftspace, a rejected/unsubmitted userspace Articles for Creation page, or a draft in either namespace with no content except the placeholder article wizard text that has not been edited (excluding bot edits) in over six months. See CSD G13."

There's got to be a better way to word this, but in the interest of not making it worse I'm soliciting suggestions here. Beeblebrox (talk) 21:59, 1 January 2019 (UTC)

For one thing, "either" at the start jangles since it's for two-item mentions only. In any event, why not just use the criterion's actual wording from WP:CSD#G13, with some minor changes to make it fit the use?
This [TYPE OF PAGE] may meet may meet Wikipedia's criteria for speedy deletion as a page that has not been edited by a human in six months, found in: 1) the draft namespace; or 2) the userspace with an {{AFC submission}} template; or 3) the userspace with no content except the article wizard placeholder text. Note that redirects are exempt from this criterion. See CSD G13.
--Fuhghettaboutit (talk) 01:07, 27 January 2019 (UTC)

Editintro parameter for contesting[edit]

Back in 2011, there was a suggestion to add an edit intro to the page that loads when you click "Contest this speedy deletion" but nothing ever came of it. I want to revitalize that idea because there are often empty contentions created by new users. I modified Template:Db-meta/sandbox to display Template:Hangon preload editintro when you click the button. Anyone mind if I added this to the live template? Regards SoWhy 08:54, 28 February 2019 (UTC)

Seems a very good idea. Galobtter (pingó mió) 10:28, 1 March 2019 (UTC)

Note, Suffusion of Yellow has created 968 (hist · log) to track such uses (might be set to disallow or warn later). Regards SoWhy 10:40, 1 March 2019 (UTC)

Since there were no objections, I have added it to the template. Regards SoWhy 19:52, 10 March 2019 (UTC)

Use named parameters in more db templates[edit]

A few of the db templates only use unnamed parameters for meaningful switches, so I've added some to those sandboxes and would appreciate a review of the changes since nested curly braces make me go crazy:

There is some discrepancy between whether templates use {{{named|{{{1|}}}}}} and {{{1|{{{named|}}}}}}. I changed the order in a couple of the diffs above (move and t3) for the existing parameter out of habit, but it's not immediately clear to me that there's an advantage to one over the other? ~ Amory (utc) 13:07, 8 March 2019 (UTC)

They all look good to me. — JJMC89(T·C) 03:30, 9 March 2019 (UTC)
 Done, thanks. ~ Amory (utc) 15:06, 10 March 2019 (UTC)
@JJMC89: I wonder if it might've been better for me to use rationale instead of reason for F9? From looking over {{db-multiple}}, it processes the former but not the latter. {{db-f7}} uses reason, as well as {{db-t2}} (which I had thought to merge into the unnamed 1 parameter), perhaps rationale would be better for them as well? {{db-move}} does as well, but since that's not compatible with {{db-multiple}} it wouldn't be an issue. ~ Amory (utc) 18:23, 10 March 2019 (UTC)
I would just make them synonymous; we're very inconsistent with parameter names, and it's hassle having to come to the template doc to see which it uses.  — SMcCandlish ¢ 😼  18:42, 10 March 2019 (UTC)
I'd make them all use the same parameter name. Adding an alias for the other is up to you. — JJMC89(T·C) 21:22, 10 March 2019 (UTC)


Please remove the statement that GFDL 1.2 files are accepted at Commons, as this is no longer the case per this discussion. funplussmart (talk) 21:37, 17 March 2019 (UTC)

 Done — JJMC89(T·C) 23:31, 17 March 2019 (UTC)

Possible fix for missing paragraph end tag and possibly incorrect closing of ifeq{self}[edit]

I have edited the sandbox with a proposed change to make use of a closing /p tag that is currently ignored. I think it is ignored because the expression ifeq{self} is not properly closed. I know that this template is used in many places, in many ways, however, and the test cases page doesn't have very many cases on it, so I am wary of putting this change into production without a check from other editors.

The current template's syntax problems can be seen by putting {{db-g7}} into Special:ExpandTemplates and observing that the closing /p tag that is in the template code is not rendered in the G7 template. Viewing the template code with the Syntax Highlighter gadget also shows the problem (the /p shows up in yellow, which is an indication that something is wrong). – Jonesey95 (talk) 19:49, 31 March 2019 (UTC)

Hearing no objections, I am carefully but boldly implementing what should be a minor change. I welcome any and all trouts and reverts if I screwed something up. – Jonesey95 (talk) 19:41, 16 May 2019 (UTC)
@Jonesey95: The only screw-up I see with this edit was that it moved the "Contest this speedy deletion" button and last editor message outside the deletion tag. Jalen D. Folf (talk) 20:00, 16 May 2019 (UTC)
Thanks for your patience, everyone. I have just implemented a slightly different attempt at a fix. This one keeps the "last edited" message inside the box. – Jonesey95 (talk) 08:44, 17 May 2019 (UTC)
Looks OK. The <p>...</p> element is peculiar (compared to other HTML elements) in that although it behaves as a block element, it cannot itself contain block elements such as <div>...</div> <table>...</table>, lists etc. When you attempt to place a block element "inside" a <p>...</p>, the opening tag of the block element implicitly forces a closing </p> immediately prior to the opening tag of the "enclosed" block element. In this case, the {{#tag: inputbox | ... }} creates a <div>...</div>. --Redrose64 🌹 (talk) 14:39, 17 May 2019 (UTC)
Thanks. I know that p tags have complex behavior, and they don't seem to make a difference most of the time, so I usually leave them alone when I am cleaning up Linter errors. This one was popping up in many db-* templates, however, and it was bugging me, so I wanted to get it off the list. – Jonesey95 (talk) 15:54, 17 May 2019 (UTC)

Template:Db-unfree listed at Redirects for discussion[edit]


An editor has asked for a discussion to address the redirect Template:Db-unfree. Please participate in the redirect discussion if you wish to do so. ~ Amory (utc) 15:15, 15 April 2019 (UTC)

Template-protected edit request on 21 April 2019[edit]


please either remove <includeonly>--</includeonly>, or replace it with --. The preload should not contain hidden characters in this manner. If the "--" should be added before the signature, there is no reason to "includeonly" them, and if they should not be, they shouldn't be present at all. Thanks, --DannyS712 (talk) 20:47, 21 April 2019 (UTC)

A3 is not in your list but has the same thing going on. Was that a deliberate omission? --Izno (talk) 01:47, 22 April 2019 (UTC)
@Izno: No, I just missed it. Its not template-protected (though maybe it should be) so I could implement this myself, but given that the scope affects multiple templates I'll wait until someone else opines about if the "--" should be kept at all. Thanks for catching that though. --DannyS712 (talk) 02:04, 22 April 2019 (UTC)
also applies to C1, F1, F2, and probably others, that I didn't list. I only listed the ones that I can't edit myself, and based on the edits to those I'll either remove the "includeonly" tags or the entire -- part. --DannyS712 (talk) 02:05, 22 April 2019 (UTC)
 Done Please feel free to make amendments to the other templates. Izno (talk) 01:50, 23 April 2019 (UTC)
@Izno: thanks. Per your edits, I will remove the "includeonly" tags but leave the "--". Thank so much, --DannyS712 (talk) 01:59, 23 April 2019 (UTC)

Template-protected edit request on 23 April 2019[edit]

At Template:Hangon preload A7, please replace ~~<noinclude />~~<noinclude> with --~~<noinclude />~~<noinclude> (add "--") to match the other hangon preload templates. See also the discussion above. Thanks, --DannyS712 (talk) 02:05, 23 April 2019 (UTC)

 Done Izno (talk) 02:06, 23 April 2019 (UTC)
@Izno: wow that was fast --DannyS712 (talk) 02:08, 23 April 2019 (UTC)