Template talk:Resolved
Add topic | Template:Resolved is indefinitely protected from editing as it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. This template does not have a testcases subpage. You can create the testcases subpage here. |
Bot
[edit]Hey, is there a bot that archives messages marked with this template? I know Commons uses something like that and I imagine we had something at some point, but it's hard to find anything about it. czar 23:11, 17 October 2015 (UTC)
- To answer my own question, see User:ClueBot III/ArchiveThis. It's currently handling the threads at WP:RX. czar 19:22, 4 March 2017 (UTC)
2014 changes broke usage
[edit]The last changes in 2014 broke the default usage, e.g.,
{{Resolved|Updated both articles with 2007 data per clear consensus; they are now in sync. ~~~~}}:
ResolvedAnd now requires |1=. But since it was done in 2014 and the documentation hasn't been updated since then, I'm not sure whether the best course of action is to revert the 2014 change that hadn't been implemented in the documentation or to update the documentation to match the change. I think it was smarter in its prior iteration, though it could be feasibly updated to take either param. 
czar 19:20, 4 March 2017 (UTC)
- @Czar: It would probably be best if it supported both, so all uses of it in archives and so forth would work. Also pinging SMcCandlish, who made the change. Graham87 08:44, 5 March 2017 (UTC)
- Those changes didn't break anything; all they did is permit either numeric or word-based parameter names, without changing either parameter. Before the changes, one parameter required a number (or nothing) and the other required a word (or nothing, but it had to be second), which was confusing and inconsistent. A
|1=or|reason=is only required if your sig (or the text of the message) include a=character, as many custom sigs do (e.g. in a<span style="something...">...</span>. Demonstration that it works as intended:{{Resolved|This is the message|Boo-yah}}- – This is the message Boo-yah
{{Resolved|2=Boo-yah|1=This is the message}}- – This is the message Boo-yah
{{Resolved|reason=This is the message|text=Boo-yah}}- – This is the message Boo-yah
- I've updated the documentation. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 08:10, 10 March 2017 (UTC)
- Those changes didn't break anything; all they did is permit either numeric or word-based parameter names, without changing either parameter. Before the changes, one parameter required a number (or nothing) and the other required a word (or nothing, but it had to be second), which was confusing and inconsistent. A
- @Czar: It would probably be best if it supported both, so all uses of it in archives and so forth would work. Also pinging SMcCandlish, who made the change. Graham87 08:44, 5 March 2017 (UTC)