Authorisation before Publishing

Next topic

Author	Message
diederik de tuinman	Tuesday 23 March 2004 5:14:05 am Hello, For a news site i want people to create their article, but not being able to publish it right away. I want the articles first being authorized before publishing. I already tried to assign different roles but there seems no such thing as dividing the creation and the publishing of an article.Is this possible? Kind regards, Diederik
Amina Bacar	Tuesday 23 March 2004 5:32:31 am Hi, Did you tried workflows? You can use Approve event for that. Amina.
diederik de tuinman	Wednesday 24 March 2004 4:29:54 am Thanks for your input. I tried the approval event and when a content editor creates an article it's not immediately published. But the next problem occurs as I cannot find the article back anywhere. There is no message or what so ever. Diederik
Balazs Halasy	Wednesday 24 March 2004 4:36:42 am Hello, Setting up an approval event/mechanism is explained in the "Building an eZ publish site" tutorial: http://ez.no/ez_publish/documentation/building_an_ez_publish_site/the_guestbook/implementing_an_approval_mechanism Hint: remember that you probably have to run the cronjobs script in order to get the node from the original author to the approver, and finally to its published state. This script must either be run manually or by making use of a scheduler mechanism (such as the cron daemon on *NIX systems). Balazs
diederik de tuinman	Wednesday 24 March 2004 5:14:55 am Up and running thanks.. Diederik

eZ debug

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	587.9063	152.6250
Module start 'layout'	0.0053	0.0028	740.5313	39.4453
Module start 'content'	0.0081	0.7050	779.9766	554.0391
Module end 'content'	0.7130	0.0020	1,334.0156	12.1641
Script end	0.7150		1,346.1797

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.4496	16	0.0002
Check MTime	0.0013	0.1758	16	0.0001
Mysql Total
Database connection	0.0008	0.1126	1	0.0008
Mysqli_queries	0.6604	92.3570	65	0.0102
Looping result	0.0008	0.1130	63	0.0000
Template Total	0.6781	94.8	2	0.3391
Template load	0.0019	0.2638	2	0.0009
Template processing	0.6762	94.5682	2	0.3381
Template load and register function	0.0002	0.0235	1	0.0002
states
state_id_array	0.0011	0.1491	1	0.0011
state_identifier_array	0.0031	0.4283	2	0.0015
Override
Cache load	0.0016	0.2206	27	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0937	3	0.0002
Fetch class attribute name	0.0017	0.2317	6	0.0003
XML
Image XML parsing	0.0007	0.0915	3	0.0002
class_abstraction
Instantiating content class attribute	0.0000	0.0020	6	0.0000
General
dbfile	0.0017	0.2446	16	0.0001
String conversion	0.0000	0.0016	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
5	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs