Module talk:WikiProject banner/Archive 12

Archive 5

←

Archive 10

Archive 11

Archive 12

Archive 13

Archive 14

Hooking an alerts template into the project banner

So, I created Template:WikiProject Louisville/alertshook. It requires no parameters. Now, how do I hook this into the bottom of my project banner? I already tried "HOOK_BOTTOM= alertshook" and other variations, but nothing works. Please help. Stevie is the man! ^{Talk • Work} 20:44, 15 December 2008 (UTC)

You'd need to use |HOOK_NOTE={{WikiProject Louisville/alertshook}}, to transclude the template into the banner. Happy‑melon 21:16, 15 December 2008 (UTC)

Doesn't work. The template doesn't show up, and it messes up the format of the rest of the banner. Note that this alerts template is included in other banners with no issue. Stevie is the man! ^{Talk • Work} 21:24, 15 December 2008 (UTC)

Oh of course, sorry. Essentially the issue there is that the hook parameters are designed to allow you to do just about anything, which means you have to do just about everything :D. That means that you need to define a new table row, a new table cell within that row, enter the alert message, then close the cell, then close the row. The parameter |BOTTOM_TEXT= is better suited to what you want to do, since it does all that for you: anything you put into that parameter will display in a full-width row across the bottom of the banner. I see it's already used for something in {{WikiProject Louisville}}, but you might want to repurpose it. Happy‑melon 21:48, 15 December 2008 (UTC)

And it would be nice if that parameter actually worked :D I'll try and work out what's wrong there... Happy‑melon 21:50, 15 December 2008 (UTC)

 Fixed Sorry to run you round in circles like that! Happy‑melon 21:52, 15 December 2008 (UTC)

Thanks! I had meant to use BOTTOM_TEXT but it stopped working. So I'll go back to using that now instead of a hook. Stevie is the man! ^{Talk • Work} 23:40, 15 December 2008 (UTC)

Peer Review Hook

The peerreview hook currently doesn't work with the category parameter as it's not used in the template. I've done a sandbox version that fixes that and also shows up on the template design page as well. I've done a sample banner so you can see it working. If it all looks ok, could someone copy it over to the live template. -- WOSlinker (talk) 17:23, 17 January 2009 (UTC)

{{editprotected}} Could someone copy over Template:WPBannerMeta/hooks/peerreview/sandbox to Template:WPBannerMeta/hooks/peerreview. Thanks. -- WOSlinker (talk) 18:38, 19 January 2009 (UTC)

Not done for now: Hi, this may be a design feature, but could you explain why the sandbox is double the length and seems a lot more complex than the current version? And what's with the "TemplatePage" and "Live" version comments? Sorry, but I'm not familiar with these templates, and I want to double-check that we're not breaking anything.--Aervanath (talk) 16:59, 21 January 2009 (UTC)

{{WPBannerMeta/hooks/qualimpintersect}} and "category="

The {{WPBannerMeta/hooks/qualimpintersect}} hook doesn't seem to respond properly to the "category=no" option. Even when this option is set the template still produces the intersected quality/importance intersections. See for example the {{physics}} template used on Wikipedia:WikiProject_Physics/Taskforces/Relativity. Anybody with more knowledge of the code know why?. (TimothyRias (talk) 17:02, 5 May 2009 (UTC))

 Fixed Happy‑melon 17:19, 5 May 2009 (UTC)

qualimpintersect New Param

{{editprotected|Template:WPBannerMeta/hooks/qualimpintersect}}

Could the qualimpintersect templates be changed to add support for a SUPPRESS_NA_CLASS which will stop the Quality/Importance Insersect category from being added to an article when |SUPPRESS_NA_CLASS=yes and |class=NA. The changes are in the sandboxes below:

• Template:WPBannerMeta/hooks/qualimpintersect/sandbox
• Template:WPBannerMeta/hooks/qualimpintersect/core/sandbox

Thanks. -- WOSlinker (talk) 19:03, 23 September 2009 (UTC)

 Done Happy‑melon 19:13, 23 September 2009 (UTC)

BANNER_NAME on /cats

I'm trying to work out whether it is really necessary to pass the BANNER_NAME parameter to the /cats hook. As the cat n parameters will be empty on the template page, it seems this could just be removed? — Martin (MSGJ · talk) 08:40, 18 April 2010 (UTC)

I would have thought the same but have a look at the use on Template:WikiProject Formula One and Template:WikiProject Cue sports. -- WOSlinker (talk) 09:33, 18 April 2010 (UTC)

Ah, I see what you mean. So what we could do is point out on the documentation that is it not required in normal cases? And I think we can simplify the code slightly by using the "and not" logical operator - could you check my code on Template:WPBannerMeta/hooks/cats/sandbox? — Martin (MSGJ · talk) 14:39, 18 April 2010 (UTC)

That looks ok. -- WOSlinker (talk) 16:06, 18 April 2010 (UTC)

Increase notes to 10?

Is there any reason not to support 10 notes on /notes? — Martin (MSGJ · talk) 14:42, 18 April 2010 (UTC)

None that I can think of. -- WOSlinker (talk) 16:08, 18 April 2010 (UTC)

 Done — Martin (MSGJ · talk) 11:41, 20 April 2010 (UTC)

bchecklist

• Perhaps moving the class check to outer template might be simpler. Suggested code is on Template:WPBannerMeta/hooks/bchecklist/sandbox. I've tweaked a few other things as well. Any comments? — Martin (MSGJ · talk) 16:37, 5 May 2010 (UTC)

  I don't have any opinion on item 1, don't mind either way. -- WOSlinker (talk) 18:06, 5 May 2010 (UTC)

  I think the only practical difference is that the check for whether the checklist is displayed uses pre-normalised values. Therefore it is possible to differentiate between a blank input and something like <yes/no>, which normalise to the same. It's hardly important but I think if someone fills in the parameters using the copy/paste table (i.e. with <yes/no>) then it would be helpful if the checklist displayed. — Martin (MSGJ · talk) 18:36, 5 May 2010 (UTC)

   Done — Martin (MSGJ · talk) 11:47, 6 May 2010 (UTC)

• Is there a way to mimic the formatting of <pre> without using <pre>? This would make it easier to manipulate the copy/paste code. — Martin (MSGJ · talk) 16:50, 5 May 2010 (UTC)

  For item 2, can use the source tag instead of the pre tag, although that's very similar. Another option would be a div tag with the style set to all the bits used in pre but I've not quite got the multiple spaces to work. -- WOSlinker (talk) 18:06, 5 May 2010 (UTC)

  I would like parser functions to work inside the environment, so your div is the best of those I think. — Martin (MSGJ · talk) 18:40, 5 May 2010 (UTC)

  I've improved the formatting by using non-breaking spaces. But it's taking up a bit too much space and the line-height property doesn't seem to make any difference. — Martin (MSGJ · talk) 22:10, 5 May 2010 (UTC)

  I've tweaked the div settings and it's all appearing to work now. -- WOSlinker (talk) 22:15, 5 May 2010 (UTC)

  Not for me. Can you work out how to reduce the line spacing in /testcases? — Martin (MSGJ · talk) 11:14, 6 May 2010 (UTC)

  Poke ... — Martin (MSGJ · talk) 15:32, 11 May 2010 (UTC)

  Sorry, hadn't seen that last message. Anyway, I've fixed the line-spacing by removing all carriage returns inside the section. The font was also a bit bigger than before, so I've changed it from 88% to 80%. -- WOSlinker (talk) 17:41, 11 May 2010 (UTC)

  Sweet. I think that code is ready to go now, if you don't mind taking a quick check. — Martin (MSGJ · talk) 20:54, 12 May 2010 (UTC)

pre

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

source

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

div

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

• How about a DISPLAY_ON_START parameter so that it is not necessary to check the output of the banner's class subpage? — Martin (MSGJ · talk) 16:52, 5 May 2010 (UTC)

  And for item 3, yes, that seems simpler than what is done at current. -- WOSlinker (talk) 18:06, 5 May 2010 (UTC)

  Added to /sandbox code - can you check? I guess a tracking category will be needed to find the uses which need this parameter. Or do you happen to know which ones? — Martin (MSGJ · talk) 18:38, 5 May 2010 (UTC)

  The only one I know of off hand is Template:WPAVIATION, but there may be others. -- WOSlinker (talk) 22:07, 5 May 2010 (UTC)

  This parameter now implemented. I've added it to WPAVIATION and added a tracking category to find any others. — Martin (MSGJ · talk) 11:48, 6 May 2010 (UTC)

• How about adding parameters CRITERION_1 to customise the text for each parameter? That would allow Template:WikiProject Cricket/bchecklist to use this template. — Martin (MSGJ · talk) 06:16, 8 May 2010 (UTC)

  Since it's only one project that would need this feature, is it worth adding? Altohugh a differnet option could be BCHECKLIST_CORE to specify a different core template rather than having CRITERION_1 to CRITERION_6 as the other difficulty is formatting the layout of the pre section correctly. -- WOSlinker (talk) 08:36, 8 May 2010 (UTC)

  I guess you're right. If it's only that project which is likely to need it, then we don't need to add it. Same logic for BCHECKLIST_CORE, I suppose, unless there are any others which could use that. — Martin (MSGJ · talk) 15:31, 11 May 2010 (UTC)

• Toying with moving the check for whether the copy/paste code is displayed onto the main template with a SHOW_SYNTAX parameter. That would allow <yes/no> to be interpreted differently to a blank input. — Martin (MSGJ · talk) 18:10, 13 May 2010 (UTC)

taskforces

I think there are several projects which will inherit the overall importance for taskforces if no specific importance is specified. However it is often not desirable to show "rated XXX-importance" if this happens, so this means that the default text cannot be used, which in turn means the importance can't be normalised before displaying. I wonder if an inherited importance feature might be worth adding to the taskforces hook to fix this problem. — Martin (MSGJ · talk) 18:14, 13 May 2010 (UTC)

Any good examples? -- WOSlinker (talk) 20:37, 13 May 2010 (UTC)

Template:WPMED and Template:WikiProject Canada are two that spring to mind. Or perhaps it would be better to add an option so that the TF_TEXT can be specified but the importance rating can still be appended to it. — Martin (MSGJ · talk) 20:47, 13 May 2010 (UTC)

That seems sensible to allow TF_TEXT & importance to work together. -- WOSlinker (talk) 22:51, 13 May 2010 (UTC)

So how about one or both of the following features?

• |DISPLAY_IMPORTANCE= - a parameter to control whether the importance rating is appended to the taskforce text.
  • |DISPLAY_IMPORTANCE=yes - append
  • |DISPLAY_IMPORTANCE=no - don't append
  • blank or undefined - current behaviour (i.e. if the default text is used then "yes" otherwise "no")
• |inherit importance={{{importance|}}} - if this is defined then if taskforce importance is used but not currently rated, then the overall importance will be applied?

— Martin (MSGJ · talk) 05:09, 14 May 2010 (UTC)

Note to self: Template:WikiProject Football also uses a system of inherited importance. — Martin (MSGJ · talk) 10:07, 8 June 2010 (UTC)

I believe the code for the first phase of this change (implemented inherited importance) is about ready to deploy. The changes are in:

• /sandbox
• /core/sandbox (just needs the code for tf1 copying down for 2-10)

There are also two new subtemplates:

• /taskforce
• /templatepage

Any comments welcomed. There are a few tests on /testcases. The code is significantly simplified by using a separate /templatepage. And the custom code can be removed from the main /taskforce template once this is deployed. — Martin (MSGJ · talk) 11:48, 17 June 2010 (UTC)

 implemented. — Martin (MSGJ · talk) 14:39, 18 June 2010 (UTC)

I'm thinking about a couple of possible adjustments:

1. Should the decision whether to use inherited importance check the ASSESSMENT_CAT parameter rather than the importance parameter? Currently some of the {{WikiProject Canada}} task forces use the generic importance and don't even have a parameter for a custom importance. This currently means that all the tf n importance parameters have to be passed blank which is not very tidy.
2. Should |tf n importance=sausage be interpreted the same as a blank parameter? This would help {{WikiProject Football}} where the task force parameter doubles as the importance parameter (and so "yes" should be ignored).

— Martin (MSGJ · talk) 19:35, 19 June 2010 (UTC)

@MSGJ: Besides Football, I've found three (Cryptography, Databases, Java) that use inherited importance, but a different method - these three use code like this:

 |tf 2 importance={{#if:{{{computer-science-importance|}}}|{{{computer-science-importance}}}|{{{importance|}}}}}<!-- Inherit importance if not specified -->

- they don't use {{WPBannerMeta/hooks/taskforces}} so there is no |inherit importance= parameter to be filled in. --Redrose64 (talk) 16:06, 19 May 2016 (UTC)

Collapsed

I'm proposing an option to display the header of a collapsed section even if the section does not collapse. This is needed for a banner which I'm working to convert. There is some code on /collapsed/sandbox which adds a DISPLAY_HEAD parameter. Any comments please. — Martin (MSGJ · talk) 15:38, 9 July 2010 (UTC)

Is the todolist option of any use?

Take a look at Special:WantedPages. Currently, an absurdly high proportion of the top links are from {{Northern Ireland tasks}} via {{WikiProject Northern Ireland}}. Is there some way to disable this link farm? More fundamentally, is there any benefit from having a TODO list on 'every Talk page in a project, especially when it's usually collapsed? What is the benefit of, say, Talk:Bonar Law having a deeply-buried redlink to Sophie Hoopman? jnestorius^(talk) 14:25, 10 December 2010 (UTC)

Many projects choose to have to-do lists as part of their project banner (looking at [1] will give you some idea of the number). It is likely that these projects think they are useful, otherwise they probably wouldn't use it. As for the red links, is there any harm in having them there? Would you be concerned if they were blue links? — Martin (MSGJ · talk) 14:55, 10 December 2010 (UTC)

As the name suggests, Special:WantedPages is intended to list redlinks. That said, since this issue is at least four years old, I guess it's best to just give up on Special:WantedPages. jnestorius^(talk) 19:06, 10 December 2010 (UTC)

You could put in a request at Wikipedia talk:Database reports for a report which showed only red-links in the article space where the links also came from articles. -- WOSlinker (talk) 19:13, 10 December 2010 (UTC)

Category for articles marked with todo

I think this hook could be tremendously useful, if the hook would also put the articles with todo lists into a category, as Tulips articles with todo. That would allow the project members to figure out which articles have been marked by this hook. Unless there is some other mechanism I don't know of. Thanks! --Codrin.B (talk) 20:51, 4 January 2011 (UTC)

Can be done by adding the following to one of the banners with CAT_1 set to the category name. -- WOSlinker (talk) 22:21, 4 January 2011 (UTC)

{{WPBannerMeta/hooks/cats
 |category={{{category|¬}}}
 |BANNER_NAME = {{subst:FULLPAGENAME}}
 |cat 1={{#ifexist:{{#rel2abs:./to do}}|yes}}
  |CAT_1      = Project articles with todo lists
}}

Thanks a lot!! --Codrin.B (talk) 20:44, 11 January 2011 (UTC)

Well, I tried adding WPBannerMeta/hooks/cats as the last hook and then the WPBannerMeta/hooks/article todolist. The todo list disappears but articles appear in the Category:Dacia articles with todo lists. If I do the opposite, the todo list appears on the talk page, but the articles don't show up in the category anymore. I am missing anything? Here is the template {{WikiProject Dacia}}. Hope you can give me a hand. Thanks a lot!--Codrin.B (talk) 21:31, 11 January 2011 (UTC)

You can only have one HOOK_BOTTOM parameter. I've just merged the two into one param and it's working now. -- WOSlinker (talk) 21:43, 11 January 2011 (UTC)

Thanks so much!! --Codrin.B (talk) 23:15, 13 January 2011 (UTC)

Master todo list at project level

Having the ability to assemble all article todo lists in a master project todo list would be of tremendous use.--Codrin.B (talk) 21:02, 4 January 2011 (UTC)

Checklist tracking categories

Something to test in Template:WPBannerMeta/hooks/bchecklist/sandbox with params B1_CAT to B6_CAT. -- WOSlinker (talk) 20:27, 15 April 2011 (UTC)

Anyone wish to take a look and comment before I put it live? -- WOSlinker (talk) 20:29, 15 April 2011 (UTC)

Does this include a single category for any article that has an incomplete checklist? I'm not sure what the exact criteria are, but I know WPSHIPS and MILHIST have categories to track some sort of incomplete B-class assessment. — Carl (CBM · talk) 22:16, 15 April 2011 (UTC)

There would be individual categories for each of the checklist criteria. Would only include articles where the checklist is shown on the banner, so articles classed as stubs would not be included in the categories. Or are you after something slightly different? -- WOSlinker (talk) 22:35, 15 April 2011 (UTC)

I think (based on [2]) that the thing people are looking for is a category for articles that have any incomplete parameter in the checklist, so that the people can make a list of articles to edit. It would be more difficult for implementing that feature in the WP 1.0 bot if we have to do a union of several categories, and much easier if there was a single category for articles that have any missing part. But categories for each parameter would be OK as well, I don't think it has to be one or the other. Limiting it to articles where the checklist is shown seems right to me. — Carl (CBM · talk) 00:14, 16 April 2011 (UTC)

Wouldn't a single category be very similar to the C-Class category? Sort of depends if you are wanting to find those articles without a parameter filled in with anything or those articles without a yes in the parameter. Could have an option for either if the choice was needed. Could also include an option fo a single category as well. -- WOSlinker (talk) 07:33, 16 April 2011 (UTC)

Here's an example to try. I've added a MAIN_CAT param and also a CAT_TYPE param, which if set to "only_blank" then will not include those with params set to no. -- WOSlinker (talk) 07:49, 16 April 2011 (UTC)

{{WPBM
 |PROJECT=Sausages
 |BANNER_NAME=Template:Fictitious template
 |category=no
 |IMAGE_LEFT=Kielbasa7.jpg
 |HOOK_ASSESS={{WPBannerMeta/hooks/bchecklist/sandbox
  |BANNER_NAME=Template:Fictitious template
  |class=start
  |b1=yes
  |b2=no
  |b3=
  |b4=yes
  |b5=sausage
  |MAIN_CAT=Sausage articles with incomplete checklists
  |B1_CAT=Sausage articles needing attention to referencing and citation
  |B2_CAT=Sausage articles needing attention to coverage and accuracy
  |B3_CAT=Sausage articles needing attention to structure
  |B4_CAT=Sausage articles needing attention to grammar
  |B5_CAT=Sausage articles attention to supporting materials
  |CAT_TYPE=only_blank
 }}
}}

I've made the changes live & set it up on {{WikiProject Poland}} with this category. -- WOSlinker (talk) 09:00, 16 April 2011 (UTC)

Having thought about it a little more, there no need for a CAT_TYPE param. What now happens is that if MAIN_CAT is set, it is used when a param is blank or unrecognised and the if individual cats are set, it is used when a param is blank, unrecognised or no. -- WOSlinker (talk) 09:42, 16 April 2011 (UTC)

Let me go ask the person who made the original request what they want, exactly. They're the ones who will be using this in the end. — Carl (CBM · talk) 12:06, 16 April 2011 (UTC)

I very much appreciate your efforts. To answer your question, WOSlinker, yes, it would be similar to the C-class now, but only to a smaller degree, as we have started adding B-class reviews (and adding/completing the checklists) now. Thus the problem is that we are losing (lost...) track of which C-class articles where simply failed and which haven't been reviwed yet. The goal of incomplete/missing B-class checklist category would be to give us a list of the articles we need to review (and add/complete the checklist), so that in the end, that category would be empty and all C-class articles would have a (Failed) B-class review. Could you point me to the new categories? Or you are welcome to annouce them at WT:POLAND. Thank you all for this effort, I think all B-class reviewing WikiProjects will benefit from this. Now, how do we notify them...? If there would be a way to easily see which projects have implemented a checklist, we could have a bot announce your new tool to them... --_{Piotr Konieczny aka Prokonsul Piotrus| talk} 16:26, 16 April 2011 (UTC)

The category is at Category:Poland articles with an incomplete B-Class checklist. -- WOSlinker (talk) 17:48, 16 April 2011 (UTC)

Thanks, this indeed is what we wanted, this is very helpful! --_{Piotr Konieczny aka Prokonsul Piotrus| talk} 15:49, 17 April 2011 (UTC)

B-class checklist example icons confusing?

Is there any reason why the red parts below:

  |b1={{#ifeq:{{{b1|<includeonly>¬</includeonly>}}}|¬|¬|y}}
  |b2={{#ifeq:{{{b2|<includeonly>¬</includeonly>}}}|¬|¬|n}}
  |b3={{#ifeq:{{{b3|<includeonly>¬</includeonly>}}}|¬|¬|!}}
  |b4={{#ifeq:{{{b4|<includeonly>¬</includeonly>}}}|¬|¬|y}}
  |b5={{#ifeq:{{{b5|<includeonly>¬</includeonly>}}}|¬|¬|x}}
  |b6={{#ifeq:{{{b6|<includeonly>¬</includeonly>}}}|¬|¬| }}

can't all just read "n"? It's nice to know that there are icons for every contingency, but I think the default can be pretty confusing for anyone not familiar with the B-class checklist, especially if B1 and B4 appear to have "criterion met". Yes, it becomes apparent once you add the checklist code to the template on the talk page of any album, but right off the bat, it may be a little misleading. Especially now that the class check has been moved elsewhere. Just a thought. – – Kerαunoςcopia^◁_galaxies 16:19, 22 May 2011 (UTC)

bchecklist graphics

Disregard

 – Apparently this isn't an issue from what I'm just seeing at another wikiproject template. – Kerαunoςcopia^◁_galaxies 04:39, 31 May 2011 (UTC)

There hasn't been any dissension to my discussion above. There is no reason for anything other than "y/yes" or "n/no" to be written in these parameters. Therefore, please make the following changes to Template:WPBannerMeta/hooks/bchecklist. Replace:

  |b1={{#ifeq:{{{b1|<includeonly>¬</includeonly>}}}|¬|¬|y}}
  |b2={{#ifeq:{{{b2|<includeonly>¬</includeonly>}}}|¬|¬|n}}
  |b3={{#ifeq:{{{b3|<includeonly>¬</includeonly>}}}|¬|¬|!}}
  |b4={{#ifeq:{{{b4|<includeonly>¬</includeonly>}}}|¬|¬|y}}
  |b5={{#ifeq:{{{b5|<includeonly>¬</includeonly>}}}|¬|¬|x}}
  |b6={{#ifeq:{{{b6|<includeonly>¬</includeonly>}}}|¬|¬}}

with

  |b1={{#ifeq:{{{b1|<includeonly>¬</includeonly>}}}|¬|¬|n}}
  |b2={{#ifeq:{{{b2|<includeonly>¬</includeonly>}}}|¬|¬|n}}
  |b3={{#ifeq:{{{b3|<includeonly>¬</includeonly>}}}|¬|¬|n}}
  |b4={{#ifeq:{{{b4|<includeonly>¬</includeonly>}}}|¬|¬|n}}
  |b5={{#ifeq:{{{b5|<includeonly>¬</includeonly>}}}|¬|¬|n}}
  |b6={{#ifeq:{{{b6|<includeonly>¬</includeonly>}}}|¬|¬|n}}

The result can be seen at my sandbox. Thanks! – Kerαunoςcopia^◁_galaxies 00:02, 31 May 2011 (UTC)

Todo list

In Template:WPBannerMeta/hooks/todolist, should the default title be (i) Todo list as at present; (ii) To do list as suggested at Template talk:WikiProject Olympics#Edit request on 3 July 2012 or (iii) To-do list? --Redrose64 (talk) 17:59, 3 July 2012 (UTC)

• To-do list --Redrose64 (talk) 17:59, 3 July 2012 (UTC)
• Should probably match {{To do}} -- WOSlinker (talk) 19:26, 3 July 2012 (UTC)
• Made the change — Martin (MSGJ · talk) 15:37, 5 July 2012 (UTC)

Table of Contents inside To-do list

I recently added a to-do list to WP:INDU's project banner, and somehow, it's hiding the table of contents for every talk page on which it is included inside the collapsed to-do list area now, e.g. on the project's main talk page. I've looked over the documentation, and I can't see anything wrong with the way I set it up. Any ideas? Thanks. —Torchiest ^talk_edits 21:41, 7 July 2012 (UTC)

I've removed the headings from your to-do list, which seems to have resolved the problem — Martin (MSGJ · talk) 22:00, 7 July 2012 (UTC)

Ah, thanks so much for that. —Torchiest ^talk_edits 00:05, 8 July 2012 (UTC)

Project task force to do lists

Hi. If anyone here's able to please comment at Wikipedia talk:WikiProject Computing#Wikipedia:WikiProject Computing/to do, it'd be most appreciated. Thanks. -- Trevj (talk) 11:13, 25 January 2013 (UTC)

Bump -- Trevj (talk) 13:30, 28 February 2013 (UTC)

Proposal: Disallow transcluded to-do lists

There is a proposal at Wikipedia talk:WikiProject Council#Proposal: Disallow transcluded to-do lists. Please comment there. PrimeHunter (talk) 23:55, 18 February 2015 (UTC)

Protected edit request on 1 July 2015

Hello! In the following line, formatting with ''' is redundant, as the bold attribute is (somehow) already inherited from the table heading:

<tr><th style="text-align:left; padding:0.2em 2px 0.2em 0;">'''{{{TODO_TITLE|To-do list}}}:'''</th></tr>

Removing that formatting would also resolve the visual issue resulting from this "double bolding". — Dsimic (talk | contribs) 14:12, 1 July 2015 (UTC)

Yes, I agree, Done --Redrose64 (talk) 16:23, 1 July 2015 (UTC)

Great, thank you! — Dsimic (talk | contribs) 16:27, 1 July 2015 (UTC)

Idea: Increase integers from 10 to 15

For Template:WPBannerMeta/hooks/taskforces I think the number of integers should be increased to 15. Wikipedia:WikiProject China is getting more and more task forces. WhisperToMe (talk) 18:45, 26 March 2016 (UTC)

@WhisperToMe: You don't need to. Just add another {{WPBannerMeta/hooks/taskforces}} to gain another set of ten - see e.g. {{WikiProject United States}} which has eleven, for a potential 110 taskforces. --Redrose64 (talk) 21:37, 26 March 2016 (UTC)

Protected edit request on 22 March 2019

Please remove the line {{pp-template}} - protection templates are automatically handled by the documentation page. Thanks, --DannyS712 (talk) 06:53, 22 March 2019 (UTC)

 Done — JJMC89 (T·C) 07:07, 22 March 2019 (UTC)