In forums we have an extremely complex permissions system which makes it impossible to write an sql query to return the correct records. In CMS we can. We certainly can create a permissions system that make it impossible in CMS also. One of the most vocal complaints about the CMS is the number of queries and the computational expense, and this would make it much worse. In addition I would like to keep the admin interface simple. So my preference is to have fewer permissions rather than more.
One comment I would like to make. There are two new content types coming in v404, both of which allow unrestricted use of HTML. Therefore we require HTML permission before anyone is allowed to create or edit one of them. My point is that the permissions are just settings, and we can use them in ways other than what their names suggest.
As I see it the options are:
Have the current permissions plus "edit after publishing."
Keep the current permissions plus expire the author's ability to edit after a set time period (unless they have edit permission).
Assign a separate "can create" permission for each content type, plus the current permissions, plus a new "edit after publishing."
Assign a separate "can create" permission for each content type, plus the current permissions, plus expire the author's ability to edit after a set time period (unless they have edit permission).
Now this is not an election or a referendum, so we don't promise to exactly follow the majority vote. We would like to know what the community wants and we will do our best to deliver that.
__DEFINE_LIKE_SHARE__
04-21-2010, 10:30 PM
العرض العادي
