FANDOM


  • It would be good if there was a script that would make it so administrators would be able to select revisions of pages for deletion, much like how they can already select individual revisions to be restored.

    For years, I've had this idea in my head, and have been wondering myself for ages, why there isn't already something that can do those things. Delete specific revisions for deletion, so only users with (deletedtext) and (deletedhistory) can see them, and only users with (undelete) can restore them.

    Considering that there's something that allows administrators and content moderators to restore specific revisions, surely there ought to be something that would allow administrators to delete specific revisions.

    Unlike (deleterevision) which can hide revisions from local groups, my suggestion would only delete individual revisions in the same manner as (delete) but give administrators the ability to select revisions rather than the entire page.

      Loading editor
    • This is technically impossible. MediaWiki does not allow deleting specific revisions except for RevisionDelete.

      EDIT: not impossible in a clean way.

        Loading editor
    • it's possible, but absolutely needless. staff can delete specific revisions, if needed. that's enough, cuz there is no reason to delete revision that not removed by staff.

        Loading editor
    • Fngplg wrote: it's possible, but absolutely needless. staff can delete specific revisions, if needed. that's enough, cuz there is no reason to delete revision that not removed by staff.

      There are reasons that I'm aware of. Because there are few pages that cannot be restored once deleted, so it would be impossible to do it the normal delete and undelete way. So as far as I'm concerned, it's far from needless.

        Loading editor
    • Fngplg wrote: it's possible, but absolutely needless. staff can delete specific revisions, if needed. that's enough, cuz there is no reason to delete revision that not removed by staff.

      You mean deleting page and then restoring specific revisions?

        Loading editor
    • C.Syde65#4
      There are reasons that I'm aware of.

      provide those reasons to staff and revision will be deleted.
      Rendann#5
      You mean deleting page and then restoring specific revisions?

      smth like
        Loading editor
    • Rendann wrote:

      Fngplg wrote: it's possible, but absolutely needless. staff can delete specific revisions, if needed. that's enough, cuz there is no reason to delete revision that not removed by staff.

      You mean deleting page and then restoring specific revisions?

      Nope. Not at all. Especially given that certain pages in certain namespaces cannot be restored once deleted. So deleting the page and attempting to restore the specific revisions would fail miserably. Deleting the specific revisions however would address that concern.

        Loading editor
    • There are certain MediaWiki messages that can't be restored once deleted, and once you've exceeded more than 500 revisions of a MediaWiki message, you cannot delete the revisions that you don't want to keep, and preserve the revisions that you do want to keep. That makes it rather awkward to pin down when exactly you added a specific code to the page so that it helps you to remember what feature the code is related to.

      Deleting edits that are identical to other edits results in a tidier revision history, and keeping all that is needed to be kept on the surface. There are far too many revisions to sort through and decide which you don't need and which you do need, and then ask Staff to delete those specific revisions.

      For one thing, you may end up having to send multiple requests every time you've decided that you want some revisions to be deleted, and then there's the possibility that Staff may not see why it's necessary for you to be deleting all these useless revisions.

        Loading editor
    • C.Syde65 wrote: There are certain MediaWiki messages that can't be restored once deleted, and once you've exceeded more than 500 revisions of a MediaWiki message, you cannot delete the revisions that you don't want to keep, and preserve the revisions that you do want to keep. That makes it rather awkward to pin down when exactly you added a specific code to the page so that it helps you to remember what feature the code is related to. Deleting edits that are identical to other edits results in a tidier revision history, and keeping all that is needed to be kept on the surface.

      Why not just use comments?

        Loading editor
    • What do you mean by that?

        Loading editor
    • C.Syde65 wrote: What do you mean by that?

      Do you actually not know what a comment is?

        Loading editor
    • I know what a comment is. I'm not stupid. But what kind of comment?

        Loading editor
    • C.Syde65 wrote: I know what a comment is. I'm not stupid. But what kind of comment?

      just think about it for a second

        Loading editor
    • What comments? I mean, what namespace am I putting the comments, what for, and why?

        Loading editor
    • C.Syde65 wrote: What comments? I mean, what namespace am I putting the comments, what for, and why?

      Reread your whole thread over again

        Loading editor
    • Just tell me what you mean. It's not my job to go round trying to solve puzzles.

        Loading editor
    • C.Syde65 wrote: Just tell me what you mean. It's not my job to go round trying to solve puzzles.

      I've already told you what I mean.

        Loading editor
    • Well maybe I should wait for someone else to respond, because I haven't a clue what kind of comments you are talking about.

        Loading editor
    • I had to ask another user instead. CSS comments. Because the size of the CSS file is large enough as is. And once Common.css is retired, I'm going to have to move everything that's on the Common.css page and add it to the Wikia.css page, which is going to add 47,664 bytes by 17,104 bytes which will equal 64,768 bytes. 47,664 bytes for a Wikia.css page was large enough, but 64,768 bytes. Users have been criticised for having large CSS pages, and adding CSS comments is only going to make the page larger still. And once I start to remove the codes that apply to elements that have been removed from Wikia, I'm going to have to verify if those codes really only affect no longer existing elements. In order to do that, I often have to browse the page history for the dates that I added those codes so that I can get some idea what elements those codes affect. Some codes I can remember what elements they affect, but I can't be expected to remember what every code affects, given the amount of code there is in total. And the revisions that I'm looking for are buried among the revisions that no one cares about, because they were draft revisions. So that's where the need to remove individual revisions comes in.

        Loading editor
    • user have been criticised not for css size itself, but for needless rules and using bad practice like "create extra wide rule, then fix it by adding more specific reverting rules".

      also
      (function() {
        if (wgAction !== 'history') return;
        var revs = [294950, 294952];
        var $revs = $('input[type="radio"]');
        revs.forEach(function(v) {
          $revs.parent().find('[value="' + v + '"]').parent().hide();
        });
      }());
      place it into ur personal js, fill revs array by revisions, in manner like above, ..., enjoy.
        Loading editor
    • C.Syde65
      C.Syde65 removed this reply because:
      I was too focused to remember that, lol.
      08:49, May 22, 2018
      This reply has been removed
    • C.Syde65 wrote: Does that even work? Also how do I use it? I understand the rev part, but how do I specify what page?

      Oh wait. Never mind. I forgot to remember that revisions don't require the name of the page because each revision number can only be used once, and in chronological order.

        Loading editor
    • Fngplg wrote: user have been criticised not for css size itself, but for needless rules and using bad practice like "create extra wide rule, then fix it by adding more specific reverting rules".

      also
      (function() {
        if (wgAction !== 'history') return;
        var revs = [294950, 294952];
        var $revs = $('input[type="radio"]');
        revs.forEach(function(v) {
          $revs.parent().find('[value="' + v + '"]').parent().hide();
        });
      }());
      place it into ur personal js, fill revs array by revisions, in manner like above, ..., enjoy.

      I'm guessing that only hides the revisions from view personally. It doesn't actually delete them?

        Loading editor
    • Why changing this for other users? Once, I posted something in Council and was told "ew custom cursor". That taught me "a change that is personal taste or controversial can go without harm".

        Loading editor
    • yep. still serves ur purpose.

        Loading editor
    • Well true. But what about when I want to go from revision to revision, by clicking the previous and next revision links? What will happen then?

      Also it could cause confusion with the revisions, because those revisions won't be seen on the surface, but since they won't really be deleted, they won't be found in the deletion logs either. I know this will only affect me but still.

      Oh yeah, and another concern that I have - I'll be surprised if this is the only other concern that I'll have - it probably won't show 500 revisions in the page history at a time. Or does it?

        Loading editor
    • it will show 500 - hidden

        Loading editor
    • What do you mean?

        Loading editor
    • Fngplg wrote: it will show 500 - hidden

      I'm not sure what you mean by that.

      Also there are other questions in my previous message that haven't been answered.

        Loading editor
    • Like, literally.

        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.

Fandom may earn an affiliate commission on sales made from links on this page.

Stream the best stories.

Fandom may earn an affiliate commission on sales made from links on this page.

Get Disney+