ezcontentObjectStates - defaults states
ezcontentObjectStates - defaults states
Wednesday 25 January 2012 11:18:45 am - 1 reply
I've noticed that defaults states are those with priority=0
according to roles and policies, it seams that this feature doesn't match, cause we can imagine user without possibilities to assign state with priority=0. so default state of object should also take in account the current user role. it cout be the lowest priotity, the user has access to.
Tuesday 21 February 2012 4:40:26 pm
Resolved:
I've added a pre-publish event that check if use can change current_state... if not. it will be the lowest priority he can manage. (either pre/post-publish event should be the same, in my case, It sould be post publish for other reasons)
that could be important if object creator should not have access to "publish".
If some one interessed... I can post It
Modified on Tuesday 21 February 2012 4:43:19 pm by Ousmane KANTE
You must be logged in to post messages in this topic!