Extending ezapprove2

Next topic

Author	Message
Oliver Frommel	Wednesday 05 September 2007 6:11:13 am (I posted the same message to the comment section of the ezapprove2 extension. I just thought that it might be better to ask here. And i am getting notifications on the thread, too :) We would like to extend it to make voluntary approvals possible. Now we have a setup where an "author" (fewer privileges) can write an article that needs approval by an "editor" (more privs). Now we would like the "editor" to send an article he wrote for approval by another "editor". Ideally both of them should be able to approve the article in the end. As you might note this is less of a formal approval but just to cross check the articles on a voluntary basis. Right now this does not work because the articles of the "editor" get published right away, probably because he is in the group which is allowed to approve. Where and how can we start to implement the desired behaviour? There's also a hardcoded reference to a class id in the text which makes me a bit nervous, as I do not completely grasp the code yet. best Oliver
Kåre Køhler Høvik	Thursday 06 September 2007 12:41:51 am Hi In <i>extension/ezapprove2/eventtypes/event/ezxapprove2/ezxapprove2type.php</i>, look up the function : <i>eZXApprove2Type::execute()</i> There's a variable in that function called <i>$userIsEditor</i>. To force all your editors to have their content reviewed, you'll need to add functionality to make sure that this variable is set to false for the users of group editor. Best regards Kåre Høvik Kåre Høvik

Author

Message

Wednesday 05 September 2007 6:11:13 am

(I posted the same message to the comment section of the ezapprove2 extension. I just thought that it might be better to ask here. And i am getting notifications on the thread, too :)

We would like to extend it to make voluntary approvals possible. Now we have a setup
where an "author" (fewer privileges) can write an article that needs approval by an "editor" (more privs). Now we would like the "editor" to send an article he wrote for approval by
another "editor". Ideally both of them should be able to approve the article in the end.
As you might note this is less of a formal approval but just to cross check the articles on a voluntary basis. Right now this does not work because the articles of the "editor" get published right away, probably because he is in the group which is allowed to approve.

Where and how can we start to implement the desired behaviour?

There's also a hardcoded reference to a class id in the text which makes me a bit nervous, as I do not completely grasp the code yet.

best
Oliver

Kåre Køhler Høvik

Thursday 06 September 2007 12:41:51 am

In extension/ezapprove2/eventtypes/event/ezxapprove2/ezxapprove2type.php, look up the function : eZXApprove2Type::execute()

There's a variable in that function called $userIsEditor. To force all your editors to have their content reviewed, you'll need to add functionality to make sure that this variable is set to false for the users of group editor.

Best regards
Kåre Høvik

Kåre Høvik

eZ debug

Timing:	Jan 18 2025 16:19:56
Script start
Timing:	Jan 18 2025 16:19:56
Module start 'layout'
Timing:	Jan 18 2025 16:19:56
Module start 'content'
Timing:	Jan 18 2025 16:19:57
Module end 'content'
Timing:	Jan 18 2025 16:19:57
Script end

Main resources:

Total runtime	0.9176 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	587.8125	152.6094
Module start 'layout'	0.0050	0.0025	740.4219	39.4141
Module start 'content'	0.0075	0.9086	779.8359	523.6328
Module end 'content'	0.9161	0.0015	1,303.4688	8.1875
Script end	0.9176		1,311.6563

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	0.3386	16	0.0002
Check MTime	0.0013	0.1386	16	0.0001
Mysql Total
Database connection	0.0007	0.0740	1	0.0007
Mysqli_queries	0.8756	95.4154	54	0.0162
Looping result	0.0004	0.0460	52	0.0000
Template Total	0.8922	97.2	2	0.4461
Template load	0.0016	0.1785	2	0.0008
Template processing	0.8906	97.0530	2	0.4453
Template load and register function	0.0002	0.0206	1	0.0002
states
state_id_array	0.0007	0.0746	1	0.0007
state_identifier_array	0.0007	0.0786	2	0.0004
Override
Cache load	0.0013	0.1470	19	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0638	2	0.0003
Fetch class attribute name	0.0011	0.1227	3	0.0004
XML
Image XML parsing	0.0006	0.0617	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0009	3	0.0000
General
dbfile	0.0007	0.0769	15	0.0000
String conversion	0.0000	0.0008	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	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: 13 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs