Page MenuHomeMiraheze

"Unpatrollable" Edit
Closed, ResolvedPublic

Description

Nothing too serious, it's more of an annoyance than anything else, but for some reason, there's one edit on this wiki that I own that I just can't seem to patrol. I've been able to patrol every other edit, including other new file uploads, but not this one. When I got to the file and look through every single diff and revision log possible, even at one point going to the API sandbox to try and patrol it that way, I couldn't seem to be able to do it. The "mark this revision as patrolled" button isn't there either, on any of its revisions... is there some "patrol all" that someone could run on this? Or another fix? Kind of a random bug. Thanks!

More information:

Screenshot 2021-04-01 at 2.20.35 PM.png (400×848 px, 58 KB)
^ Screenshot of the revision that won't patrol... (Anyone know how to make it bigger?)

Link to the file itself and its history.
Note: The wiki in question is a private wiki, and needs certain permissions to access.

Let me know if you need anything else.

Event Timeline

Turtle84375 created this task.

I have seen this on Miraheze Commons. It's related to uploaded files, but I'm not sure this is fixable within Miraheze. It may be an upstream bug. My best advice would be to try deleting all versions of that file, including the file page, then restore one or both. I know that magically patrols unpatrolled revisions on pages, so it may work on files as well.

I have seen this on Miraheze Commons. It's related to uploaded files, but I'm not sure this is fixable within Miraheze. It may be an upstream bug. My best advice would be to try deleting all versions of that file, including the file page, then restore one or both. I know that magically patrols unpatrolled revisions on pages, so it may work on files as well.

Hm, interesting. I will try your suggestion and report back with my findings.

Turtle84375 assigned this task to Dmehus.

Success! I did something a little simpler, I just deleted the specific revision that wasn't patrolling, leaving the other "patrolled" updated revisions of the file intact. I'm not sure what went wrong in the first place, but this is now resolved for the moment. Thanks, Dmehus!