https://bugzilla.wikimedia.org/show_bug.cgi?id=38365
--- Comment #11 from Krinkle <[email protected]> --- (In reply to Brad Jorsch from comment #10) > It certainly looks like checking both the move and edit protections for a > page move is intentional: this has been part of the code ever since move > protection was correctly added in r6827. > > I think the UI fix suggested in comment 9 would be the way to go. Although > the definition of "at least" may be problematic, since protection levels > aren't necessarily hierarchical. Indeed, they are not hierarchical. However, as in many places, changing a page requires the ability to edit plus any additional rights. Though this principle could use much better documentation, I don't think it is a bug. We use this in quite a few places. This, for example, allows user groups to be configured with relative ease. There is no need to go out of one's way and figure out all the possible actions a user can take (not to mention actions provided by extensions, it simply doesn't scale). Instead we provide lower-level actions like "edit" and "read" that are intended to cascade through to more impactful actions. Meaning if a page is protected from editing and your user group is not allowed to edit, the fact that your group has the 'move' right in general doesn't matter. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
