Last modified: 2011-06-23 20:22:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T28607, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26607 - Allow disabling of create protection
Allow disabling of create protection
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
1.18.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-06 13:04 UTC by Umherirrender
Modified: 2011-06-23 20:22 UTC (History)
1 user (show)

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


Attachments

Description Umherirrender 2011-01-06 13:04:54 UTC
After fix of bug 26574 I have notice, that the create protection is also not in $wgRestrictionTypes, so it is not possible to disable create protection on a wiki.

This can be more complex, because create protection is listed on Special:ProtectedTitles, not Special:ProtectedPages, the api listed this with list=protectedtitles and not with list=allpages&apprtype=, due to seperated database table.

It is possible to disable create protection?

Thanks.
Comment 1 Roan Kattouw 2011-01-06 14:25:27 UTC
Create protection is not in $wgRestrictionTypes because it's a different beast. Unlike edit, move, upload and any custom restriction types, it's not applied to existing pages but to titles. For this reason, its implementation is completely (? at least mostly) separate from other protection types.

Making it disableable is a legitimate feature request, but it should not be done through $wgRestrictionTypes.
Comment 2 Umherirrender 2011-06-19 16:09:18 UTC
'create' is inside $wgRestrictionTypes since r82853, need testing
Comment 3 Umherirrender 2011-06-19 19:02:07 UTC
Works, but action=protect makes no check, if there are anything to protect, but that is the same, when removing "edit" and "move" from the $wgRestrictionTypes. The Tab "protect" is also there, when there is nothing to protect, but that is not a problem.

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


Navigation
Links