I had previously posted suggesting to rename Lock to Archive. I apologise, this feature is not needed at all. It should only be needed where a discussion is quite permanently closed per policy (such as a past request for permissions).
Maybe so.
In this case, such thread should be simply protected using the standard page protection tools available to sysops.
I tried protecting a topic ("safs" on http://ee-flow.wmflabs.org/wiki/User_talk:Maryana ). If an anonymous user then tries to reply, summarize, or edit title, she sees an pink errorbox
- User is blocked
So protect is close to the Lock (former Close) action, except
* users can still Summarize/Edit summary of a locked topic
* the right to Lock can be granted to different classes of users than page protection.
I don't know if protect of a topic could be adjusted to allow summarize.
* users can still Summarize/Edit summary of a locked topic
* the right to Lock can be granted to different classes of users than page protection.
I don't know if protect of a topic could be adjusted to allow summarize.
We should probably make the protect error more friendly, using messages similar to page protection:
You do not have permission to edit this page, for the following reason:
|
(permissionserrorstext-withaction: 1, (action-edit)) and
(protectedpagetext: editprotect, edit)
I worked out some more suggestions here:
- https://www.mediawiki.org/wiki/Thoughts_on_moderation_in_Flo
--
=S Page Features engineer