Module talk:WikiProject banner/Archive 9: Difference between revisions

Content deleted Content added
SmackBot (talk | contribs)
m Subst: {{unsigned}} (& regularise templates)
MiszaBot II (talk | contribs)
m Archiving 2 thread(s) from Template talk:WPBannerMeta.
Line 101:
 
:There are some portal features in {{tl|WikiProject Comics}}, {{tl|WikiProject Aviation}} and {{tl|WikiProject China}}. Would any of them work as a starting point which could then be customised further to meet your needs? -- [[User:WOSlinker|WOSlinker]] ([[User talk:WOSlinker|talk]]) 22:00, 22 August 2010 (UTC)
== file vs. image, still both categories out there, some within the same project ==
 
I'm not quite sure how this ended up, but is the {{tl|class mask}} for FQS now defaulting to "File-Class", instead of "Image-Class", or are both still implementing, with a yes/no parameter required? Just wondering, because several projects have both categories out there, like: [[:Category:File-Class rail transport articles]] and [[:Category:Image-Class rail transport articles]]. I'm wondering if I should redirect the Image cat to the File cat, or does the {{tl|WikiProject Trains/class}} page (which is protected) need to be corrected instead? Thanks, --[[User:Funandtrvl|Funandtrvl]] ([[User talk:Funandtrvl|talk]]) 00:25, 2 September 2010 (UTC)
:That is (just guessing) most likely caused by the images int he later category still calling it "images" and only showing File superficially on the front-end, compared to former category actually using "file", Although that probably should get fixed, it would caused a lot of empty categories I would be guessing, and a far bit of load changing all those categories around. [[User:Peachey88|Peachey88]] <sup>([[User_Talk:Peachey88|T]]<span style="font-weight:bold;">&nbsp;·</span>&#32; [[Special:Contributions/Peachey88|C]])</sup> 01:59, 2 September 2010 (UTC)
 
:See [[WP:RIF]]/[[WT:RIF]]. Those are the last few stragglers... –[[user:xeno on an iPhone|<font face="verdana" color="black">'''xeno'''</font>]][[user talk:xeno|<font color="black"><sup>talk</sup></font>]] 02:35, 2 September 2010 (UTC)
:Yes, you're right. Since July the class mask is defaulting to File-class. I regard this sluggish movement of pages between categories as a bug. The majority moved over fairly quickly, but I don't think the job queue can be blamed for the others taking so long. &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 19:53, 2 September 2010 (UTC)
 
::Marvelous, I didn't realise this was finally being done. :) I was only aware of the "no concensus" outcome of the initial CfD. [[User:PC78|PC78]] ([[User talk:PC78|talk]]) 12:23, 18 September 2010 (UTC)
 
== Case sensitivity of parameter names ==
 
I was just trying to assign an article a wikiproject class. I have done this several times and would have thought it could be a fairly intuitive exercise, having read the criteria for assigning articles. But to get the 4 permutations of upper and lower cases of "Class" and the letter signifying the value right took me... yees, you guesssed it, 4 goes. And then there was getting the order of the quality and importance right to please the templates.
 
I presume there's a master template for the plethora of minor wikiproject categorization templates (many unfilled, perhaps not helped by this tediousness). Wouldn't some template wiz feel great about disposing of unnecessary case (and order) sensitivities to help move this along a bit smoother? <span style="font-family: 'Brush script MT', cursive;font-size:1.4em;vertical-align:middle;"> [[User:Trev M|Trev M ]]&nbsp;[[User_talk:Trev_M|~&nbsp;]]</span> 12:38, 3 September 2010 (UTC)
:Suggest this at [[Template talk:WPBannerMeta]]. –[[user:xeno|<font face="verdana" color="black">'''xeno'''</font>]][[user talk:xeno|<font color="black"><sup>talk</sup></font>]] 17:51, 3 September 2010 (UTC)
::Always good to get a bit nearer to the business end of things&nbsp;– thanks Xeno.
 
So, here's that thead copied to here. Any thoughts? <span style="font-family: 'Brush script MT', cursive;font-size:1.4em;vertical-align:middle;"> [[User:Trev M|Trev M ]]&nbsp;[[User_talk:Trev_M|~&nbsp;]]</span> 19:24, 3 September 2010 (UTC)
 
:This can't be done at WPBannerMeta. It needs to be done at all the individual project banners. For example replacing
<pre>
|class={{{class|}}}
</pre>
:with
<pre>
|class={{{class|{{{Class|}}}}}}
</pre>
:would then mean that it works with class= and Class= . -- [[User:WOSlinker|WOSlinker]] ([[User talk:WOSlinker|talk]]) 19:31, 3 September 2010 (UTC)
::I notice the words "getting the order of the quality and importance right to please the templates" in your original post. I'd like to mention that since {{para|class}} and {{para|importance}} are ''named'' parameters, the order in which they are given is completely immaterial (see [[Help:Template#Templates with named parameters|here]]).
::What matters is that both the spelling and capitalisation of the parameter names should be exactly as per the template's documentation. Further, the same named parameter cannot occur twice: for example, if you put
:::<code><nowiki>{{WikiProject Tulips |class=c |importance=low |class= }}</nowiki></code>
::the second {{para|class}} overrides the first, so the talk page goes in the "unassessed tulips articles" category.
::Most, if not all, project banners are completely tolerant about the capitalisation of parameter ''values''; so {{para|class|c}} is treated as if it were {{para|class|C}}; but I don't know of any that would allow {{para|Class|C}}. There seems to be a convention that parameter names are almost always entirely lowercase, with the capitalised form only used for proper names: for example, {{tlx|WikiProject Trains}} has {{para|Scotland}}, but not {{para|scotland}}. --[[User:Redrose64|<span style="color:#d30000; background:#ffeeee">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 21:02, 3 September 2010 (UTC)
:::I don't think this is an issue; template parameters are generally assumed to be lower-case. Changing them to recognize upper-case and lower-case (i.e., {{code|1=class=}} versus {{code|1=Class=}}) has no purpose, in my opinion. <font style="font-family: 'Times New Roman'">[[User:Intelligentsium|<span style="color:#013220">Intelligent</span>]]'''[[User_talk:Intelligentsium|<span style="color:Black">sium</span>]]'''</font> 00:15, 4 September 2010 (UTC)
:::The parameter is lower case but the value is not. It's correct to have class=C. I also don't think it's an issue but perhaps some WikiProjects have an issue like the above Scotland= example WikiProject Trains. Regards, [[User:SunCreator|SunCreator]] <sup>([[User talk:SunCreator|talk]])</sup> 00:26, 4 September 2010 (UTC)
::::It is only an issue at WP banner templates that use the upper case for parameters, and don't remember to double-code it to take both uc and lc characters. Maybe this could be pointed out in the TF setup instructions, somewhere? --[[User:Funandtrvl|Funandtrvl]] ([[User talk:Funandtrvl|talk]]) 20:19, 7 September 2010 (UTC)
:::::The original poster is not complaining about case-sensitivity of parameter values, but of parameter names. Most WP banners have at least five parameters - the standard-ish ones being {{para|category}}, {{para|class}}, {{para|importance}}, {{para|listas}}, {{para|small}}; and I don't know of any banner templates that are coded to allow variants on these five such as {{para|Class}}.
:::::On the other hand, the ''values'' of these five are normally passed through to {{tlx|WPBannerMeta}} completely unaltered, which handles all five in a largely case-insensitive manner; so {{para|class|c}} is identical in effect to {{para|class|C}} whatever the banner. --[[User:Redrose64|<span style="color:#d30000; background:#ffeeee">Red</span>rose64]] ([[User talk:Redrose64|talk]]) 20:35, 7 September 2010 (UTC)