Wikipedia:Page Curation/Suggested improvements/Archive 2
![]() | This is an archive of past discussions on Wikipedia:Page Curation/Suggested improvements. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current main page. |
Archive 1 | Archive 2 |
51. Allow users to override infinite scrolling of the feed
The infinite scrolling interface is annoying and unproductive. Even to go back a few days in the queue requires way too much user input. To get to the vast middle of the queue is onerous. There should be an option to load everything in the queue (at least for pages created by new users), or to load pages similar to how it is done in Special:RecentChanges.- MrX 15:39, 15 June 2017 (UTC)
- See Wikipedia:Page_Curation/Suggested_improvements#15._Jumpback above. Tracked at the right Phab Task. — Insertcleverphrasehere (or here) 08:13, 19 October 2018 (UTC)
52. Allow patroller to send message to editor without tagging or un-reviewing/re-reviewing
![]() |
---|
I often add tags to an article I've come across, perhaps while stub-sorting, using Twinkle as usual, and then realise that it's awaiting NPP. I might want to send a message to the creator ... but I can't do so without adding another tag. I've been known to add a duplicate tag, send the message using the Curation toolbar, then edit again to remove duplicate. PamD 17:45, 15 June 2017 (UTC)
|
53. Allow filtering by no citations
done
|
---|
Adding a filter to the new pages feed to allow patrollers to see which pages are marked by the software as having no citations would be helpful. I have created this task in phab. TonyBallioni (talk) 17:27, 28 June 2017 (UTC) Support This would be a useful way to prioritise our patrolling. Boleyn (talk) 05:36, 14 July 2017 (UTC)
|
54. Send feedback to talk page
While working on reviewing "older" new pages, I sometimes notice that I'm sending feedback to someone who created a redirect that has been turned into an article by someone else. I think I've asked for a feature to select the recipient, but I now think that such a feature clutters the UI and makes things more complicated. It occurred to me that it would be better to post the feedback to the talk page and leave a notification for the creator/main contributor instead. That way, the tags have a context that is more easily accessible to other contributors. Is there support for such a change? Mduvekot (talk) 12:04, 1 July 2017 (UTC)
- Definitely would like to be able to automatically record comments (eg: Noting that a page appears to pass an SNG), without necessarily needing for it to notify the page creator. The way to do it might be to have a field for user to notify, and automatically populate it with page creator. That could be replaced with one or more users (separated by commas?), or left blank for article talkpage comment but no notification. ~Hydronium~Hydroxide~(Talk)~ 08:12, 2 July 2017 (UTC)
- I completely support the idea of leaving feedback on an article's talk page. But obviously only when it's useful to other editors to improve that article. Unaware of this thread, I today suggested a similar idea on this page. In essence, I propose an option to "Add copy of comments to article's talk page". It would probably need some covering text, such as:
- A New Page Reviewer has left feedback for the creator of this article. The following extract may also be of relevance to other editors in improving this page: (insert text and autosignature).
- It would be good to hear what support other reviewers would give for such a function. Nick Moyes (talk) 16:56, 14 July 2017 (UTC)
- I completely support the idea of leaving feedback on an article's talk page. But obviously only when it's useful to other editors to improve that article. Unaware of this thread, I today suggested a similar idea on this page. In essence, I propose an option to "Add copy of comments to article's talk page". It would probably need some covering text, such as:
- Support This would allow others who come to the article to see the reviewer's comments, this can only be an improvement. — Insertcleverphrasehere (or here) 04:12, 4 September 2018 (UTC)
- One of the flaws of the curation tool is that is sends the notes from the reviewer to the creator of the article. It should go to the talk page of the article instead. I've gotten my share of "what were you thinking?" responses from experienced editors who created a redirect that was overwitten by a new editor. I learned to always check the history of a page I'm reviewing. Vexations (talk) 01:47, 17 September 2018 (UTC) (comment copied from the discussion board by — Insertcleverphrasehere (or here))
- Vexations, I totally agree about the notifications to the article creator when it should go to the article TP. It even notifies banned/blocked users. I'm pinging MMiller (WMF) hoping maybe he can either fix it or make a suggestion so we can. Atsme✍🏻📧 02:11, 17 September 2018 (UTC) (comment copied from the discussion board by — Insertcleverphrasehere (or here))
- Requested on Phab. — Insertcleverphrasehere (or here) 08:31, 19 October 2018 (UTC)
57. List of previous creators of an article
Page creation log is now live at: special:log/create. — usernamekiran(talk) 19:38, 30 June 2018 (UTC)
|
---|
Adding such a feature to new pages feed would be complicated. But if only new page reviewers (and nobody else except sysops) could see it in page history, the proposed feature may become reality. —usernamekiran(talk) 00:15, 9 September 2017 (UTC)
|
58. Add the Sources exist Tag
![]() |
---|
Can we please add the {{sources exist}} tag to the page curation toolbar? This tag would be immensely useful in reducing duplicate work required and would be an easy way of notifying other editors "yes I did a search and I found a bunch of stuff". It would also make it so that NPP reviewers could mark articles as reviewed and AfC reviewers could 'accept' drafts that might not "demonstrate" notability, but were clearly notable when the reviewer did a search (i.e. they could add the tag indicating why they accepted it). All in all just a useful variant of the {{more references}} tag. — Insertcleverphrasehere (or here) 06:31, 22 December 2017 (UTC)
|
59. Wikidata
Not a priority - out of scope for NPR
|
---|
It'd be useful for Special:NewPagesFeed to indicate whether an article is linked to a wikidata item, and where so, to provide the Qid as a link. The indication / link would enable action to be taken to create a link or a wikidata item, and facilitate an inspection of a linked item, from the feed page. Not least, a number of en.wikipedia project have a dependency on good linkage to wikidata - e.g. Women in Red. --Tagishsimon (talk) 22:43, 11 January 2018 (UTC)
[[:d:{{BASEPAGENAMEE}}]]
...Or there's Yair rand's tool (available as a gadget on meta) which may satisfy your needs. Cabayi (talk) 10:44, 30 October 2018 (UTC) |
60. Add information link to 'Notices' message sent to article creator
Closed at Phab. Templates are locally configurable
|
---|
Hi, I received a message on my 'Notices' icon containing 'The page <article name> has been reviewed', a link to the article I had created (which appeared unchanged), a link to the user that performed the review, but nothing to explain the review's outcome or what a review entails. I believe adding the same Learn more link that exists on the New pages feed to the notification text would be beneficial, especially as a new editor such as myself, or if possible a direct link to the details/outcome of the review? – Paul · ✉ 13:12, 12 January 2018 (UTC)
|
61. Articles to go back into NPR queue when overwritten
Proposed here. When all or a very large proportion of an article's content is overwritten with new material, the article should be marked as unpatrolled and added to the NPR queue. This is virtually creation of a new article, but can be done by IPs and new accounts, and is often a sign of conflict-of-interest editing: Noyster (talk), 11:03, 16 January 2018 (UTC)
- That is a very good idea, Noyster. What number of bytes do you think should trigger the alarm? Join the development discussion n the talk page of Wikipedia:WikiProject Articles for creation/AfC Process Improvement May 2018 before it's too late. Kudpung กุดผึ้ง (talk) 11:03, 18 May 2018 (UTC)
- See Wikipedia:Village_pump_(technical)/Archive_162#Flagging_overwriting_of_articles for more technical details. — Insertcleverphrasehere (or here) 08:41, 19 October 2018 (UTC)
62. "on behalf of"
Done
|
---|
I recently unreviewed a page (unintentionally), which triggered this note to be posted to Jbhunley's talk page. The note itself is no problem and seems like a good idea, however, it is signed by me as though I personally wrote it and the edit history shows the same, in contrast - for instance - to other auto-generated notices which will often carry the disclaimer, for instance, "Message delivered by Legobot, on behalf of Chetsford" (e.g. [2]). Is there a way to amend the script so it clarifies, when posting messages on behalf of editors, that the tool is posting the message "on behalf of" and that the editor did not personally compose the message him/herself? Chetsford (talk) 18:35, 3 March 2018 (UTC)
@Insertcleverphrasehere, Barkeep49, and Chetsford:-- |
63. Capacity to handle 2nd+ AfD nominations
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Currently, when a page is nominated for AfD using the curation toolbar and there exists a previous nomination, the result is a minor trainwreck - see e.g. my last instance. Such nominations have to carried out manually. Some functionality to detect previous nominations, increment the count, and handle the paperwork would be very welcome. (I'm getting the impression that some articles remain un-nominated because people don't want to tangle with the manual process, which seems counterproductive). --Elmidae (talk · contribs) 13:48, 8 March 2018 (UTC)
- Support This is a pretty major failing of the PC tools, a deficiency that I have not noticed occurring with twinkle (just another reason to use twinkle for all deletions, (in addition to the lack of ability to have a userspace CSD log. — Insertcleverphrasehere (or here) 10:04, 17 March 2018 (UTC)
- It's not a 'major' problem, and in any case,only admins can do deletions. BTW, this is not a RfC. Kudpung กุดผึ้ง (talk) 14:16, 17 March 2018 (UTC)
- Support Among the reasons I still use twinkle. DGG ( talk ) 19:35, 17 March 2018 (UTC)
- Support--Crazy bug! One of the reasons behind Twinkle's constant popularity:)~ Winged BladesGodric 13:24, 22 March 2018 (UTC)
- Support as useful. Object to the notion that AfD it does'n work in Curation. It works oerfectly and it's even easier than Twinkle. Kudpung กุดผึ้ง (talk) 11:06, 18 May 2018 (UTC)
- Strong support - definitely. I do hope this bug will get fixed at some point; it appears to still be occurring.--SkyGazer 512 Oh no, what did I do this time? 23:21, 21 September 2018 (UTC)
- Use Twinkle! There is nothing in the PC's deletion module that can't be done using Twinkle. (This isn't so for the tagging module - TW doesn't allow sending a message to the creator, and the UI/UX is poorer.) But Twinkle's CSD, PROD, XFD modules are simply perfect and have stood the test of time. Any bugs found in them are usually fixed quickly. WMF devs have just wasted their time building something that's totally redundant to, as well as inferior to the already existing functionality in Twinkle. SD0001 (talk) 19:04, 1 January 2019 (UTC)
- According to Phab, this is now done. Someone please check. Barkeep49?. Kudpung กุดผึ้ง (talk) 07:18, 13 September 2019 (UTC)
- @Kudpung: unfortunately, that isn't the case; according the phab, the investigation into feasibility is done, the actual work is at phab:T231357 DannyS712 (talk) 07:57, 13 September 2019 (UTC)
- DannyS712 is correct. The original ticket was an investigation into how feasible this change would be. We might have to put it back on a future wishlist to actually get done. Best, Barkeep49 (talk) 13:13, 13 September 2019 (UTC)
- Barkeep49, I don't think that we need to put it into a future wishlist. MaxSem has already submitted a patch and someone is going to review them, soon enough pending which this ought to go into production .... ∯WBGconverse 13:25, 13 September 2019 (UTC)
- DannyS712 is correct. The original ticket was an investigation into how feasible this change would be. We might have to put it back on a future wishlist to actually get done. Best, Barkeep49 (talk) 13:13, 13 September 2019 (UTC)
- @Kudpung: unfortunately, that isn't the case; according the phab, the investigation into feasibility is done, the actual work is at phab:T231357 DannyS712 (talk) 07:57, 13 September 2019 (UTC)
64. CSD/PRODs: update userspace logs
Continue discussion at #55 above
|
---|
While Twinkle keeps a userspace log of these forms of deletion nomination, the page curation toolbar does not. To maintain interoperability with twinkle, it probably should read the relevant section of twinkleoptions.js, if it exists. ∰Bellezzasolo✡ Discuss 11:24, 30 March 2018 (UTC)
|
65. Reviewer No Decision
Done
|
---|
As someone who tends to hang-out more in the oldest view of NPP, it would be helpful if reviewers had a way, like on the Article Talk page, to indicate that they had undertaken a review of a page but did not reach a decision with the option to include a message about why. If several reviewers all start looking at an article and move on that says something (what it says would depend on circumstances) vs if a reviewer happens to be the first person to actually examine an article. Best, Barkeep49 (talk) 06:07, 18 May 2018 (UTC)
|
66. N articles deleted (of which Z via SD) out of M created
Generating a SD% is too troublesome.Not worth it.
|
---|
As a reviewer I think adding this query would be welcomed by many reviewers: a way to show the number of deleted articles right in the Page Curation tool (e.g. Created by Username (talk | contribs) · XXX edits since dd Month year) - N articles deleted (of which Z via SD) out of M created. This would be useful in cases (and there are many) when a user keeps creating pages without reading the basic policies and on his talk page we see that most of the newly created articles were sd. We'd have a percentage of the editor's sd page percentage. And, seeing a notice in this regard would be some sort of heads up for the reviewer, although sometimes other editors may of been improved the article and obviously we need to take a closer look. Robertgombos (talk) 19:23, 1 June 2018 (UTC)
|
67. [Bug] Cleanup tag preventing marking incorrectly
I cannot replicate either.Was a local bug or was fixed at some point.
|
---|
Not sure if this is the correct spot, let me know if I need to post it somewhere else If you tick the box to tag a page with the Cleanup tag, then uncheck the box and attempt to submit the other tags, the curation tool will inform you that you must add a description to the cleanup tag before submitting it. You can work around this by ticking and unticking the cleanup tag again, but it would still be nice to get this bug fixed. Xevus11 (talk) 05:10, 29 June 2018 (UTC)
|
68. Requesting revision deletion
Adding functionality to the Page Curation tools to allow a reviewer to easily request Revision Deletion is essential. Currently the only options that it gives is to drop a generic {{non-free}} template, or else CSD nomination. There aren't any good tools for requesting Revdel either. I would envision something along the lines of pulling up a scroll-able list of revisions, and the user simply selection ranges to be tagged for Revdel. — Insertcleverphrasehere (or here) 04:02, 4 September 2018 (UTC)
- Support Best, Barkeep49 (talk) 05:35, 4 September 2018 (UTC)
- Support — Yep, this would make a lot easier to request cv-revdel. Regards, SshibumXZ (talk · contribs). 07:41, 19 October 2018 (UTC)
- Best tool for this currently is User:Enterprisey/cv-revdel. This tool is great but it would be really good to have this added as an option in the Page Curation tools as a popup. — Insertcleverphrasehere (or here) 08:56, 19 October 2018 (UTC)
- ICPH,I believe the pop-up addition can be locally implemented.Will take a look:-) ∯WBGconverse 16:21, 21 October 2018 (UTC)
- Insertcleverphrasehere, the copyvio-revision-deletion template (wherein either the set of diff(s) have to be manually inputted or (that I had integrated the copy-patrol functionality into the template), the Copypatrol URL of the violation can be directly inputted) can be easily implemented into the Curation toolbar.
- Would that be any helpful? ∯WBGconverse 20:13, 21 October 2018 (UTC)
- @Winged Blades of Godric: At the very least it would be helpful to simply dump the empty template on the page via a tag. I've noticed that even if you don't fill in the Diffs, if it is simple most admins can figure out which revisions need to go relatively quickly. Thanks for helping out with these tasks. Cheers, — Insertcleverphrasehere (or here) 20:17, 21 October 2018 (UTC)
- Thanks:-) This can be sought as an edit-request but to avoid any messes, I have asked for permission to try the integration at Beta-cluster. ∯WBGconverse 05:53, 22 October 2018 (UTC)
- @Winged Blades of Godric: At the very least it would be helpful to simply dump the empty template on the page via a tag. I've noticed that even if you don't fill in the Diffs, if it is simple most admins can figure out which revisions need to go relatively quickly. Thanks for helping out with these tasks. Cheers, — Insertcleverphrasehere (or here) 20:17, 21 October 2018 (UTC)
- @Galobtter:--Does this look any good? A few system-messages need to be locally created though!∯WBGconverse 09:37, 22 October 2018 (UTC)
- Winged Blades of Godric, looks reasonable, but I'm no js expert or know too much about the configuration of the page triage extension - so testing on testwiki:MediaWiki:PageTriageExternalTagsOptions.js by asking one of the intadmins at Special:ListUsers/interface-admin would be good. Galobtter (pingó mió) 09:50, 22 October 2018 (UTC)
- Thanks:-) Asked Oshwah! ∯WBGconverse 10:29, 22 October 2018 (UTC)
- Tweaked a bit and this is the new diff:-)∯WBGconverse 17:24, 22 October 2018 (UTC)
69. Passive aggressive messaging system
On-wiki templates amended
|
---|
Remove the "Thanks for creating XXXXXX, Author!" from the message template, or at least get rid of the exclamation point. If I want to send negative feedback, especially to say that the page is inappropriate and unsuited for Wikipedia, it comes off as extremely passive-aggressive. — Insertcleverphrasehere (or here) 04:17, 4 September 2018 (UTC)
|
70. Curation toolbar opt-out or opt-in in preferences
Worked upon by Miller.Xao has already provided a nice solution.
|
---|
The page curation toolbar has now been enabled by default for every page you open from the special:newpagesfeed. Not all of us want this though (at least I don't): I do new page patrolling, but don't need or want the curation toolbar, and it is rather intrusive. Having to minimize and remove it on every page is tiresome. Can we please have an option in preferences to opt-in or opt-out of this toolbar? Fram (talk) 14:34, 19 October 2018 (UTC)
|
84. 'Potential Issues' flagged in Page Curation Toolbar Page Info flyout
Fixed
|
---|
As far as I can see, the page curation tool is supposed to flag 'potential issues' in the 'Page info' section of the toolbar (or at least this is what was intended when it was being made [3]). This info is currently visible from the NewPagesFeed, but not from the toolbar. This functionality seems to be nonexistent and was either never implemented properly, or has become bugged and broken. It should contain things like 'Blocked user', 'Orphaned', 'No categories', as well as the ORES stuff that has been added recently: 'Possible Vandalism', 'Possible Spam', 'Possible attack page', and 'Possible Copyvio' which is currently being added to New Pages Feed (this last one should also have a link to the Copyvios report). When a page has issues it should be flagged with a red number on the Page Info Icon as shown in the mockups at the link above. — Insertcleverphrasehere (or here) 13:45, 24 October 2018 (UTC)
|
86. Page Curation toolbar: do not mark pages as 'reviewed' when adding CSD and PROD tags
Done
|
---|
Per this discussion, we have decided that it is best to not mark pages as 'reviewed' when adding CSD and PROD tags to articles (due to the ease at which articles can fall through the cracks if these tags are removed and the reviewer doesn't notice). The Page Curation toolbar currently automatically marks pages as 'reviewed' when adding CSD tags and PROD tags, this should change and simply leave the page unreviewed after the page is tagged for deletion (that way it will fall back into 'unreviewed' pages if the CSD tag is removed inappropriately or if the PROD is removed). |
88. Add Tags and hatnotes
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Doesn't the Add Tags feature recognise hatnotes and place the tags below them, per WP:MOSLAYOUT? I noticed this from this edit. --Paul_012 (talk) 16:14, 12 May 2019 (UTC)
- Currently, tagging is done via a wrapper api that only accepts as parameters what tags to prepend and what to append (and others not relevant here) - this would require reworking the api to parse the current text and place them accordingly DannyS712 (talk) 04:55, 18 September 2019 (UTC)
89. A Curation tool message that's using a non-existant template
Resolved
|
---|
This is maybe already fixed, but it appears CurationTool is trying to subst Template:Sentnote-NPF instead of Template:Reviewednote-NPF, see this example or this which shows a handful of instances. Can this sentnote template redirect to reviewednote or are they supposed to include different text? --148.63.157.82 (talk) 22:59, 23 July 2019 (UTC)
|
93. Have page curation be less hard coded and more controllable by Wikipedia
Right now a lot of things are hard coded into page curation. Given that the WMF has said that they will not devote regular resources to page curation and that instead we need to go through the wishlist, it seems to me that moving as much control as possible to the encyclopedia through templates, would be desirable. IN this way even if the WMF cannot devote resources those volunteers who wish to do so could continue to adapt and change the page curation tool. For instance, the length of time that it takes for a redirect or article to be indexed could be controlled via template rather than be hard coded into the curation tool. There are probably other such things. If/when the WMF extends the curation tool to other wikipedias this sort of local control would only become more important - for instance they might not have the same content tag concerns as us and so there wouldn't be a desire for every tag we have, but on the other hand they might have other warnings that we don't have which they would like to be able to tag on articles. Best, Barkeep49 (talk) 23:15, 11 August 2019 (UTC)
- The way PageTriage code-base is written, it's sheer impossible to incorporate a wiki-agnostic mode. Same for most other stuff. Sans a complete overhaul, not possible, I dare say. ∯WBGconverse 09:19, 13 September 2019 (UTC)
Article patrol status after refund/undelete
Per the discussion, when an article is undeleted per WP:REFUND, it should always be back in the queue. MB 18:51, 25 June 2022 (UTC)
- I'll support that. I'm surprised it's not a;ready done. I guess I kinda took it for granted. Kudpung กุดผึ้ง (talk) 06:34, 26 June 2022 (UTC)
80. Page Curation tools optionally available on any page, not just those in NewPagesFeed
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
It should be possible to make ?showcurationtoolbar=1 and the 'curate this article' link work on any article, not just those in the feed (but currently can only be used on articles that have not expired out of the NewPagesFeed).
It is quite annoying that the Page Curation tools are only available for new pages that haven't expired, it means that I have to use Twinkle whenever a page has been reviewed and expires out of the feed.
It silly that the Page Curation tools are only available on new pages and not, for example, on Broadwater Green. IMO the 'curate this article' link in the toolbar should always be available to New Page Reviewers regardless of the page they are reviewing (It would even be useful for drafts).
Note that the page curation tools should ONLY show up on 'other pages' (pages that aren't in the NewPagesFeed) if that string is added to the URL or if you click the 'curate this article' link. Otherwise I think people would get quite annoyed with it showing up on all sorts of other pages constantly. — Insertcleverphrasehere (or here) 16:07, 19 October 2018 (UTC)
- This can be likely implemented easily, via a patch.Let's see. ∯WBGconverse 20:09, 27 October 2018 (UTC)
Vandalism by Category and Importance?
Is Vandalism on stubs or low rank articles common? And do unwatched articles get more vandalism? I know there can be multiple projects, but the project importance quality table might be good to have in long run, https://en.wikipedia.org/wiki/Wikipedia:Version_1.0_Editorial_Team/Star_Wars_articles_by_quality_statistics Wakelamp d[@-@]b (talk) 08:52, 24 November 2021 (UTC)
- @Wakelamp: There are hundreds of projects on Wikipedia (if not thousands). No priorities are set, or can be set for them. School artcles receive a high dose of vandaliasm, for example, because they attract children, but there are possibly others. As this is not a tool request or a bug report, please consider reposting your question at WT:NPR where it will get more exposure and a faster response. Kudpung กุดผึ้ง (talk) 04:04, 11 April 2022 (UTC)
Mark unpatrolled
This feature, if it doesn't already exist, was suggested by this unanswered question I found while looking at the Help Desk archives.— Vchimpanzee • talk • contributions • 18:00, 23 November 2021 (UTC)
- A patroller can add any page back to the NPP queue by clicking "Add to the New Pages Feed" in the "Tools" left hand menu Polyamorph (talk) 19:58, 23 November 2021 (UTC)
- I'll let the person know. Thanks.— Vchimpanzee • talk • contributions • 20:25, 23 November 2021 (UTC)
Please move the “mark as reviewed” checkbox

I do all my reviewing on iPad and the checkbox for “mark as reviewed” is about one fifteenth of a fingertip away from the green bar for “add selected tags”. This means I frequently make fat finger errors and have to go back and unreview an article. Instead of appearing just above the green bar could the checkbox move over to the right to allow clear space between them? Thanks Mccapra (talk) 11:48, 14 November 2021 (UTC)
- Hey @Mccapra. Thanks for your suggestion. You're talking about the check mark in the vertical toolbar right? The vertical toolbar is already all the way to the right of the screen, leaving no space to move it further right, so I think I am missing something. Feel free to clarify. –Novem Linguae (talk) 06:36, 23 July 2022 (UTC)
- Thanks for following up. I’ve added a screenshot above. What I’m asking is for the “Mark this page as reviewed” checkbox to be moved away to the right so it takes two distinct finger movements to add tags and to mark as reviewed. At the moment it’s too easy to accidentally mark as reviewed when I only mean to add tags, since the two are so close together. Thanks Mccapra (talk) 07:28, 23 July 2022 (UTC)
- Got it. That's an easy one. I'll prioritize it. Thanks for suggesting. –Novem Linguae (talk) 07:53, 23 July 2022 (UTC)
- Woo hoo! Tick box has moved! Thank you! Mccapra (talk) 08:00, 29 July 2022 (UTC)
- Got it. That's an easy one. I'll prioritize it. Thanks for suggesting. –Novem Linguae (talk) 07:53, 23 July 2022 (UTC)
- Thanks for following up. I’ve added a screenshot above. What I’m asking is for the “Mark this page as reviewed” checkbox to be moved away to the right so it takes two distinct finger movements to add tags and to mark as reviewed. At the moment it’s too easy to accidentally mark as reviewed when I only mean to add tags, since the two are so close together. Thanks Mccapra (talk) 07:28, 23 July 2022 (UTC)
Page feed introduction
At the top of the Page feed, there is the intro text beginning with "Rather than speed..." I would like a way to remove that to maximize the number of articles shown on the screen. I know you can scroll it off, but it comes back if you are scrolling within the article list. Can this be collapsed to hide it (with the collapse button being in the unused space in the header bar). MB 15:13, 19 August 2022 (UTC)
- @MB. The code for that is located at MediaWiki:Pagetriage-welcome. Maybe sandbox something then propose it at MediaWiki talk:Pagetriage-welcome. I've watchlisted the page and will be sure to weigh in. –Novem Linguae (talk) 20:06, 19 August 2022 (UTC)
- I tried to create a sandbox over there, but unlike a protected template, I couldn't edit the sandbox. I made this with a simple hide button. It's not exactly what I wanted, but now knowing how that is done, it's close enough. What do you think? MB 06:39, 20 August 2022 (UTC)
- Thanks for sandboxing it. Looks great. Let's move forward by doing an {{Edit fully-protected}} on the talk page. –Novem Linguae (talk) 08:43, 20 August 2022 (UTC)
- Before I do that, do you know if there is a way to hide it instead of just collapse it, so there isn't even a line with "show" visible. The notifications on the top of the watchlist are dismissible. I know they use cookies to keep messages dismissed, and I don't mean that. Just a way hide the message knowing it would come back every time the page is reloaded. I couldn't figure out how the watchlist dismiss feature works to even be able to make a non-persistent version. MB 20:24, 21 August 2022 (UTC)
- Looks like MediaWiki:Gadget-watchlist-notice-core.js is what makes the dismiss button work. This is a gadget that is enabled by default for everyone, although it is possible to turn it off. A dismiss button could probably be hacked to work outside the watchlist, but could be a bit fragile. Might be better to just move forward with the collapse box. Or you can make a request over at WP:Requested templates to create a new Template:Dismissable or similar. –Novem Linguae (talk) 02:03, 22 August 2022 (UTC)
- Before I do that, do you know if there is a way to hide it instead of just collapse it, so there isn't even a line with "show" visible. The notifications on the top of the watchlist are dismissible. I know they use cookies to keep messages dismissed, and I don't mean that. Just a way hide the message knowing it would come back every time the page is reloaded. I couldn't figure out how the watchlist dismiss feature works to even be able to make a non-persistent version. MB 20:24, 21 August 2022 (UTC)
- Thanks for sandboxing it. Looks great. Let's move forward by doing an {{Edit fully-protected}} on the talk page. –Novem Linguae (talk) 08:43, 20 August 2022 (UTC)
- I tried to create a sandbox over there, but unlike a protected template, I couldn't edit the sandbox. I made this with a simple hide button. It's not exactly what I wanted, but now knowing how that is done, it's close enough. What do you think? MB 06:39, 20 August 2022 (UTC)
Page Curation toolbar not displaying

The page curation tool hasn’t been showing up for a while now. I thought it would with time, but it hasn’t. It stopped working after it glitched when I used it to nominate an article for deletion (which didn't work right, btw). Any help? Any suggestions? R E A D I N G Talk to the Beans? 04:33, 7 August 2022 (UTC)
- Hey @Reading Beans. Thanks for the question. AFD is super buggy, I've been working on fixing that one for a couple weeks. It's been a tricky set of bugs to crush, hopefully my patch coming out this Thursday finishes fixing it.
- As for your toolbar not showing up, can you click on Kuala Pembuang and see if this page displays the toolbar after a few seconds? If not, can you take a screenshot and post it here? Can you also follow the directions at WP:CONSOLEERROR and see if there's any relevant errors? –Novem Linguae (talk) 04:41, 7 August 2022 (UTC)
- I had to remove every other script present in my common.js page. It’s working now, thank you. Reading Beans (talk) 05:24, 7 August 2022 (UTC)
- @Reading Beans. If you can figure out exactly what other script is interfering with PageTriage, I'd be happy to take a look. Otherwise I'll probably archive this soon. I'm glad you got it working :) –Novem Linguae (talk) 03:42, 24 August 2022 (UTC)
- @Novem Linguae, I cannot really tell. Archiving it 100% fine. Reading Beans (talk) 22:48, 24 August 2022 (UTC)
- @Reading Beans. If you can figure out exactly what other script is interfering with PageTriage, I'd be happy to take a look. Otherwise I'll probably archive this soon. I'm glad you got it working :) –Novem Linguae (talk) 03:42, 24 August 2022 (UTC)
- I had to remove every other script present in my common.js page. It’s working now, thank you. Reading Beans (talk) 05:24, 7 August 2022 (UTC)
Add "were created by autopatrolled users" to filter list

Abuse by UPE, spammers, and simply editors who totally fail to create their new pages in the spirit of the user right. These problems are being increasingly discovered through better due diligence and patroller intuition and the rate is alarming. These new pages are still listed on new page lists and feeds, but are listed with the green check mark as if they have been reviewed by a patroller. I'm therefore requesting the addition of 'were created by autopatrolled users' as an option in the prefs panel. I'm sure this was asked for during the development of the panel, but it was overlooked at the time. See themw:Page_Curation development page. Kudpung กุดผึ้ง (talk) 21:41, 7 July 2022 (UTC)
- This patch got approved today. It will deploy next Thursday 8/11. –Novem Linguae (talk) 11:36, 3 August 2022 (UTC)