eZContentOperationCollection vs content/updateobjectstate operation

«

Previous topic

|

|

Next topic

»

Author	Message
Marko Žmak	Wednesday 29 June 2011 3:13:50 pm In kernel/state/assign.php we have this part of code: if ( eZOperationHandler::operationIsAvailable( 'content_updateobjectstate' ) ) { $operationResult = eZOperationHandler::execute( 'content', 'updateobjectstate', array( 'object_id' => $objectID, 'state_id_list' => $selectedStateIDList ) ); } else { eZContentOperationCollection::updateObjectState( $objectID, $selectedStateIDList ); } So there's a check if the content_updateobjectstate exists, and if ti doesn't then eZContentOperationCollection::updateObjectState() is used. Why this amibguity? Why do we have the ability to use both ways and not only one? And if I develop an extension that changes object state, what should I use? Which is the proper way of doing it? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Damien Pobel	Thursday 30 June 2011 5:12:59 am Hi Marko, " So there's a check if the content_updateobjectstate exists, and if ti doesn't then eZContentOperationCollection::updateObjectState() is used. Why this amibguity? Why do we have the ability to use both ways and not only one? " It's not exactly a check against content_updateobjectstate existence but against wether the operation is activated or not in workflow.ini/[OperationSettings]/AvailableOperations So both will do the job, but with the operation you can plug a workflow event type while without you can't. This is done this way to avoid the performance penalty of always using the operation even if there's no workflow. Cheers Damien Planet eZ Publish.fr : http://www.planet-ezpublish.fr Certification : http://auth.ez.no/certification/verify/372448 Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish
Marko Žmak	Thursday 30 June 2011 5:27:25 am " This is done this way to avoid the performance penalty of always using the operation even if there's no workflow. " Any idea about how much is the penalty? Is this pinciple, of avoiding using operations where there's no workflow, used consistently through the eZP code? Is it done like this in all parts where we can have/nothave operations and workflows? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Damien Pobel	Friday 01 July 2011 10:30:19 am I'm not sure about the performance penalty... But, yes this is done like this for all operations that were added in 4.2 or 4.3 (I don't remember which version) : $ grep -RH 'eZOperationHandler::operationIsAvailable' * extension/ezjscore/classes/ezjscserverfunctionsnode.php: if ( eZOperationHandler::operationIsAvailable( 'content_updatepriority' ) ) kernel/content/view.php:if ( eZOperationHandler::operationIsAvailable( 'content_read' ) ) kernel/content/translation.php: if ( eZOperationHandler::operationIsAvailable( 'content_updateinitiallanguage' ) ) kernel/content/translation.php: if ( eZOperationHandler::operationIsAvailable( 'content_updatealwaysavailable' ) ) kernel/content/translation.php: if ( eZOperationHandler::operationIsAvailable( 'content_removetranslation' ) ) kernel/content/state_edit.php: if ( eZOperationHandler::operationIsAvailable( 'content_updateobjectstate' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_sort' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_move' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_swap' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_updatemainassignment' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_addlocation' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_removelocation' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_updatepriority' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_createnodefeed' ) ) kernel/content/action.php: if ( eZOperationHandler::operationIsAvailable( 'content_removenodefeed' ) ) kernel/content/removeobject.php: if ( eZOperationHandler::operationIsAvailable( 'content_delete' ) ) kernel/content/removeobject.php: if ( eZOperationHandler::operationIsAvailable( 'content_removelocation' ) ) kernel/content/section_edit.php: if ( eZOperationHandler::operationIsAvailable( 'content_updatesection' ) ) kernel/content/hide.php:if ( eZOperationHandler::operationIsAvailable( 'content_hide' ) ) kernel/state/assign.php: if ( eZOperationHandler::operationIsAvailable( 'content_updateobjectstate' ) ) kernel/user/preferences.php:if ( eZOperationHandler::operationIsAvailable( 'user_preferences' ) ) kernel/user/ezuseroperationcollection.php: if ( eZOperationHandler::operationIsAvailable( 'user_activation' ) ) kernel/user/password.php: if ( eZOperationHandler::operationIsAvailable( 'user_password' ) ) kernel/user/forgotpassword.php: if ( eZOperationHandler::operationIsAvailable( 'user_password' ) ) kernel/user/forgotpassword.php: if ( eZOperationHandler::operationIsAvailable( 'user_forgotpassword' ) ) kernel/user/activate.php: if ( eZOperationHandler::operationIsAvailable( 'user_activation' ) ) kernel/user/setting.php: if ( eZOperationHandler::operationIsAvailable( 'user_setsettings' ) ) Cheers Damien Planet eZ Publish.fr : http://www.planet-ezpublish.fr Certification : http://auth.ez.no/certification/verify/372448 Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish
Marko Žmak	Saturday 02 July 2011 5:31:20 am So I guess disabling some of the available operations for which I don't need workflows could bring some performance improvements... I wonder how much improvement would bring and is it worth the work? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 29 2025 13:45:34
Script start
Timing:	Jan 29 2025 13:45:34
Module start 'layout'
Timing:	Jan 29 2025 13:45:34
Module start 'content'
Timing:	Jan 29 2025 13:45:34
Module end 'content'
Timing:	Jan 29 2025 13:45:34
Script end

Main resources:

Total runtime	0.0143 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.0046	588.4219	151.2422
Module start 'layout'	0.0046	0.0023	739.6641	36.7031
Module start 'content'	0.0069	0.0059	776.3672	102.3750
Module end 'content'	0.0127	0.0015	878.7422	41.9766
Script end	0.0143		920.7188

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	15.5067	14	0.0002
Check MTime	0.0010	7.1280	14	0.0001
Mysql Total
Database connection	0.0006	4.2409	1	0.0006
Mysqli_queries	0.0022	15.5549	3	0.0007
Looping result	0.0000	0.1114	1	0.0000
Template Total	0.0011	7.8	1	0.0011
Template load	0.0009	5.9921	1	0.0009
Template processing	0.0003	1.7512	1	0.0003
Override
Cache load	0.0005	3.7752	1	0.0005
General
dbfile	0.0017	12.0691	8	0.0002
String conversion	0.0000	0.0349	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