Last modified: 2011-03-13 18:06:02 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 5204 - Automatic/default protection for images
Automatic/default protection for images
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Lowest enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-08 07:00 UTC by Jamie Hari
Modified: 2011-03-13 18:06 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jamie Hari 2006-03-08 07:00:47 UTC
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.
Comment 1 Rob Church 2006-03-08 07:10:59 UTC
(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.
Comment 2 Brion Vibber 2006-03-08 07:50:01 UTC
What you're asking for can be accomplished already by setting
$wgGroupPermissions['user']['reupload'] = false;
Comment 3 T. Gries 2006-03-08 08:14:50 UTC
(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)
Comment 4 Jamie Hari 2006-03-09 02:16:32 UTC
(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!
Comment 5 Rob Church 2006-03-09 07:24:06 UTC
(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.
Comment 6 Rob Church 2006-03-09 07:24:47 UTC
Reopening with respect to comment 4; the request for a one-off "protect this
image" checkbox on upload.
Comment 7 Brion Vibber 2006-03-09 21:18:05 UTC
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.
Comment 8 Jamie Hari 2006-03-10 01:09:18 UTC
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)
Comment 9 Brion Vibber 2006-03-10 01:20:46 UTC
Very, very few compared to the ~thousand page views per second.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links