wagtailapproval._signals¶
These are the signals used for internal behavior. Some of these are great places to start if you’re looking at adding your own types to your pipeline.
-
approvalticket_cascade_delete
(sender, instance, **kwargs)[source]¶ This deletes objects from
ApprovalTicket
if they are deleted, to avoid leaking space (a deleted object would otherwise never be freed from the ticket database, as cascades don’t work forGenericForeignKey
without aGenericRelation
). Essentially, this is a custom cascade delete.
-
catch_collection_objects
(sender, instance, created, **kwargs)[source]¶ If newly-created objects are created inside of a collection that is owned by an ApprovalStep, it will automatically take ownership of those objects
-
delete_owned_group_and_collection
(sender, instance, **kwargs)[source]¶ This deletes the owned group and collection from
ApprovalStep
when the step is deleted.
-
delete_owned_user
(sender, instance, **kwargs)[source]¶ This deletes the owned user from
ApprovalPipeline
when the pipeline is deleted.
-
send_published_signals
(sender, instance, **kwargs)[source]¶ This simply watches for a published step or pipeline, and sends a
pipeline_published()
orstep_published()
signal for it.
-
set_document_collection_edit
(sender, approval_step, edit, **kwargs)[source]¶ Sets collection permissions for documents
-
set_image_collection_edit
(sender, approval_step, edit, **kwargs)[source]¶ Sets collection permissions for images
-
setup_group_and_collection
(sender, instance, **kwargs)[source]¶ Create or rename the step’s owned groups and collections