Last modified: 2011-03-13 18:05:31 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 12583 - Add Create permission to Protectedpages
Add Create permission to Protectedpages
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: 12977 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2008-01-11 09:26 UTC by Filip Maljkovic [Dungodung]
Modified: 2011-03-13 18:05 UTC (History)
5 users (show)

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


Description Filip Maljkovic [Dungodung] 2008-01-11 09:26:30 UTC
In [[Special:Protectedpages]], in the Permission: combo box, there are currently only "Edit" and "Move" selections. Since the "Create" permission (for protecting inexistent pages) has recently been added, it should be there as well.
Comment 1 Roan Kattouw 2008-01-11 10:43:22 UTC
This is quite tricky to do, because edit/move protections are in a separate table from create protections. As a consequence, implementing limits is very hard if not impossible. Maybe a separate special page (e.g. [[Special:Noncreateablepages]]) would be better.
Comment 2 Huji 2008-01-11 18:27:46 UTC
Roan, I think [[Special:Protectedtitles]] already does it. Anyways, I almost created a patch which would do what is requested here (which means, by applying that patch, we wouldn't need Protectedtitles anymore, and it would practically be merged to Protectedpages). I couldn't figure a few minor bugs so I left it, and (damn) forgot to save my changes (just reverted it!) Now that I look back, I think it is better to first make sure we really want to merge the two special pages, and then actually offer a patch.
Comment 3 Roan Kattouw 2008-01-13 20:43:44 UTC
I don't know exactly how you've patched it, but I suspect that any implementation of a combined protectedpages-protectedtitles special page would be very ugly database-wise and be shot down by Domas immediately.
Comment 4 Huji 2008-01-14 08:54:40 UTC
Heh. Well what I did was to add lots of IFs in the code, to run the current ProtectedPages code when 'edit' or 'move' are selected, and run the imported code from ProtectedTitles when 'create' is selected! ;) That doesn't have anything to do with the DB-side of the story, but I'm in agreement with you that it makes the code "ugly". That's why I avoid redoing the whole thing unless given a good reason.
Comment 5 Roan Kattouw 2008-01-14 14:37:59 UTC
The entire idea is to be able to present a mixed list of create-protected and edit/move-protected pages, which is hell.
Comment 6 Filip Maljkovic [Dungodung] 2008-02-09 18:39:44 UTC
*** Bug 12977 has been marked as a duplicate of this bug. ***
Comment 7 oysterguitarist 2008-03-01 04:25:18 UTC
What about having cascading on the combo box also, I know it shows up with full but, it might be helful to have cascading on there as well.
Comment 8 Aaron Schulz 2008-03-24 19:16:37 UTC
These really are two different things. One is a list actual pages that are protected, the other is a list of titles that cannot easily be re-created and probably should not exist.
Comment 9 Aaron Schulz 2008-09-05 22:56:17 UTC
Additionally, the code to do this would need two different pagers and the UI would have various nonsense options like "size" for protected titles. I suppose some fancy JS could try and add/remove options...

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