Forums / Developer / Workflow trigger on delete content

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Workflow trigger on delete content

« 
Previous topic
|
Developer
|
Next topic
 »
Author Message

Rainer Scharinger

Friday 23 January 2009 5:43:19 am

Hi,

I am looking for a trigger on content delete and I found a kernel hack (http://ez.no/developer/contribs/hacks/content_remove_workflow).

Is this kernel hack part of the new 4.10?

Is there another way without touching the kernel code to execute my code when content is deletet?

Regards,

Thomas

Damien Pobel

Sunday 25 January 2009 4:28:58 am

HI Rainer,

This feature request comes again and again :
- http://issues.ez.no/12445
- http://issues.ez.no/10754
- http://issues.ez.no/10176
- http://ez.no/developer/forum/suggestions/requesting_remove_triggers

But this is not yet part of Exponential 4 even if it would be very useful ! This kernel hack is for Exponential 3.7 but a similar code should work with Exponential 4

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

Amine BETARI

Wednesday 06 April 2011 7:35:20 am

and it's always like that even if it is 2011
is that this problem has been resolved?

Peter Keung

Wednesday 06 April 2011 8:27:25 am

There are now a bunch of triggers that can be enabled in workflow.ini:

[OperationSettings]
# Deprecated : AvailableOperations. Use AvailableOperationList instead.
# AvailableOperations=content_publish;before_shop_confirmorder;shop_checkout
# AvailableOperations=content_publish;content_read;shop_confirmorder;shop_checkout
AvailableOperations=

# List of available trigger operations.
AvailableOperationList[]
AvailableOperationList[]=content_publish
# Other extra available operations
# Note that the code which is used to 
# implement them may be changed if needed
# we will not apply BC rules for these ones
# AvailableOperationList[]=content_sort
# AvailableOperationList[]=content_move
# AvailableOperationList[]=content_swap
# AvailableOperationList[]=content_updatemainassignment
# AvailableOperationList[]=content_addlocation
# AvailableOperationList[]=content_removelocation
# AvailableOperationList[]=content_updatepriority
# AvailableOperationList[]=content_hide
# AvailableOperationList[]=content_delete
# AvailableOperationList[]=content_updatesection
# AvailableOperationList[]=content_read
# AvailableOperationList[]=content_updateinitiallanguage
# AvailableOperationList[]=content_updatealwaysavailable
# AvailableOperationList[]=content_removetranslation
# AvailableOperationList[]=content_updateobjectstate
# AvailableOperationList[]=content_createnodefeed
# AvailableOperationList[]=content_removenodefeed
# AvailableOperationList[]=user_activation
# AvailableOperationList[]=user_password
# AvailableOperationList[]=user_forgotpassword
# AvailableOperationList[]=user_preferences
# AvailableOperationList[]=user_setsettings
AvailableOperationList[]=before_shop_confirmorder
AvailableOperationList[]=shop_checkout
AvailableOperationList[]=shop_addtobasket
AvailableOperationList[]=shop_updatebasket

That "content_delete" trigger operation will enabled "content/delete/before" and "content/delete/after".

http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada