Template talk:Userbox-level
Colour change
[edit]{{editprotect}} Change the colours for level 0 to the more usual:
- border-c = #FFB3B3
- id-c = #FFB3B3
- info-c = #FFE0E8
OrangeDog (talk • edits) 17:14, 2 October 2009 (UTC)
- The colours shouldn't really be changed as all the existing templates that already use these colours will also then be changed. A better option would be to have a 0a & 0b option so that both sets of colours an be used. -- WOSlinker (talk) 19:01, 2 October 2009 (UTC)
- I've now added that option in the sandbox -- WOSlinker (talk) 19:07, 2 October 2009 (UTC)
0a-0 | 0a version |
0b-0 | 0b version |
- I just haven't seen a userbox that uses the grey colour, most override it to give the red one (as well as changing the level 5 one as well, but there's no common alternative) OrangeDog (talk • edits) 19:49, 2 October 2009 (UTC)
- It's mainly language ones that use grey, for example {{User en-0}} & {{User fr-0}}. -- WOSlinker (talk) 22:10, 2 October 2009 (UTC)
- Fair enough, almost all the programming language ones have messy hacks to make them red. Let's have both then. OrangeDog (talk • edits) 22:13, 2 October 2009 (UTC)
Not done. Please give a complete and specific description of the requested edit; the exact code in question and its proposed replacement. Skomorokh, barbarian 07:24, 4 October 2009 (UTC)
{{editprotected}} Copy the code in the sandbox over to the live template. Thios adds the 0a & 0b levels. -- WOSlinker (talk) 08:13, 4 October 2009 (UTC)
- No problem, done. Cheers, Skomorokh, barbarian 16:23, 4 October 2009 (UTC)
0a and 0b not showing lang-0
[edit]{{editprotect}} Please change the following from:
| id = {{{id}}}{{#switch:{{{level}}}|0|1|2|3|4|5|N=-{{{level}}}|3a|3b=-3|5a|5b=-5}}
to:
| id = {{{id}}}{{#switch:{{{level}}}|0|1|2|3|4|5|N=-{{{level}}}|0a|0b=-0|3a|3b=-3|5a|5b=-5}}
to fix this error. Borgarde (talk) 06:33, 23 November 2009 (UTC)
Done thanks ! —TheDJ (talk • contribs) 15:02, 23 November 2009 (UTC)
nocat
[edit]{{editprotected}} Could the sandbox version be copied over? It adds in the nocat parameter. Thanks. -- WOSlinker (talk) 11:20, 3 January 2010 (UTC)
Done —TheDJ (talk • contribs) 12:13, 3 January 2010 (UTC)
add usercategory3
[edit]{{editprotected}} Can the sandbox version be copied over which adds a usercategory3 option. Thanks -- WOSlinker (talk) 21:21, 13 February 2010 (UTC)
Done —TheDJ (talk • contribs) 02:28, 14 February 2010 (UTC)
Some tweaks to conditionals
[edit]{{editprotected}}
Please sync with the sandbox to add support for passing info-lh
through. Chris Cunningham (not at work) - talk 16:33, 28 April 2010 (UTC)
Done - could you update the documentation? — Martin (MSGJ · talk) 16:58, 28 April 2010 (UTC)
- Done, also fixed the usage so that it validates. Chris Cunningham (not at work) - talk 13:50, 29 April 2010 (UTC)
Forbid linebreak before the level
[edit]How about forbidding a linebreak after the id and before the -level? {{user latex-3}}
and similar ones (where the id is a picture) are awkward otherwise, seeming to indicate a negative level. I'm not sure what markup would suffice (<div>?) and I am not an administrator. — Pt (T) 15:38, 4 July 2010 (UTC)
{{editprotected}}
Easily done. Fixed in sandbox: sync requested. Chris Cunningham (not at work) - talk 10:42, 6 July 2010 (UTC)
Done — Martin (MSGJ · talk) 11:39, 6 July 2010 (UTC)
Allow linebreak before the level
[edit]{{editprotected}}
Orthogonally to the previous topic, I've prepared a change in the sandbox which allows a new optional parameter "level-br", which if used inserts a hard line break instead of the hyphen between the "id" and the "level". The purpose of this is to allow use of this template for cases like {{User simple-4}}, which currently doesn't use this template.
(The simple language templates are a mess, {{User simple-2}} and {{User simple-0}} have seemingly negative levels, {{User simple-4}} and {{User simple-1}} don't use this template and use different colors, and {{User simple-3}} has an ugly linebreak in the middle of the word. I'd like to standardize these to look like {{User simple-4}} but use standard colors, but it would be nice (and easier) to be able to use this template.) --Mepolypse (talk) 20:46, 9 December 2010 (UTC)
Done -- WOSlinker (talk) 23:00, 9 December 2010 (UTC)
Level 0.5
[edit]Wikipedia:Babel | ||||
---|---|---|---|---|
| ||||
Search user languages |
We already have these for language proficiency.
That works fine for me; my competence in these is around 0.5.
But the colours are a problem.
The Russian one is using Native Speaker green.
Can 0.5 be formalized?
Thanks, Varlaam (talk) 19:50, 1 April 2012 (UTC)
en-0.5 | This user is learning English at a basic level and does not understand the language well, if at all. |
Another of these guys. Varlaam (talk)
- I've added level=0.5 -- WOSlinker (talk) 21:13, 1 April 2012 (UTC)
- Wow. When I next need something done with lightning speed ...
- Thanks, Varlaam (talk) 21:17, 1 April 2012 (UTC)
Level 5 should have white text
[edit]![]() | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Because the background colour of level 5 is dark, the foreground should be white, like for Template:User iso15924, for better accessibility. Can someone please add:
| id-fc = {{#ifeq:{{{2|}}}|5|white}}
to the template call? If you could also change the <br>
to <br/>
as well, that would fix the syntax highlighting. Thanks! — OwenBlacker (Talk) 23:02, 17 March 2016 (UTC)
- Similarly, the
|info-c=
colour for Template:User iso15924 is#FFBBBB
, which would provide better accessibility. Ideally, that would also be changed fromFF5555
for switch cases5
and5a
, please. — OwenBlacker (Talk) 23:07, 17 March 2016 (UTC)
Partly done: - I've lightened the backgrounds a little, but not changed the text color. I haven't changed the HTML, since it's the syntax highlighting that's not working correctly, not the HTML which is fine. fredgandt 08:39, 18 March 2016 (UTC)
Edit request to complete TfD nomination
[edit]![]() | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Template:Userbox-level has been listed at Templates for discussion (nomination), but was protected so could not be tagged. Please add:
{{subst:tfm|help=off|1=User lang}}
to the top of the page to complete the nomination. Thank you. Soumya-8974 (he) talk contribs subpages 17:57, 8 December 2020 (UTC)
- To editor Soumya-8974:
done, and thank you very much! P.I. Ellsworth ed. put'r there 20:16, 8 December 2020 (UTC)
Template-protected edit request on 8 December 2020
[edit]![]() | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please wrap the TfD notification in a noinclude tag as it's messing with userbox formatting as of the latest revision. Thanks :) 🎄🎄 Ed talk! 🎄🎄 20:52, 8 December 2020 (UTC)
User:Paine_Ellsworth should remove the notice.--SchizoidNightmares (talk) 21:43, 8 December 2020 (UTC)- I'm pretty sure the noinclude is already there, yet it still appears in the template... Maybe other pages take some time to update, or maybe I'm not understanding what's going on. --SchizoidNightmares (talk) 21:49, 8 December 2020 (UTC)
- To editors Ed and SchizoidNightmares: what's going on is that the user pages that I checked, where this template is transcluded, all show a message in tiny font about the TfD that is still ongoing. That is supposed to happen. The entire TfD template does not appear on user pages, only the tiny information message. The Noinclude module takes care of that. See the template documentation for examples. P.I. Ellsworth ed. put'r there 21:58, 8 December 2020 (UTC)
- What is not supposed to happen though, are these horrendous spaces introduced by the notice, at least for me on Chrome. Until that is fixed, I would suggest removing the notice. Cheers, intforce (talk) 00:48, 9 December 2020 (UTC)
- Same issues for me on Microsoft Edge since the last edit – these huge spacings appear on all User pages with this template. NoNews! 04:47, 9 December 2020 (UTC)
- I attempted a fix, but as it didn't work I reverted myself. Paine Ellsworth this needs to be fixed or the TfD notice will be removed. Everybody's babel is messed up. Mjroots (talk) 06:43, 9 December 2020 (UTC)
- I reverted to before the tag was added. I don't know the reason for this, but having hundreds of thousands of user pages looking bad seems important enough to me to revert this for now. --Muhandes (talk) 07:07, 9 December 2020 (UTC)
- I attempted a fix, but as it didn't work I reverted myself. Paine Ellsworth this needs to be fixed or the TfD notice will be removed. Everybody's babel is messed up. Mjroots (talk) 06:43, 9 December 2020 (UTC)
- Same issues for me on Microsoft Edge since the last edit – these huge spacings appear on all User pages with this template. NoNews! 04:47, 9 December 2020 (UTC)
- What is not supposed to happen though, are these horrendous spaces introduced by the notice, at least for me on Chrome. Until that is fixed, I would suggest removing the notice. Cheers, intforce (talk) 00:48, 9 December 2020 (UTC)
- To editors Ed and SchizoidNightmares: what's going on is that the user pages that I checked, where this template is transcluded, all show a message in tiny font about the TfD that is still ongoing. That is supposed to happen. The entire TfD template does not appear on user pages, only the tiny information message. The Noinclude module takes care of that. See the template documentation for examples. P.I. Ellsworth ed. put'r there 21:58, 8 December 2020 (UTC)
- I'm pretty sure the noinclude is already there, yet it still appears in the template... Maybe other pages take some time to update, or maybe I'm not understanding what's going on. --SchizoidNightmares (talk) 21:49, 8 December 2020 (UTC)
To editors Ed, SchizoidNightmares, intforce, NoNews, Mjroots and Muhandes: the notice on user pages has been disabled with the latest addition of the Tfm template to this template. Of course this means that users who use this template won't be notified of the merge discussion and won't know to weigh in if they want to. You might want to look over the other options for the |type=
parameter at {{Tfm}} to see if there is a better choice other than |type=disabled
. P.I. Ellsworth ed. put'r there 07:32, 9 December 2020 (UTC)
- :Soumya-8974 – courtesy ping since it was your edit that was altered. P.I. Ellsworth ed. put'r there 08:06, 9 December 2020 (UTC)
- If it's a lack of notification you're worried about, I would suggest raising this issue at the talk page of WP:CENT and see if consensus can be gained for an addition there, given the issues raised here. From what I can see, there is not going to be any difference in the look of the babel boxes post-merge, so I'm not that worried about a lack of publicity over this. Appreciate that others may want this to be publicised somehow, hence my suggestion. Mjroots (talk) 07:47, 9 December 2020 (UTC)
- I don't know how different the two merged templates will appear, but yes, editors deserve to be notified of any changes. Also keep in mind that this is a meta-template used inside several babel userboxes, which is why the notification should probably be kept to
|type=tiny
. But that choice relies on the consensus of these involved editors. I remain objective. P.I. Ellsworth ed. put'r there 08:11, 9 December 2020 (UTC)
- I don't know how different the two merged templates will appear, but yes, editors deserve to be notified of any changes. Also keep in mind that this is a meta-template used inside several babel userboxes, which is why the notification should probably be kept to
Template-protected edit request on 8 May 2022
[edit]![]() | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Apply implementation of fakelevel
parameter (diff) from the sandbox. 0xDEADBEEF (T C) 08:33, 8 May 2022 (UTC)
Not done for now: please establish a consensus for this alteration before using the
{{edit template-protected}}
template. If this is a result of discussion elsewhere please provide a link Muhandes (talk) 11:23, 8 May 2022 (UTC)- @Muhandes: I'm not sure if consensus is needed for this. It is just a new parameter which doesn't cause anything to change. The rationale is to support leveled boxes with custom ids. For example Template:User_rust-1 0xDEADBEEF (T C) 11:31, 8 May 2022 (UTC)
- @0xDeadbeef: I believe this is countering the purpose of this template which is to provide some standardization. However, I'm no expert for this template so I'll revert to unanswered and let other template editors voice their opinion. --Muhandes (talk) 11:44, 8 May 2022 (UTC)
- I don't understand what fakelevel would achieve that level can not? — Martin (MSGJ · talk) 19:48, 8 May 2022 (UTC)
Done I've named the parameter
hidden-level
which is clearer, but yes I'm happy with this. User:GKFXtalk 20:54, 8 May 2022 (UTC)
- @Muhandes: I'm not sure if consensus is needed for this. It is just a new parameter which doesn't cause anything to change. The rationale is to support leveled boxes with custom ids. For example Template:User_rust-1 0xDEADBEEF (T C) 11:31, 8 May 2022 (UTC)
Template-protected edit request on 2 July 2022
[edit]![]() | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change
<!--
# Track the existence of level-zero templates
-->{{Template other|{{#ifeq: {{{level|}}}|0|[[Category:Level-zero userbox templates]]}}}}
to
<!--
# Track the existence of level-zero templates
-->{{Template other|{{#switch: {{{level|}}}|0|0a|0b=[[Category:Level-zero userbox templates]]}}}}
Thanks! —CX Zoom[he/him] (let's talk • {C•X}) 08:55, 2 July 2022 (UTC)
Done -- WOSlinker (talk) 10:29, 2 July 2022 (UTC)
Template-protected edit request on 30 August 2023
[edit]![]() | This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I am allowed to pass Semi Protect (see more) but not allowed to pass Template Protect. I would like to change that. Yxisx (talk) 15:33, 30 August 2023 (UTC)
Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. – Jonesey95 (talk) 16:01, 30 August 2023 (UTC)