Policy rule

Next topic

Author	Message
Roberto Sacchi	Tuesday 10 March 2009 2:58:56 pm I would like to create a policy rule like that: users can edit an object but they can only save a draft, not publish the modified content. (another rule could be "create but not publish") I don't find that function in the admin panel. Maybe I miss it. Thanks Rob
Jean-Yves Zinsou	Tuesday 10 March 2009 3:50:09 pm Hi there, in fact, it is not the way it supposed to be done. You must allow users to create content, and then define a workflow with an event /approve and a trigger "before publish" . When they will click on "publish" the element will be submitted to a group of approvers. After an approver approves (ha ha) the object will be really published on the site. You can even define a set of users that can publish without approval needed. Se here : http://ez.no/doc/ez_publish/technical_manual/4_0/reference/workflow_events/approve Don't forget : you must properly define the schedule of the matching cronjobs... Hope this helps Have fun ! Jey Do Androids Dream of Electric Sheep? I dream of eZpubliSheep.... ------------------------------------------------------------------------ http://www.alma.fr

Author

Message

Tuesday 10 March 2009 2:58:56 pm

I would like to create a policy rule like that:
users can edit an object but they can only save a draft, not publish the modified content.
(another rule could be "create but not publish")

I don't find that function in the admin panel.
Maybe I miss it.

Thanks

Rob

Jean-Yves Zinsou

Tuesday 10 March 2009 3:50:09 pm

Hi there,
in fact, it is not the way it supposed to be done.

You must allow users to create content, and then define a workflow with an event /approve and a trigger "before publish" .

When they will click on "publish" the element will be submitted to a group of approvers.
After an approver approves (ha ha) the object will be really published on the site.

You can even define a set of users that can publish without approval needed.

Se here :
http://ez.no/doc/ez_publish/technical_manual/4_0/reference/workflow_events/approve

Don't forget : you must properly define the schedule of the matching cronjobs...
Hope this helps

Have fun !
Jey

Do Androids Dream of Electric Sheep?
I dream of eZpubliSheep....
------------------------------------------------------------------------
http://www.alma.fr

eZ debug

Timing:	Jan 31 2025 03:33:32
Script start
Timing:	Jan 31 2025 03:33:32
Module start 'layout'
Timing:	Jan 31 2025 03:33:32
Module start 'content'
Timing:	Jan 31 2025 03:33:32
Module end 'content'
Timing:	Jan 31 2025 03:33:32
Script end

Main resources:

Total runtime	0.0233 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	588.0078	151.1953
Module start 'layout'	0.0052	0.0042	739.2031	220.6406
Module start 'content'	0.0093	0.0126	959.8438	997.7578
Module end 'content'	0.0219	0.0014	1,957.6016	29.9922
Script end	0.0233		1,987.5938

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	10.7179	14	0.0002
Check MTime	0.0011	4.5674	14	0.0001
Mysql Total
Database connection	0.0010	4.1713	1	0.0010
Mysqli_queries	0.0027	11.4435	3	0.0009
Looping result	0.0000	0.0553	1	0.0000
Template Total	0.0010	4.4	1	0.0010
Template load	0.0008	3.4856	1	0.0008
Template processing	0.0002	0.8709	1	0.0002
Override
Cache load	0.0006	2.3947	1	0.0006
General
dbfile	0.0023	9.9667	8	0.0003
String conversion	0.0000	0.0338	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs