This page has archives. Sections older than 3000 days may be automatically archived by Lowercase sigmabot III when more than 400 sections are present.
Title of subpage
How can I change the title of the "Draftify log" subpage which logs the actions performed by this script? Would it be okay if I copy the entire source to my subpage then customize the subpage location? KingAndGod13:46, 22 April 2018 (UTC)[reply]
@KingAndGod: At the moment the subpage name is hard-coded in the source. Is there actually a need to have it at a different page title? You could always transclude it to another page using ((User:KingAndGod/Draftify log)) if you want it to show up somewhere else. As for copying the entire source – you can do so if you want, just provide attribution as per the CC-BY-SA-3.0 licence (just like any other Wikipedia page, see WP:Copying within Wikipedia) and make sure edit summary links go to your version of the script. The downside of doing so is that you then don't get any updates if I fix bugs, or add/improve features. - Evad37[talk]00:24, 23 April 2018 (UTC)[reply]
Also note that the logs aren't just for you; they also make it easier for others to review your draftications. Allowing non-standard titles could potentially somewhat obscure the logs. - Evad37[talk]00:38, 23 April 2018 (UTC)[reply]
Okay thanks! I was looking to make the maintenance logs more consistently titled with the prefix "log-" for proper sorting (e.g. log-draftify, log-prod, log-speedy, etc). KingAndGod11:05, 23 April 2018 (UTC)[reply]
Currently, the "Move to draft" link is shown on all pages, even talk pages and special pages such as logs and user contributions pages. It would also be confusing for pages that are already in the draft namespace. The script should therefore be fixed to only show the link in the "More" menu in the Vector skin or between the "history" and "move"/"delete" (for admins) tabs in the Monobook skin on non-redirect articles in the main namespace excluding disambiguation pages. GeoffreyT2000 (talk) 21:23, 23 April 2018 (UTC)[reply]
Partly done. Fixed the namespace detection - that was there previously but I broke it in a recent update. Detecting mainspace pages on which the script shouldn't activate is a bit more tricky. - Evad37[talk]00:13, 24 April 2018 (UTC)[reply]
Edit summaries
Is there a way to make the edit summary changeable when using this tool? I would like to be able to put the reason for moving to draft in the edit summary where it can be seen by all instead of just the talk page message to the creator. Natureium (talk) 19:52, 6 June 2018 (UTC)[reply]
@Natureium: Just to clarify, are you talking about just the user talkpage edit, the page move itself, or all the edits made by the script? - Evad37[talk]02:04, 7 June 2018 (UTC)[reply]
Sorry, I'm talking about the page move itself, where it says "(Undersourced, incubate in draftspace (via script))" It would be nice to be able to change "undersourced" to whatever is appropriate, such as in articles that are unsourced and contain nothing but an infobox. Natureium (talk) 13:53, 7 June 2018 (UTC)[reply]
Would it be possible to add a checkbox (which would be checked by default) to decide if we want to leave the AfC template or not? Given ACPERM I feel that the template is unnecessary on a good number of articles I move to draft and it would be nice to not have that template on there for editors that don't need to go through AfC but who are still creating articles which might be best put in draft space temporarily. Best, Barkeep49 (talk) 15:30, 18 September 2018 (UTC)[reply]
I think it's best to treat the contribution as the editor's "draft" than the editor's "article", which assumes some sort of affiliation/ownership with the topic. After all, the tool is moving a draft, not an article. czar18:41, 26 January 2019 (UTC)[reply]
@Czar:Siddiqsazzad001 does have a point that the current phrasing is a bit inconsistent: An article you recently created ... I've moved your draft to [[Wikipedia:Draftspace|draftspace]] ... where you can incubate the article with minimal disruption ... When you feel the article meets Wikipedia's [[WP:GNG ... click on the "Submit your draft for review!" button. - Evad37[talk]23:30, 26 January 2019 (UTC)[reply]
It's your script so fine with whatever you choose but I don't think it's necessary to call it a "draft" each time. As is, it's "your draft" and "the article" (or "article you created") but not "your article". czar00:11, 27 January 2019 (UTC)[reply]
Hi! You've probably answered this a dozen times already, but ... is there a way to suppress notifications to the article creator? I'm thinking of a situation where an editor has created about twenty articles with insufficient sourcing, where of course if I decide to move them to draft I don't want to leave twenty notifications, but one hand-written one. Justlettersandnumbers (talk) 21:35, 30 March 2019 (UTC)[reply]
Big thanks to both of you. Since I posted this, I have ended up doing a few manually to avoid sending the notification; the extra work and the mistakes I made made me realise just how valuable this script is. So thanks again! Justlettersandnumbers (talk) 08:53, 13 April 2019 (UTC)[reply]
Option for mulitiple Authors?
Greetings, Where it asks Initial author can a pipe ( | ) be used to add more than one authors? Today for an article written in 2009 I did override Author to a more current editor. Wondering if script allows several editors? Also, if left blank will it skip the Author notification? Can I fill in my own Username to "send-to-self"? Regards, JoeHebda (talk) 18:27, 10 April 2019 (UTC)[reply]
This morning I tested by using myself as "Notify author" and yes that does work. BTW, thanks for the Checkbox for Notify--very handy, especially for dormant & blocked authors. Also testing, I did change wording on the actual notification here. Added timestamp & attempt to clarify wording. Cheers! JoeHebda (talk) 14:13, 13 April 2019 (UTC)[reply]
Draftify log
@Evad37: Please see this post on my talk page. I sometimes use this script when reviewing new pages. However, I do not want the script to try to create a draftify log in my userspace. An admin salted the page: See here. Is there a way to configure the script that prevents it from trying to create a draftify log without the use of creation protection? Also, please ping me when you answered this question. Interstellarity (talk) 19:23, 31 July 2019 (UTC)[reply]
Wasn't the log optional? I thought the edit summary search was sufficient. Was it discussed somewhere other than this talk page? czar16:35, 4 August 2019 (UTC)[reply]
@Evad37: if you want to add this, some code that you could use at the start of the draftifyLog function:
I thought there was some further discussion re logging from a couple of years ago, maybe at NPP or a guideline talkpage, but I haven't yet been able to actually find any - Evad37[talk]06:32, 6 August 2019 (UTC)[reply]
@Evad37: This is also the case for me: I do not wish to have a Draftify log at all when I use the script, as it gets annoying for me to click "Skip" every time the prompt asks me to log draftication. Jalen Folf(talk)16:45, 13 October 2019 (UTC)[reply]
Draftifications should be logged. Consider for example this move by Interstellarity. It fails the conditions written at WP:Drafts#Moving articles to draft space. It is, essentially, a backdoor, non-transparent mode of deletion. If the author (typically the sole watcher) is intimidated or inactive, unilateral draftification is a de facto deletion. After six months of no edits, it will be deleted per G13. There is a long history of “unsourced” being proposed and rejected as a CSD#A* deletion criteria, and “undersourced” is both subjective and a long way short of that. New article draftifications involve considerable trust, and without a log it is quite difficult to review the draftifiers draftifications. —SmokeyJoe (talk) 12:37, 18 October 2019 (UTC)[reply]
@SmokeyJoe: Using a userspace subpage wasn't ideal for such a log anyway – users could opt-out by getting the page salted as per the above, or by not using this script for some or all draftications; or make it more difficult to review by manually editing the page. I've added a new draftification log tool to the latest version of this script – User:Evad37/MoveToDraft#Draftity log – which will show all draftications, including from all users if you don't put in a username. It doesn't (yet) show deleted pages as red links, and may have one or two other bugs, but seems to work well enough in my initial testing. - Evad37[talk]07:28, 19 October 2019 (UTC)[reply]
varretry=confirm("Could not retrieve page wikitext:\n"+extraJs.makeErrorMsg(c,r)+"\n\nTry again?");
on line 295. However, this is shown when there is an error with retrieving the page pagetriage status, not the wikitext. Can you update the message? Thanks, --DannyS712 (talk) 16:57, 19 October 2019 (UTC)[reply]
I've been using MoveToDraft for a while, and it's wonderful. Thanks for writing it. Would it be possible to produce a "MoveToUserspace version? -- RoySmith(talk)15:28, 30 January 2020 (UTC)[reply]
Per Wikipedia:Global rights policy, Global rollbackers may use the ... suppressredirect function[] on the English Wikipedia only in the context of counter-vandalism efforts. Moving pages to the draft namespace is not in the context of counter-vandalism efforts, so the script should leave a redirect behind when a global rollbacker (who isn't also a page mover or sysop) draftifies an article. * Pppery *it has begun...02:19, 27 May 2020 (UTC)[reply]
Any such cross-namespace redirect left behind would then be tagged as WP:R2 and deleted. Surely there is a more elegant solution? czar02:24, 27 May 2020 (UTC)[reply]
Streetdeck, there's a concern that if you use the MoveToDraft function (which you have got installed in your common.js), it may use your global rollbacker priv to suppress the redirect which would otherwise be created. The script doesn't ask, it suppresses automatically. As that move is not strictly counter vandalism the suppression of a redirect could technically be in breach of the Wikipedia:Global rights policy#Global rollbackers. Cabayi (talk) 11:22, 27 May 2020 (UTC)[reply]
Hi. Just noticed this... is the link in the more menu supposed to be "DraftiFy log" or "DraftiTy log"? If it's supposed to be the former, you might want to fix line 1110 and the documentation page. Cheers, --Mdaniels5757 (talk) 02:12, 3 August 2020 (UTC)[reply]
Suggestion: Don't close the modal if the "Move page" step failed
I'd suggest removing the $("#M2D-modal").remove(); part in the "Move page" step. A move fails if the draft page already exists. What I want to do instead is to choose a new title.
The reason this would be a much better option is that removing the modal makes me lose the work I put into writing a custom edit summary and custom explanation to the author (a generic "Undersourced, incubate in draftspace" is usually not the best explanation).
First, make the script automatically add ((Drafts moved from mainspace|date=Month Year)) to all pages it draftifies. This is so that the number of edits by JJMC89 bot can be reduced.
Second, if it notices that an article has already been draftified by someone else, then it should abort the draftification instead of moving the draft to the same title but with a number suffixed at the end. This has happened at least two times:
I came here to say the same thing. The current edit summary and notification text is way out of line with policy; what makes an article "undersourced" isn't defined anywhere (except for BLPs) and neither of the guidelines above mention lack of sources as a reason to move a page to draft. I think this is confusing to new editors and contributes to reviewers misusing draftspace, if they follow the text of this tool rather than the policy. Something that allows the review to choose from the list of criteria at WP:DRAFTIFY, and better explains to the creator what draftspace is and what they need to do to return the article to mainspace, would be much better. – Joe (talk) 09:43, 11 December 2020 (UTC)[reply]
Done I've updated the script's user interface to request users check their draftifications are appropriate per WP:DRAFTIFY, and that they add to or replace the default text the script generates (which I also updated). Eventually I would like to redo the interface with mw:OOUI, and perhaps make it more like a wizard, or at least check if the supplied draft title exists, and automatically show a preview of the notification texts (that updates as you type). But that will have to wait until I have more time - Evad37[talk]07:06, 17 December 2020 (UTC)[reply]
Is there an error?
I edit (mostly) from mobile and whenever I load any wikipedia page, I get a notification that states: "An attempt to load a user script has failed. Please see JavaScript console for more information." – the bold "user script" is a link that lands on user:Evad37/MoveToDraft.js. Is there a bug with the Draftify tool? – DarkGlow (contribs • talk) 21:22, 25 January 2021 (UTC)[reply]
Hey Evad. Thanks for making this script. Quick feature request. Perhaps create a setting we can add to common.js that will have the draftify script automatically watchlist the old page and the new page upon draftifynig. Hope that helps. Thank you. –Novem Linguae (talk) 14:54, 11 March 2021 (UTC)[reply]
Help
Hello Evad37, and thanks for developing this script with amazing features. However, it appears there is a possible bug in this script. I have draftified many non-notable or/poorly sourced articles using this script. However, I am not sure why some deleted or active articles appear in my article creation list at xtools when i have never created them? The issue is only with a few articles such as Seyed Ebrahim Amerian, Dominica at the 2019 World Athletics Championships and Arya Linux (OS). Is there any option to remove them from my article creation list, please? TheBirdsShedTears (talk) 16:56, 2 August 2021 (UTC)[reply]
@TheBirdsShedTears: The basic process the script follows is pretty much the same as manually moving an article into draftspace and then doing some cleanup edits. The automatic creation of a redirect as a result of the move can't be suppressed unless you have admin or page mover rights. If another tool is showing these pages as article creations instead of redirect creations, then you need to file a bug report or feature request with that tool's maintainers. - Evad37[talk]06:32, 3 August 2021 (UTC)[reply]
I don't know if this is related. When a draft already exists the script generates an error message with 'Try again' and 'Cancel' buttons. Going back to March 2020 when I first started using the script, pressing the 'Try again' always brought up the error message again so I started pressing the cancel button and re-running the script adding a 2 to the end of the draft article name. More recently, I have pressed the wrong button by mistake (Try again instead of Cancel) and the script has run. Looking at User:John B123/Draftify log the first instance of 'Draft:Draft' was 15 May 2021. --John B123 (talk) 20:46, 23 August 2021 (UTC)[reply]
Acknowledged, it would be useful for admins. This would be a new feature, the earlier discussion you reference was the link unexpectedly appearing on non-existent pages (without any code to actually handle undeletions) - Evad37[talk]09:50, 14 January 2022 (UTC)[reply]
I'm running into a strange problem right now with your script, not with my use (I find it very helpful), but another editor. Somehow, they are able to suppress the redirect, which is fine, but then the script recreates the original page and tags it with a speedy deletion tag, CSD R2. So, there was no redirect left, then the page is created with a request to delete that page. I'm not sure if this page will be around when you see this message but an example is Noorpora. The editor involved, does not have page mover rights and should not be able to suppress the redirect but they might have some global privileges which enable them to do this. There is a discussion at User talk:Ts12rAc#Pravav.S.S.
I not only use your script frequently, but I also delete a lot of crossname space redirects left behind and I haven't run into this situation before. Sometimes new editors create User pages that only include a tag for their deletion but they are usually trying things out with tagging, this is the only situation I've run into with an experienced editor. Thanks for any insight you can provide. LizRead!Talk!20:22, 28 January 2022 (UTC)[reply]
...no one is suggesting "let's overrule the global rights policy" so come on. Where have you stated your actual recommendation to resolve this? Are we looking at something like: (1) Make sure the redirect is unsuppressed, (2) tag for R2, and (3) then carry through the R2 deletion if the user has the rights or leave the R2 tag if the user does not? czar04:09, 29 January 2022 (UTC)[reply]
@Evad37: Then, you should modify your script to create a new variable named "noRedirect" and move the code in lines 341 and 342 to another place so that administrators and page movers have "noRedirect = 1" and other users have "noRedirect = 0". Then, "noredirect: 1" should be replaced with "noredirect: noRedirect" at what is currently line 335 (which will inevitably shift to a different line number)., and "!noRedirect" or "noRedirect === 0" should then appear at what is currently line 340 (and now that the inside code is short enough, line 343 could be shifted up to the end of line 340). Again, the resulting line numbers will be shifted.
A Community Wishlist Survey proposal for this would then look like the following:
Extended content
Problem: When a global rollbacker draftifies an article using User:Evad37/MoveToDraft.js, the redirect is suppressed contrary to global rights policy and then a new page with just the R2 tag on it is created.
Who would benefit: Global rollbackers
Proposed solution: Make the script suppress the redirect only if the user is an administrator or a page mover.
I had the same problem back in November, and I was promptly told by an admin to do something else on enwiki. Currently moving pages to draft without script, which is a bit inconvenient, but it's not the end of the world. ~StyyxTalk?^-^08:21, 16 February 2022 (UTC)[reply]