Module talk:WikiProject banner/Archive 3

Archive 1

Archive 2

Archive 3

Archive 4

Archive 5

→

Archive 10

Padding

User:PC78 reports that Template:WikiProject Korea/sandbox looks like this on his/her browser (Internet Explorer):

I thought this padding issue had been resolved? Martin 00:09, 2 January 2009 (UTC)

Me too, but then again I use a proper browser :D.  Fixed Happy‑melon 11:23, 2 January 2009 (UTC)

Looks better. Cheers! PC78 (talk) 12:29, 2 January 2009 (UTC)

WikiProject Merseyside

I've attemted a conversion of this project's banner at Template:WikiProject Merseyside/sandbox. It all looks good to me, but can someone more familiar with the meta cast an eye over it? I'd like to be sure before I switch the code over, and avoid any potential screw-ups. Thanks in advance! Small-town hero (talk) 22:17, 2 January 2009 (UTC)

Looks pretty good! But the colour of the Wikipedia:WikiProject Merseyside/Collaboration link suggests to me that you are not using this collaboration of the month thing, so maybe these should be fixed or removed? Ditto for Wikipedia:WikiProject Merseyside/Merging. As you are using so many of the extended quality classes, I might suggest that it would be simpler to use them all and do away with the custom class that you have created. Regards, Martin 23:33, 2 January 2009 (UTC)

I dunno, I'd prefer to keep things as they are in the current template - they can always be dealt with later. This is still a relatively new WikiProject after all. :) Since everything seems to be in order I'm going to go ahead with the switch. Cheers! Small-town hero (talk) 01:49, 3 January 2009 (UTC)

Another Padding Comment

Module:WikiProject banner/doc
This page is a soft redirect.

Module:WikiProject banner/doc
This page is a soft redirect.

There's a little bit of a difference with the border on the left when comparing the WPBannerMeta and Tmbox template. Should a bigger left border be added to WPBannerMeta? -- WOSlinker (talk) 13:20, 2 January 2009 (UTC)

I don't think the border should be bigger necessarily. But perhaps it ought to be the same as the border on the right, which it currently isn't (on my browser anyway). Martin 16:16, 2 January 2009 (UTC)

The main difference is that the quality/importance rows have backgrounds that fill the entire cell; IMO it looks a bit wierd having a huge border between them and the banner border. I agree that the right image should have the same padding as the left image, I'll have a look at that. Happy‑melon 16:38, 2 January 2009 (UTC)

I synchronised the padding left and right. What do people think about it overall? Happy‑melon 18:38, 3 January 2009 (UTC)

Looks better now that left & right match. Not too bothered about matching with tmbox. -- WOSlinker (talk) 19:22, 3 January 2009 (UTC)

Infobox parameter

So far as I can tell, the infobox parameter will always display the following text:

This page has been marked as needing an infobox.

Is it possible to have it use "article" instead of "page" where appropriate (to make it consistant with other uses of article/page/whatever in the banner)? Also, would it be possible to define custom text and even images for this parameter? This could be useful for a WikiProject to link to a specific template or page, for example. PC78 (talk) 02:11, 3 January 2009 (UTC)

It looks like there are two occurences of {{ns:0}} in WPBannerMeta/core that need changing to {{ns:1}} to fix the article/page issue. If you want to use more options for the infobox then there is always the option to use the note 1 parameters instead.

|note 1 = {{{needs-infobox|}}}
 |NOTE_1_TEXT     = This {{#switch:{{NAMESPACE}}|{{ns:0}}=article|page}} has been marked as needing an [[Template:Tulip Infobox|infobox]].
 |NOTE_1_IMAGE    = Nuvola apps arts.png
 |NOTE_1_CAT      = Tulip articles needing infoboxes. 

-- WOSlinker (talk) 10:50, 3 January 2009 (UTC)

What if notes 1-5 are already used? Is it possible to specify more? PC78 (talk) 13:17, 3 January 2009 (UTC)

There's a |HOOK_NOTE= parameter which can be used to add further notes. See example below: -- WOSlinker (talk) 13:44, 3 January 2009 (UTC)

{{WPBannerMeta
|PROJECT          = Tulips
 |small  = {{{small|}}}
 |category={{{category|¬}}}
 |listas = {{{listas|}}}
|note 1 = {{{audio-file|}}}
 |NOTE_1_TEXT     = An audio file has been created of this article.
 |NOTE_1_IMAGE    = Nuvola apps arts.png
 |NOTE_1_CAT      = Tulip articles with audio files
|note 5 = {{{infobox|}}}
 |NOTE_5_TEXT     = An infobox needs to be added to this article.
 |NOTE_5_IMAGE    = Diamond-caution.svg
 |NOTE_5_CAT      = Tulip articles without infoboxes
|HOOK_NOTE={{WPBannerMeta/hooks/notes
 |category={{{category|μ}}}
 |note 1={{{navbox|}}}
  |NOTE_1_TEXT          = An navbox needs to be added to this article.
  |NOTE_1_IMAGE         = Diamond-caution.svg
  |NOTE_1_CAT           = Tulip articles without navboxes
 |note 5={{{otherbox|}}}
  |NOTE_5_TEXT          = An otherbox needs to be added to this article.
  |NOTE_5_IMAGE         = Diamond-caution.svg
  |NOTE_5_CAT           = Tulip articles without otherboxes
 }}
}}

Gotcha. Cheers! PC78 (talk) 17:35, 3 January 2009 (UTC)

Another article/page issue

Could the WPBannerMeta/importancescale be altered so that "This article has been" is changed to "This {{#if:{{SUBJECTSPACE}}|page|article}} has been", so that it matches WPBannerMeta/qualityscale. Thanks. -- WOSlinker (talk) 12:47, 3 January 2009 (UTC)

 Done Happy‑melon 17:07, 3 January 2009 (UTC)

A couple of things...

1. Could the text for NA quality be changed to "This page is not an article and does not require a rating on the quality scale.", as per other non-article classes and NA importance? This would be useful where NA-Class is used in the article space in lieu of Disambig-Class or Redirect-Class.
2. When NA quality is used in the article space, the forced comment message is suppressed. Would it be possible/desirable to suppress the forced message for other non-standard quality grades as well?

Cheers! PC78 (talk) 17:50, 3 January 2009 (UTC)

Point 1 has now been fixed I believe. I don't quite understand point 2: what do you mean by "forced comment message"? Martin 18:32, 3 January 2009 (UTC)

The "please leave comments here..." message that appears if no comments exist and |COMMENT_FORCE= is set. Now disabled for Redirects and Disambigs. Any others? Happy‑melon 18:38, 3 January 2009 (UTC)

Thanks for that. PC78 (talk) 19:11, 3 January 2009 (UTC)

Collapsed section

In the Collapsed section, |c note 1= & |c note 2= don't work as there are two spaces missing from WPBannerMeta/core.

Could the following be changed from

{{#if:{{{COLLAPSED_TEXT|}}}{{#switch:{{{c note1|}}}{{{c note2|}}}{{{c note 3|}}}{{{c note 4|}}}{{{c 
note 5|}}}||¬|¬¬|¬¬¬|¬¬¬¬|¬¬¬¬¬=|yes}}

to

{{#if:{{{COLLAPSED_TEXT|}}}{{#switch:{{{c note 1|}}}{{{c note 2|}}}{{{c note 3|}}}{{{c note 4|}}}{{{c 
note 5|}}}||¬|¬¬|¬¬¬|¬¬¬¬|¬¬¬¬¬=|yes}}

Thanks. -- WOSlinker (talk) 23:37, 3 January 2009 (UTC)

Oops, that was this edit. Well spotted WOSlinker (what is a WOS linker?) Martin 09:17, 4 January 2009 (UTC)

Well spotted.  Fixed Happy‑melon 10:17, 4 January 2009 (UTC)

Well, WOS stands for World of Spectrum. When I first started, I was just adding links to a number of computer games articles. But since then I done a few other things. -- WOSlinker (talk) 11:44, 4 January 2009 (UTC)

You certainly have :) Martin 12:06, 4 January 2009 (UTC)

B-class checklist niggle

If none of the B-class checklist parameters are used, then the following is displayed:

| b1 <!--Referencing & citations--> = <yes/no>
| b2 <!-- Coverage and accuracy --> = <yes/no>
| b3 <!-- Structure             --> = <yes/no>
| b4 <!-- Grammar and style     --> = <yes/no>
| b5 <!-- Supporting materials  --> = <yes/no>
| b6 <!-- Accessible            --> = <yes/no>

However, not all projects use the same parameters (for example, some use B-Class-1, B-Class-2, etc.) so this may be incorrect. I was just thinking that Talk:East Prussia might really confuse someone who is trying to rate it as B-class. Martin 11:57, 4 January 2009 (UTC)

Ouch! I can see the issue, but I think trying to play with the default message is asking for a world of pain with optional parameters flying everywhere. Isn't the simplest method to make sure each banner supports this set of parameters, whatever their 'primary' parameters may be? Happy‑melon 13:28, 4 January 2009 (UTC)

Yes, maybe, but that will involve updating all banners which use the checklist which could also be very painful! Martin 13:34, 4 January 2009 (UTC)

There aren't actually that many of them. Happy‑melon 16:01, 4 January 2009 (UTC)

Okay, this should be possible then. Shall we just change any non-standard ones to

|b1={{{B-Class-1|{{{b1|}}}}}}

etc. I've noticed some using B1, B2, etc. I suppose parameters are case=sensitive? Martin 17:48, 4 January 2009 (UTC)

Yes, that looks good. Parameter names are case-sensitive, although the parameter values are not. Happy‑melon 17:51, 4 January 2009 (UTC)

Huh? That doesn't sound right. Parameter values are case-sensitive, otherwise we wouldn't need to use constructs such as {{lc:{{{class}}} }}. Martin 10:30, 5 January 2009 (UTC)

Sorry, I meant that parameter values are case-insensitive because we use the lc: construct everywhere :D. There's no equivalent construct to make parameter names case insentitive, unfortunately. Happy‑melon 10:38, 5 January 2009 (UTC)

 Done. All banners using the checklist have been fixed, and the documentation has been updated to prevent this problem in the future. Martin 16:06, 5 January 2009 (UTC)

class=Image

Would it be possible for class=Image to also recognize class=File after our namespace change? Just a thought. §hep • ¡Talk to me! 22:19, 5 January 2009 (UTC)

Yes :D  Done Happy‑melon 22:55, 5 January 2009 (UTC)

Thanks. §hep • ¡Talk to me! 23:18, 5 January 2009 (UTC)

listas={{{listas|}}}

It says in the template doc that listas={{{listas|}}} is required for the template to work. I was wondering if this changes means that {{OH-Project}} needs updated to include this? Is this a recent thing? I don't remember it always being required or even existent. §hep • ¡Talk to me! 19:59, 22 December 2008 (UTC)

This functionality should really be included in all banners, notwithstanding the fact that it is currently broken :D. I am waiting on a MediaWiki configuration change (Template:Bug) to make it possible to use this system efficiently. But there's no reason not to include it. The banner isn't going to explode if you don't use this feature, but equally it's not going to do any harm if you do. You don't even have to document it if you don't want to encourage its use. Happy‑melon 13:30, 23 December 2008 (UTC)

If you could include it that'd be great and I'd be more than happy to doc it. I just can't touch the template in its current state... Thanks. §hep • ¡Talk to me! 21:06, 25 December 2008 (UTC)

 Done Happy‑melon 21:41, 25 December 2008 (UTC)

Thanks. §hep • ¡Talk to me! 21:41, 25 December 2008 (UTC)

I have found a number of instances where the WP Greece banner does explode if it does not have a value for the listas parameter but a banner above it, especially WP Biography, does have a value for the listas parameter. It is not a pretty sight.

I firmly believe that all banners should use the listas parameter, rather than the hodge-podge that now exists. I further believe that all banners should have nested=yes.

Although I am working to clean it out Category:Pages with DEFAULTSORT conflicts may have examples of the above. Within the last 12 hours a bot has completed the listas parameter in only the WP Biography template. See what a mess can be made.

JimCubb (talk) 16:27, 6 January 2009 (UTC)

The |nested= parameter is completely superfluous on WPBannerMeta banners; you can include or not include it at your pleasure, but if you experiment you'll see that it has no effect whatsoever: moving a WPBannerMeta banner inside a banner shell collapses it automagically. As for listas, note that this functionality is currently somewhat broken (see #listas functionality below; we're waiting on a MediaWiki configuration change that will make it much easier to fix listas conflicts both here and with other banners. Your comments in that thread would be very much appreciated. Happy‑melon 16:35, 6 January 2009 (UTC)

listas functionality

On the to-do list, there is check listas functionality.

It looks to me as it's not quite doing which it should be. Although there is some code in WPBannerMeta/core which does {{#if:{{{listas|}}}|{{DEFAULTSORT:{{{listas}}}}} }}, anywhere that a category is set, it is overriding the default sort with the {{PAGENAME}} value. For example [[Category:{{{MAIN_CAT}}}|{{PAGENAME}}]]

I think if {{#if:{{{listas|}}}|{{DEFAULTSORT:{{{listas}}}}} }} was moved from WPBannerMeta/core to WPBannerMeta and then in WPBannerMeta listas was passed to core as |listas = {{{listas|{{PAGENAME}}}}} and also the listas parameter passed through to the other subpages as well, then category setting code could be changed to override to the listas value, For example [[Category:{{{MAIN_CAT}}}|{{{listas}}}]]

Would that be better?

-- WOSlinker (talk) 19:20, 5 January 2009 (UTC)

The todo should probably be "fix listas functionality", it is currently as you say completely broken. I'm actually waiting for Template:Bug, which will make the whole issue a hell of a lot easier (we'd just need to remove the sortkeys altogether). The solution you propose would fix the problem, but it would require passing parameters around that will become superfluous in the (hopefully) near future. I can 'fix' it if there's a pressing need for it, but I'm not aware of many projects that actively use this feature at the moment... Happy‑melon 20:04, 5 January 2009 (UTC)

No pressing need, although if you moved the {{#if:{{{listas|}}}|{{DEFAULTSORT:{{{listas}}}}} }} bit from core into the main template, there wouldn't be any need to pass listas over to core. -- WOSlinker (talk) 20:29, 5 January 2009 (UTC)

On the contrary, you'd have to pass 'listas', defaulting to {{PAGENAME}}, everywhere you wanted a category, so it could be specified as a sortkey. It would be messy :D Happy‑melon 22:51, 5 January 2009 (UTC)

I'm meaning after Template:Bug is fixed. -- WOSlinker (talk) 19:05, 6 January 2009 (UTC)

Ah, I see. Then yes, as you say, after the bug is fixed it will be very easy; move the listas code as you say, and remove all the sorkeys from all the subtemplates. Happy‑melon 20:02, 6 January 2009 (UTC)