unnecessary limitation in policy edit of hide function?

Next topic

Author	Message
nigel dodd	Tuesday 05 July 2005 9:18:26 am In version 3.6.0, while it seems possible to assign a role to, for instance, <b>edit</b> only classes of type myClass, it does not seem possible to assign a role to <b>hide</b> just classes of type myClass. I would like my editors to be able only to hide objects of a certain class, not running around the site hiding anything they see fit. Like the can_edit flag, why can't the can_hide flag be applied whenever a node is accessed and according to permissions? Since I want my editors to only be able to hide objects that they can already edit I suppose I can add that flag to the object class, but I have just come across the hide facility and my policy is not to re-invent what is already there.

Author

Message

Tuesday 05 July 2005 9:18:26 am

In version 3.6.0, while it seems possible to assign a role to, for instance, <b>edit</b> only classes of type myClass, it does not seem possible to assign a role to <b>hide</b> just classes of type myClass.

I would like my editors to be able only to hide objects of a certain class, not running around the site hiding anything they see fit.

Like the can_edit flag, why can't the can_hide flag be applied whenever a node is accessed and according to permissions?

Since I want my editors to only be able to hide objects that they can already edit I suppose I can add that flag to the object class, but I have just come across the hide facility and my policy is not to re-invent what is already there.