Forums / Setup & design / unnecessary limitation in policy edit of hide function?

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

unnecessary limitation in policy edit of hide function?

Previous topic

Setup & design

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

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.