Template talk:Collapse bottom

Alternative message

edit

{{editprotected}} Please change ''The above....'' to ''{{{1|The above....}}}'' so that the message can be specified, just like {{Collapse top}}, especially when it is not a "discussion" that has been collapsed.

Also, or alternatively seeing as {{Collapse top}} does not allow the corresponding text to be changed, change the (default) text to "The above content has been placed in a collapse box for improved usability.", which is identical to the text from {{Collapse top}} except for "above". Mark Hurd (talk) 09:58, 30 May 2009 (UTC)Reply

  Done, went with your alternative proposal. — Martin (MSGJ · talk) 11:09, 30 May 2009 (UTC)Reply

Fix stray characters

edit

There is a "|}" at the top of the article. Do they serve a purpose? – S. Rich (talk) 00:37, 22 February 2013 (UTC)Reply

Given your 61,000 edits I hope you're joking, but they are the actual purpose of this template: closing off the collapsible table started by {{collapse top}}. Mark Hurd (talk) 13:35, 29 March 2014 (UTC)Reply

Broken template

edit

@NJA: please revert [1], it breaks the template. See #Fix stray characters above. Thanks, --DannyS712 (talk) 02:51, 8 August 2019 (UTC)Reply

  Done N.J.A. | talk 02:53, 8 August 2019 (UTC)Reply
@NJA: Thanks. Given that this has come up before, I've created Template:Editnotices/Page/Template:Collapse bottom, just to be on the safe side. --DannyS712 (talk) 03:00, 8 August 2019 (UTC)Reply
It looks like Northamerica1000 has made an identical mistake, despite your editnotice. * Pppery * it has begun... 03:00, 14 May 2020 (UTC)Reply
Oops, sorry about that. I used the template at the bottom of a discussion and it was adding "|}" at the bottom. Doesn't seem to be occurring now, though. Here's a diff from when it occurred minutes ago...scroll to bottom. North America1000 03:08, 14 May 2020 (UTC)Reply
Pppery: Well, the "|}" is back (diff). Will all discussions that use the template now have to this in place at the bottom? I hope not. North America1000 03:12, 14 May 2020 (UTC)Reply
(edit conflict) @Northamerica1000: Was this because you were using {{collapse bottom}} instead of {{archive bottom}}? J947 [cont] 03:17, 14 May 2020 (UTC)Reply
Northamerica1000, because you used archive top and collapse bottom and those two templates are not meant to be combined. I fixed it so it uses archive bottom and the extra character goes away. Best, Barkeep49 (talk) 03:18, 14 May 2020 (UTC)Reply
(edit conflict) Also, pings only work if you add a timestamp in the same edit as you add the ping, so Pppery wouldn't have received a notification from that message. J947 [cont] 03:19, 14 May 2020 (UTC)Reply
(ec) Got it —   Facepalm — I figured it out after revisiting the page, but Barkeep49 beat me to fixing it. Sorry for the hassle. North America1000 03:21, 14 May 2020 (UTC)Reply
I've now added a testcase page for this template as well. As a general note for anyone editing templates: if you see {{high-use}} on the template documentation page, it is a widely-used template and you should test your changes in the sandbox first. If you see {{used in system}} on the template documentation page, the template is used in an interface message and you should test your changes in the sandbox first. If the template is fully protected as a widely-used template used in an interface message, you should test your changes in the sandbox first. And if there's an editnotice telling you not to do the exact thing you're trying to do, you should really test your changes in the sandbox first. --AntiCompositeNumber (talk) 03:28, 14 May 2020 (UTC)Reply

Edit request to complete TfD nomination

edit

Template:Collapse bottom has been listed at Templates for discussion (nomination), but was protected so could not be tagged. Please add:

<noinclude>{{subst:tfm|help=off|1=Hidden archive bottom}}</noinclude>

to the top of the page to complete the nomination. Thank you. –MJLTalk 03:10, 28 February 2021 (UTC)Reply

Done. Jo-Jo Eumerus (talk) 09:55, 28 February 2021 (UTC)Reply

Protected edit request on 14 May 2021

edit

This page gets listed in Special:LintErrors/stripped-tag because of having |}</div> without the balancing <div>{| tags. Functionally this is correct since this template is paired with {{Collapse top}} which has the opening tags. So a div and table tag wrapped in noincude needs to be added to remove the page off Linter report.

So in the first line, replace |}</div><noinclude> with <noinclude><div>{|</noinclude>|}</div><noinclude>

You can see in Template:Collapse bottom/sandbox that this works. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 06:05, 14 May 2021 (UTC)Reply

  Not done this isn't actually causing any problems, no need to change it. — xaosflux Talk 10:59, 14 May 2021 (UTC)Reply
To editor Xaosflux: then can you make the two tags as includeonly? <includeonly>|}</div></includeonly> I have updated the sandbox with this. You can check testcases that it works. It won't change the template function and removes page from Linter list. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 11:14, 14 May 2021 (UTC)Reply
  Donexaosflux Talk 12:43, 14 May 2021 (UTC)Reply

An edit request that was emailed to me

edit

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Hi everyone! I was emailed a request to edit this article and replace line 1 from:

<includeonly>|}</div></includeonly><noinclude>
to:
<div><includeonly>|}</div></includeonly><noinclude>

Is this change necessary? I'm posting this message on behalf of the user that emailed this to me. :-) Thanks for looking - ~Oshwah~(talk) (contribs) 03:08, 16 June 2021 (UTC)Reply

Oshwah, no, it would be wrong. The /div is within includeonly tags so it doesn't show on the template page. Adding an opening div tag would break or invalidate the template page. Alexis Jazz (talk or ping me) 17:16, 15 August 2022 (UTC)Reply
Alexis Jazz - Good call; thanks for responding and for letting me know. :-) What about the following code below instead? It basically swaps the position of the <div> and <includeonly> tags. I'm still trying to figure out why the extra <div> tag is necessary and being requested in the first place (as well as the </div> tag, if it's even an extra one at all)... I'm also trying to find the original email that was sent to me about this as well...
<includeonly>|}</div></includeonly><noinclude>
to:
<includeonly><div>|}</div></includeonly><noinclude>
Thoughts? ~Oshwah~(talk) (contribs) 04:25, 31 August 2022 (UTC)Reply
Oshwah, that would break the template. The lone </div> here complements the opening div tag in {{collapse top}}.Alexis Jazz (talk or ping me) 13:25, 31 August 2022 (UTC)Reply
Alexis Jazz - Ah, thank you. I probably would've missed that... Okay, then I'm not making any changes. Case closed! ~Oshwah~(talk) (contribs) 14:33, 31 August 2022 (UTC)Reply
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Protected edit request on 16 December 2023

edit

Please edit the comment, on the third line of the code, replacing the current with the following:

The template is fully protected and can only be edited by administators. Every admin knows where to put categories and interwiki links. Therefore I do not see any benefit of this change. — Martin (MSGJ · talk) 19:34, 17 December 2023 (UTC)Reply
Okay and I'm sorry. I agree that I am being unnecessarily nitpicky due to my paranoia related to Yin and Yang and the Butterfly effect. Nishimoto, Gilberto Kiyoshi (talk) 21:32, 17 December 2023 (UTC)Reply

Bug: cot works in auto-indent, but cob breaks

edit

Per title, when replying in a thread using the visual Reply Tool, which auto-indents markup with :, {{cot}} seems to function with an arbitrary number of preceding :::: but {{cob}} gets incorrectly parsed, resulting in all subsequent text being hatted. Going into markup and removing the indents from the template resolves the issue, but in any case any hatted text will not be indented at the same level with one's reply, disrupting reading. SamuelRiv (talk) 03:06, 15 January 2024 (UTC)Reply