I think displaying ''This revision is deleted.'' in the textbox is bad form,

there's no way to tell if the revision is really deleted or if somebody just
wrote that and saved a revision without looking at the history, I think that
"This revision is deleted." should be displayed on rendering but now when you go
into the source to avoid the ambiguity.

Use wfMsgHtml not htmlspecialchars( wfMsg( ..

You changed the export format, then you have to updated the export format,

make a new docs/export-0.4.xsd based on docs/export-0.3.xsd and define <deleted/>

I think displaying ''This revision is deleted.'' in the textbox is bad

form,

there's no way to tell if the revision is really deleted or if somebody just
wrote that and saved a revision without looking at the history, I think that
"This revision is deleted." should be displayed on rendering but now when you

Agree with Kelly, there's a good reason this bug/feature fix would come in
REALLY handy right now. Cleaning out a few edits from the history of a 5000 edit
article is very difficult to do reliably and efficiently by all reports. So any
enhancements would be greatly appreciated. ++Lar

Please do not make posts that do not have to do with the patch's development.
They send people unnecessary e-mails and clog up the thread so that devs have a
harder time finding relevant info. If you would like to express your support,
just vote for the bug.

This functionality exists for users with oversight anyway, what's the issue?
(Note that replying to that question is relevant, since it clarifies the desired
featureset. ;) )

Please do not make posts that do not have to do with the patch's development.

Understood, sorry, I won't do it again.

This functionality exists for users with oversight anyway, what's the issue?

Seventeen users with the permission isn't enough to deal with the number of
cases in which this comes up. It would be an extremely handy feature for
postings of personal information and copyvios, and there's no reason that this
should be restricted to so few users as those assigned oversight and not all
admins, who can due this now anyway, albeit with significant drawbacks.

The importance of this feature is that there are often times when deletion of a
single edit, or only a few edits, is required. Currently, the only way to do
that is to delete the entire page and restore all of the other edits, which has
the following problems: 1) while the page is deleted it is inaccessible to other
users, 2) it is very difficult on large pages (I nearly crashed my computer
trying to delete [[WP:AN/I]] to remove some edits containing personal
information), 3) one cannot use diffs once the page is deleted to check that the
edit they're trying to delete is in fact the correct one, which can emerge as a
problem on long pages, and 4) one has to click on a MESS of boxes to undelete
large pages, depending (sometimes one can shift-select of use javascript
workarounds, but it's still a pain).

In that case, what you want is for oversight permission to be granted to all
bureaucrats, perhaps, or all sysops, or whatever. This can be done with current
software, it's a policy issue and should be discussed on VPP or wheverever.

If you want the edits to be recoverable, though, that I can understand and agree
with as an eventual goal. I've changed the summary to clarify what the current
situation is.

(Removed needs-review, patch: patch is close to a year out of date and will have
to be rewritten. Changed priority from High back to Normal: this is noncritical
with the oversight feature available in the code.)

This feature was developed by Tietew in the context of problems experienced by
Japanese Wikipedia. I believe that ja community would still prefer edits to be
recoverable - just like deleted pages, deleted revisions should be recoverable
and be subject to inspections when in doubt. (Besides, for some reason, oversight
permission is granted on en wikipedia, not elsewhere, according to the page on
meta. http://meta.wikimedia.org/wiki/Hiding_revisions ).

But the more important reason why this feature is needed is that it will hide
the content of the revision, while keeping the history visible to the public.
Oversight permission as I understand does not do that. And keeping history
information (who contributed to the page and when) is a simple way to comply
with GFDL.

Imagine that you find an infringing material in a past revision of an article,
and that infringing part is inhereted by subsequent revisions down to
the very current one. In the meantime, many valuable contributions are made to
the article. What you can do with this feature is to edit out all the infringing
parts so that the current one becomes clean, and suppress the text of all the
revisions containing the infringement, but keeping the revision history intact,
so that we have on the record who contributed to the current revision of the
article. In contrast, if without this feature, their names will be deleted along
with the revisions they contributed, and reflecting their contributions to the
current revision without proper attribution to them in the revision history is a
violation of GFDL (4I).

If my explanation is not clear, please let me know (in person or here), I am
more than happy to explain it to defend the value of this feature.

In a nutshell, this feature enables us to do things oversight permission cannot
do. It is a simple way to preserve some past contributions that are mixed with
past infringement. Some Japanese Wikipedians like me have been discussing about
this feature from time to time, waiting for the implementation for a long time.

Priority is determined by developers, not the users. It's a way of them telling
you what they plan to do, not you telling them what you want them to do. If you
believe this is an important feature, vote for it and/or submit a patch. This
may or may not speed things along, because MediaWiki is a volunteer project: it
will get done when a dev feels like doing it. Setting the priority field
certainly won't help anything (it's basically not used here anyway).

-Add uption to blockip to hide name from block log, ipblocklist, and listusers.
The block entry goes to the oversight log and users with 'hiderevision' can see
the ipblocklist items.
-Allow for quick, clean, total page suppression. Oversights can do the opposite
by checking an option at special:undelete.
-More cleanup: recentchanges styling, revisiondelete checkboxes, ect...

Also note:
-Instead of rc_log_action I have rc_actiontext to separate log action text from
log comments to better carry over log hiding.
-The rc_log_type is now used and some slight watchlist sql query changes now
allow for watchlist to show log events (bug 5546).

I have a feeling that it's limited to bureaucrats. I haven't had a chance to see any documentation yet, but IIRC the default (commented-out) settings in DefaultSettings.php of MW 1.11.1 had the right assigned to bureaucrats.

(In reply to comment #62)

Why can't sysops use this on Wikimedia projects? I get a permission error when
I go on [[Special:Revisiondelete]]. Isn't it ready?

It could also be that the new core code simply hasn't been synchronized with the WMF servers yet. I keep hoping someone more knowledgeable will notice this thread and answer your questions, Aphaia and Pietrodn...

It could also be that the new core code simply hasn't been synchronized with
the WMF servers yet. I keep hoping someone more knowledgeable will notice this
thread and answer your questions, Aphaia and Pietrodn...

Both. It is not synced, a schema change is pending. Also, it will be tested and reviewed more before being turned on.

Add Comment

Text is available under the Creative Commons Attribution-ShareAlike 3.0 License; code is available under the GNU General Public License or other appropriate open source licenses. By using this site, you agree to the Terms of Use and Privacy Policy. · Wikimedia Foundation · Privacy Policy · Terms of Use · Disclaimer

Column Prototype

This is a very early prototype of a persistent column. It is not expected to work yet, and leaving it open will activate other new features which will break things. Press "\" (backslash) on your keyboard to close it now.