Approve event

Author Message

Marko Žmak

Sunday 06 November 2005 7:10:27 am

The aprove event is used to aprove publishing of an object in eZ, thah I know. It works OK when e new object i created. But I would like to know does it work when an exsisting object is edited, and how?

What I would actually want to know is can editing of an exsisting object be approved/rejected?

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Bruce Morrison

Sunday 06 November 2005 3:01:50 pm

Hi Marko

The approve event is a before/publish event,which means it gets triggered each time an object is sent for publishing. So, yes it gets run for the initial object as well as any subsequent edits and works exactly the same in both cases.

Cheers
Bruce

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Marko Žmak

Tuesday 08 November 2005 3:24:05 pm

Thanks for the reply. Another question. Can the same thing be done for deleting or moving an object? It seems to me the answer is now, but I would like someone to confirm that.

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

Bruce Morrison

Tuesday 08 November 2005 4:13:45 pm

Hi Marko

The only places it's possible to inject workflow in the content module is reading & publishing (without hacking the core dist of course).

See kernel/content/operation_definition.php

Cheers
Bruce

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

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 19 2025 14:00:45
Script start
Timing: Jan 19 2025 14:00:45
Module start 'layout'
Timing: Jan 19 2025 14:00:45
Module start 'content'
Timing: Jan 19 2025 14:00:45
Module end 'content'
Timing: Jan 19 2025 14:00:45
Script end

Main resources:

Total runtime0.0129 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0046 589.0313152.6094
Module start 'layout' 0.00460.0023 741.640639.4141
Module start 'content' 0.00690.0044 781.054793.2891
Module end 'content' 0.01140.0015 874.343834.3047
Script end 0.0129  908.6484 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002216.7055140.0002
Check MTime0.00097.3548140.0001
Mysql Total
Database connection0.00075.392210.0007
Mysqli_queries0.002216.825730.0007
Looping result0.00000.085110.0000
Template Total0.00129.410.0012
Template load0.00064.911210.0006
Template processing0.00064.461710.0006
Override
Cache load0.00043.405510.0004
General
dbfile0.00064.667080.0001
String conversion0.00000.046240.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs