From: Shaun M. <sh...@ae...> - 2005-02-23 14:41:52
|
On 23 Feb 2005, at 13:34, Matthew McNaney wrote: > > This is in place but you have to hand-hold with the permission system. > For the example the blog entries have int column for authorization. > 0 - Anyone can see this blog > 1 - Registered users can see this blog > 2 - Registered groups who have view permission for this item can see > it. > That would mostly work but I'm not that keen on this method as it puts the emphasis on the module developer to implement permissions in each module and in the case of the example isn't fine grained enough for some. For instance, you might want to make some blog entries readable for guests and some for registered users only. Also if you had a level of user above registered, how do you specify that they can read the special articles for them only, without also opening them up to normal registered users? eg. for paid content. I really think it should be item based permissions not module level. Couldn't it be at a more core level like the level fatcat is at with a similar kind of interface so that you could pick a permission level from predefined groups? That was my reasoning behind the dropdown with a list of groups on any module's edit interface or even on say a block in layout mode. Shaun aegis design - http://www.aegisdesign.co.uk |