User talk:BilledMammal/Move+

Latest comment: 6 days ago by Rtkat3 in topic Stalls in Move+

Kudos!

edit

I just tested this out and it's wonderful. Safari ScribeEdits! Talk! 22:20, 16 May 2024 (UTC)Reply

Thank you! BilledMammal (talk) 22:22, 16 May 2024 (UTC)Reply

Issue with mass move

edit

Hey, I closed the discussion at Talk:Snooker world rankings 1976/1977 and tried to mass-move all the articles using the move all button, but the script failed to move them. Not sure why, and a couple of the ones in the middle did get moved (I closed out of the pop-up around that time, as the first several had all failed and I didn't expect any of the rest to work).

I ended up just moving the articles using the script but using the move directly button, which worked okay. Skarmory (talk • contribs) 22:31, 18 June 2024 (UTC)Reply

  • Looking at how it started working a minute after the edits listing the close were done I think that might be due to rate limiting by the servers - I suspect the same issue would have occurred if you had clicked "move directly" from the start.
    I’ve been meaning to implement a more systematic process to prevent rate limiting causing issues, but that wont be a quick fix - for the moment, when closing large multi-move RM’s, maybe wait a minute before clicking any button to start the moves? BilledMammal (talk) 22:45, 18 June 2024 (UTC)Reply

Suggestion for project notifications

edit

Nice script, I plan on testing it out. I was going to make a suggestion over at the talk page for RmCloser when I stumbled upon this script, so I'll leave it here instead as I see myself using this script more.

Sometimes we have RMs on pages that include other pages, which may have wikiprojects not tagged on the discussion page. In that case, it would be handy to have an "other Wikiproject" box in the notification dialog which would allow us to enter or even search for a project (in that case, it might be handy to figure out how the "Rater" script gets its list of projects, but even just a plain "type your own" box might be doable). The only other way presently is to temporarily tag the discussion page, or just do it manually.

Also: the move+ option appears in the menu on pages you shouldn't be able to move, like Special:MovePage (only mentioning this because I can see some users trying to use it there for page swaps, and it pre fills "Special:MovePage" into the from box, which is of course impossible.)

No worries or pressure, just an idea. Keep up the good work! ASUKITE 15:26, 12 July 2024 (UTC)Reply

Thanks, I'll add both of those to the todo list! BilledMammal (talk) 06:26, 20 July 2024 (UTC)Reply

Apparent issue

edit

@BilledMammal: I've reverted a couple broken edits today where this script has removed a redirect entirely when it appears that it did not intend to do so, see here and here. Not sure if this is an issue with the script itself or simply user error but either way it should probably refuse to make such edits. Tollens (talk) 06:20, 20 July 2024 (UTC)Reply

That's bizarre. It has to be the script breaking, but I'm not sure why it will have suddenly started. I'll look into it, thank you. BilledMammal (talk) 06:27, 20 July 2024 (UTC)Reply
I'm struggling to reproduce it. I'll continue looking into it, but if you or other editors have additional examples, please let me know. BilledMammal (talk) 05:28, 21 July 2024 (UTC)Reply
edit

Hi,

I've noticed a few examples of the use of your script where a post-move cleanup leaves links of the form [[A|A]] - for example, here, [[Michael Mosley (broadcaster)|Michael Mosley]] becomes [[Michael Mosley|Michael Mosley]], and here, [[Darren Jones (politician)|Darren Jones]] becomes [[Darren Jones|Darren Jones]]. Is this user error or a shortcoming of the script? Clearly it's not a big problem, but I thought it was worth asking. Jean-de-Nivelle (talk) 12:31, 24 July 2024 (UTC)Reply

That's a failure of the script - it should check whether it will be creating a redundant pipe and not do so. I'll add that to the todo list. BilledMammal (talk) 11:51, 28 July 2024 (UTC)Reply

Failed to move talk page with its article

edit

Leaving it for me to clean up. Script should ensure talk pages move with their articles. See User talk:Wbm1058#My MediaWiki core developers thread. wbm1058 (talk) 11:40, 28 July 2024 (UTC)Reply

It should have, I've not sure what happened there - it's possible that Frostly unchecked "Move talk page". BilledMammal (talk) 11:53, 28 July 2024 (UTC)Reply
No, even when "Move talk page" is checked, the MediaWiki software (until it gets fixed, as I have been attempting to do) the talk page will not automatically move if there is page history blocking the move. The talk page must be moved separately, manually by the human page mover/admin, after the article moved. Since you are usurping manual human tasks with your script, I'd appreciate if you could make the script check to confirm whether the talk page actually moved, and if it did not, then move it as a second, associated move. Since lazy human editors are expecting their scripts to do tedious, manual tasks such as this. – wbm1058 (talk) 12:10, 28 July 2024 (UTC)Reply
Move+ checks the status of the relevant talk pages, and only provides the user with options that will result in both the talk page and the article being moved.
I just tried to move User:BilledMammal/Test page 1 to User:BilledMammal/Test page 4 and it required a Round-Robin move, because while User:BilledMammal/Test page 4 is a redirect the talk page is not. It is possible there is a bug, but I will need to investigate further to determine when it occurs - can you link the page that used to exist at Talk:Victor Cruz? I've been unable to find it. BilledMammal (talk) 12:19, 28 July 2024 (UTC)Reply
You can't find it because I deleted it.
11:12, 28 July 2024 Wbm1058 talk contribs block deleted page Talk:Victor Cruz (G6: Deleted to make way for move from Talk:Victor Cruz (American football))
Actually, there was only a single edit there, a redirect from a page move, so if the box was checked it should have been deleted.
The developers call it a "desired feature", but I view it as a bug. – wbm1058 (talk) 12:32, 28 July 2024 (UTC)Reply
Thank you, identified the bug - it is T12814.
It should be an easy fix, but I don't have time to do it and the required tests right now - I'll do it ASAP. BilledMammal (talk) 12:47, 28 July 2024 (UTC)Reply
Technically the relevant bug is phab:T287590, given that Frost isn't an admin and was using delete-redirect. SilverLocust 💬 22:24, 21 August 2024 (UTC)Reply
It's rather awkward to see a non-administrator coding scripts to do administrator tasks. You might familiarize yourself with how administrators move pages by making yourself an admin on a test wiki. – wbm1058 (talk) 12:17, 28 July 2024 (UTC)Reply

Mass move

edit

It's quite awkward to see the script move three out of seven pages after a move discussion is closed and implemented. If the editor didn't check back to see that the pages are moved, it will eventually result being handled by another editor manually or at RM/TR. Additionally, when there is an option to "move directly" and "move directly without leaving a redirect," the "move directly" option doesn't seem to move the page as it states, even though the logs show the page was moved, instead, it will close asap. This results in the editor having to move the page manually. All these issues complicates handling page moving requests. Except that, the script is very much helpful. Safari ScribeEdits! Talk! 20:48, 4 August 2024 (UTC)Reply

@SafariScribe: The fact that you're seeing "move directly without leaving a redirect" is odd; that was in the original rmCloser, but Move+ does it in a different manner.
I see in User:SafariScribe/common.js you're importing both User:BilledMammal/rmCloserExpanded.js and User:TheTVExpert/rmCloser.js. I think the latter may be conflicting with the former; perhaps try removing it from your common.js and see what happens?
It might also help to update the former to User:BilledMammal/MovePlus.js, but that shouldn't make a difference as rmCloserExpanded.js redirects to MovePlus.js. BilledMammal (talk) 22:30, 8 August 2024 (UTC)Reply
Thank you for the kind explanation. I have done as above. Cheers! Safari ScribeEdits! Talk! 03:23, 9 August 2024 (UTC)Reply
No problem! If you still see issues, let me know! BilledMammal (talk) 03:43, 9 August 2024 (UTC)Reply

Unable to move articles

edit

Somehow I am unable to move articles with your script, most recently with Israeli allegations against UNRWA discussion, which is the simplest move to make, moving to a non-existent title. I tried to see if there are error messages thrown in the console, but there is no error messages emitted. – robertsky (talk) 05:46, 14 August 2024 (UTC)Reply

@Robertsky: that’s odd.
When you tried to move the page, did it give you an option to do so? If it did, when you pressed the button did it just fail to move the page without any message telling you of that appearing on the screen? BilledMammal (talk) 06:37, 14 August 2024 (UTC)Reply
It just fails with a message to contact you upon clicking on the Move button. – robertsky (talk) 06:46, 14 August 2024 (UTC)Reply
Thank’s, I’ll take a look. BilledMammal (talk) 06:58, 14 August 2024 (UTC)Reply

  You are invited to join the discussion at User talk:TheTVExpert/rmCloser § Requesting wikiproject notified template. 142.113.140.146 (talk) 10:42, 18 August 2024 (UTC)Reply

Duplicate pipes

edit

Hello. Is it possible to tweak your script to prevent something like this from happening? Thanks. InfiniteNexus (talk) 16:53, 20 August 2024 (UTC)Reply

If possible, please also prevent the script from piping valid redirects such as this one, per NOTBROKEN. This took a while to clean up; I have also spoken with the editor regarding NOTBROKEN and NOPIPE. InfiniteNexus (talk) 17:24, 20 August 2024 (UTC)Reply
It is, but I’m not sure a hard block is desirable - a valid use is to fix the soon-to-be broken links prior to changing the redirect, to minimise disruption to readers.
However, I could add a warning in such circumstances? BilledMammal (talk) 22:36, 20 August 2024 (UTC)Reply
Yes, the only circumstance where such an action is appropriate would be to fix incorrect links after a page move. Otherwise, this breaches WP:NOTBROKEN. I don't know if it's possible for the script to detect whether the link it's about to add is equivalent to the redirect it is trying to replace, but a warning could help if that's not technically feasible. InfiniteNexus (talk) 22:41, 20 August 2024 (UTC)Reply
It is very feasible - but I think it is also appropriate to fix the links immediately before the move, to minimise the impact on the reader, and I don’t want to prevent that use.
Instead, I think that in circumstances where an editor is trying to change a link from a redirect to the target, it gives a warning reminding editors of NOTBROKEN. BilledMammal (talk) 22:59, 20 August 2024 (UTC)Reply
It is; it’s near the top of my todo list, I’ll try to get to it soon. BilledMammal (talk) 22:36, 20 August 2024 (UTC)Reply
Great, thanks. InfiniteNexus (talk) 22:41, 20 August 2024 (UTC)Reply

Pages sometimes left in Draft:Move/ space

edit
This box dynamically lists any subpages of Draft:Move/

Move+ sometimes leaves pages in Draft:Move/ space. Today I noticed and fixed 44 of them from the Yahoo RM that were left there after step 2 of the round-robin swap didn't use redirect suppression for some reason.

Another example is the chained move Talk:Tommy Robinson#Requested move 18 August 2024. I see that "Add support for chained moves" is on the to-do list, so I won't dwell on that one (details in the collapse box).

Extended content

Redirects were suppressed normally, but the request was A → B and B → C (where C was a redirect with history). Move+ appears to have moved

  1. B → Draft:Move/B
  2. C → Draft:Move/C
  3. A → B
  4. Draft:Move/B → A

And presumably tried and failed to do Draft:Move/C → B, where there was already a page.

A correct set of moves would be

  1. C → Draft:Move/C
  2. B → C
  3. A → B
  4. Draft:Move/C → A

SilverLocust 💬 21:32, 29 August 2024 (UTC)Reply

Here was another instance. Special:Diff/1244596191. SilverLocust 💬 00:49, 8 September 2024 (UTC)Reply
The Yahoo RM errors were my fault; I accidentally interrupted it half way through.
I'll look into the others, thank you. BilledMammal (talk) 11:58, 8 September 2024 (UTC)Reply

U

edit

Hey BilledMammal, cool tool, thanks! Only a little thing, but in the edit summary, how about an upper case 'U' for 'using Move+'? Because it comes after a period, as far as I can see (although I've only used it a few times.) SerialNumber54129 11:48, 8 September 2024 (UTC)Reply

Thank you!
Most cases the "u" doesn't follow a period (for example, this move), but I'll look at adding a check for when it does! However, it isn't much of a priority. BilledMammal (talk) 12:01, 8 September 2024 (UTC)Reply
BM, thanks for that too-quick-for-a-Sunday reply  :) ah, it must've been me that added the period then! D'oh. Sorry about that; it's not that important, as you say. I suppose there's no way, while I'm here, of folding the move discussion close into the move itself? Like, merge discussion closer with it? Anyway, have a good weekend. SerialNumber54129 12:19, 8 September 2024 (UTC)Reply
I’ve got this page on subscribe, and I try to be prompt replying to it.
Can you give an example of what you mean? I don’t quite understand. BilledMammal (talk) 12:42, 8 September 2024 (UTC)Reply

Stalls in Move+

edit

Hi. Yesterday, I was able to run the Move+ by having Ben Grimm's links redirected back to Thing in light of someone moving it back. While using Move+ to correct like someone did when it came to any articles that had their Reed Richards links changed back to Mister Fantastic, I had to do some manual edits when it stalled on Baron Strucker the first time and on Michael Chiklis the second time. Even after the latter happened, it still stalled. Can you find a way to fix this error? --Rtkat3 (talk) 15:39, 10 September 2024 (UTC)Reply