Page MenuHomePhabricator

Automatic/default protection for images
Closed, DeclinedPublic

Description

Author: webmaster

Description:
I propose is a variable in LocalSettings.php, which can be set to 'protected',
'semi-protected' or 'unprotected'. The point being that all newly uploaded
images are by default set to the appropriate permission.

I am not sure whether the new semi-protection functionality has been implemented
for the image(file) namespace yet, but if it hasn't it would serve just as useful.

Some sites are bound to get more vandalism than others and may be inclined to
set their permissions to 'protected', thus locking images into the database,
preventing 'overwrite' vandalism. Furthermore, until [[Bug:2099]] (undeletion
(reversion) of images) is more properly handled, it might be a good way to
prevent image loss.


Version: unspecified
Severity: enhancement

Details

Reference
bz5204

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 9:09 PM
bzimport set Reference to bz5204.
bzimport added a subscriber: Unknown Object (MLST).

robchur wrote:

(In reply to comment #0)

I am not sure whether the new semi-protection functionality has been implemented
for the image(file) namespace yet, but if it hasn't it would serve just as useful.

Protection acts upon all namespaces, except Special. You would enable "semi
protection" using the autoconfirm group in the usual manner.

I would be inclined to not take behaviour out of the user's control, although I
can see the reasons for doing so. We might consider adding a "Protect this
image" checkbox on the upload form, next to the "Watch this image" and "Ignore
warnings" ones.

What you're asking for can be accomplished already by setting
$wgGroupPermissions['user']['reupload'] = false;

(In reply to comment #2)

What you're asking for can be accomplished already by setting
$wgGroupPermissions['user']['reupload'] = false;

for which version(s) of MediaWiki ? (Version info missing in this bugzilla)

webmaster wrote:

(In reply to comment #2)

What you're asking for can be accomplished already by setting
$wgGroupPermissions['user']['reupload'] = false;

Thanks Brion...
That ought to accomplish the task of 'locking' all images quite nicely.

(In reply to comment #1)

Protection acts upon all namespaces, except Special. You would enable "semi
protection" using the autoconfirm group in the usual manner.

I would be inclined to not take behaviour out of the user's control, although I
can see the reasons for doing so. We might consider adding a "Protect this
image" checkbox on the upload form, next to the "Watch this image" and "Ignore
warnings" ones.

Rob,

Could we still get that 'protect this image' checkbox?
It would add a great deal of functionality and convenience where a 'total
lockdown' is not needed.

Thanks guys!

robchur wrote:

(In reply to comment #3)

for which version(s) of MediaWiki ? (Version info missing in this bugzilla)

The permission "reupload" is checked in MediaWiki 1.6 and above.

robchur wrote:

Reopening with respect to comment 4; the request for a one-off "protect this
image" checkbox on upload.

I don't think that would be generally needed; only sysops would be able
to use it, and clicking the protect tab after uploading is *exactly* the
same number of clicks. I'd rather see protection remain consistent in the
UI and not encourage it by default.

WONTFIX.

webmaster wrote:

Fair enough that it should remain consistent, BUT despite being the same amount
of clicks, it is NOT the same amount of *page loads*.

Therefore, an additional server burden for page rendering.
Large sites could see a small (READ: TINY) performance increase, if lots of page
protection is happening.

In fact, it might even be MORE beneficial to add the 'protect page' checkbox to
articles, such that you save the additional 2 page loads on each of those
scenarios as well.

I wonder how many page protections some of the larger wikis see?
(Please reconsider re-opening)

Very, very few compared to the ~thousand page views per second.