I accidentally renamed Liangent to Liangent~zhwiki just now but I have reverted this rename. I actually wanted to reject the rename ticket but pressed the wrong button. There was a period when the names of his user page subpages and talk page were not reverted. He reverted the moves but later, the global rename script caused the revisions of his user page and the subpages to be lost. I request to retrieve the revisions from the database and restore his user page and subpages to what they were before.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T97536 GlobalRename is moving over existing pages, causing revisions to go missing (tracking) | |||
| Open | None | T95408 Liangent's user page and user subpages on zhwiki |
Event Timeline
Comment Actions
I suppose we need a javascript confirm button on the rename queue like Special:GlobalRenameUser has?
Comment Actions
Quite sad we would need this. But if there is no other way to prevent users from clicking wrong buttons/get users to do such actions only with caution and on appropriate devices, I agree this is probably a necessary step.
Comment Actions
Hopefully I'll find the time for this tonight, but I can't promise anything.
See also T89051
Comment Actions
I got something, in total we have lost 61 pages:
- all move action to blame https://quarry.wmcloud.org/query/64337
- all affected (gone) page IDs https://quarry.wmcloud.org/query/64341
- revision info of the root page https://quarry.wmcloud.org/query/64326
- revision info of all pages https://quarry.wmcloud.org/query/64339
Seems all are recoverable. since there are several instances tracked in T97536, maybe it's worth writing a maintenance script to correct them.
Comment Actions
Deeply sorry to bother you, but could you help fix this decade-long issue? Or do you know anyone that can claim this task?
Comment Actions
Based my understanding, the work needed here is to recreate the entries of Liangent's user pages in the page table (as @Func's queries show the revisions are still in revision); or move those affected revisions to archive and undelete the pages. Are these usually resolved with ad hoc scripts, or more general maintenance scripts would be needed?