Please see the following comment for the motivation behind this request: https://bugzilla.mozilla.org/show_bug.cgi?id=675795#c0
This permission should not be granted to ordinary users.
Depends on: 677814
Summary: Do not allow ordinary users to move pages → Permission for moving pages
Whiteboard: u=administrator c=siteadmin p= → [user-interview] u=administrator c=siteadmin p=
This is currently open to all, in Kuma. To gate it with access control, I think we'd wrap the ability to change title and slug with a permission. Slug actually changes the URL, but we might as well cover title too. One question: Should a user be able to move/rename a page he or she created?
I think yes. I don't know if Kuma still has a "user sandbox", but a user should be able to create a page in a scratch area, and move it into its "real" location when it's "done". Or they may realize that they created a page in the "wrong" location; letting them move it without bugging anybody would be good. In that case, the key thing is making the move dialog more self-explanatory than in MindTouch. MT's move dialog confuses people and causes them to do the wrong thing.
Component: Website → Landing pages
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Landing pages → User management
Whiteboard: [user-interview] u=administrator c=siteadmin p= → [user-interview]
Les, do you think we should keep this open? IIRC we manage this "permission" with Waffle currently, but I know that may not be the best solution.
Severity: normal → enhancement
Whiteboard: [user-interview] → [user-interview][type:feature][triaged]
(In reply to John Karahalis [:openjck] from comment #4) > Les, do you think we should keep this open? IIRC we manage this "permission" > with Waffle currently, but I know that may not be the best solution. Waffle should only ever be thought of as a temporary gate to a feature in testing. We should never consider it permission control.
We need to get this tied to the "Can move a tree of pages" permission now, so we can start letting trusted localizers move pages to keep up with the massive reorg the English content is undergoing. Can we get this done in the next few days, please?
This would be good, even if we didn't foresaw how much this would be needed with the reorg; ideally we would like to have this for next Saturday (Paris l10n Sprint Week-end) Feedbacking Maris.
James, Les, what do you think about comment 6? Would it be possible to tie the permissions together in time for the docs sprint on April 26th?
(In reply to Māris Fogels [:mars] from comment #8) > James, Les, what do you think about comment 6? Would it be possible to tie > the permissions together in time for the docs sprint on April 26th? I'm not really familiar with page move, but what we could probably do by then is: 1) Wrap the feature in a Django permission 2) Create a new user group, grant the permission to the group 3) Add users as needed to the group via Django admin That would require whomever wants to share the permission to get comfortable navigating Django admin views & adding users to a group. Anything more user friendly is on a much farther horizon.
I can get this together in the next couple days.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/70b658ba3b9d6567309f91ae51bb01305276ccd6 Bug 675842: Remove waffle flag for page move. This removes the waffle flag check that controls access to the page move view; going forward, access will be controlled by the permissions infrastructure. https://github.com/mozilla/kuma/commit/eb926aefdab2fdaa78c2ad7998c94f66ccb0459e Merge pull request #2322 from ubernostrum/page-move-no-waffle Bug 675842: Remove waffle flag for page move.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
5 years ago
You need to log in before you can comment on or make changes to this bug.