Add Cascading Delete Features

[joshfeck]

Moving related "Deletion Behavior Refactor" milestone from codebase. Which has some related tickets for reference:

• Cascading Deletion options for models 9984

• Permanently delete any metadata associated with our CPT objects automatically via EEM_CPT_Base when a permanent delete is initiated 9177

• automatically delete related extra meta when deleting an item 6411

• Add bulk delete transactions with chained delete of related registrations & payments 11496

• avoid orphaned data when deleting a WP user that has related events 7961

See also Brent and Darren's comments in https://events.codebasehq.com/projects/event-espresso/tickets/10754

See also the discussion in https://events.codebasehq.com/projects/event-espresso/tickets/10891
where in the end, Mike remarked:

ok I'm going to put this on hold then. This can be incorporated into the cascading deletion code, or invalidated (and the branch removed) once that happens

With regards to a bulk payment deletion feature, I don't think we need to add that. Instead, if we can allow for deleting transactions where all related entities also get deleted, there shouldn't be a need for bulk deleting payments.

See also related GitHub issue #349

[joshfeck]

Two further ideas noted by @nerrad , related to allowing contacts to be permanently deleted:

1. Create an option somewhere in EE for purging the database of records prior to a certain date. That way people would just give the date to purge records for, and we can just delete permanently all related data for that date (that means' some contacts might still remain if there are registrations on that contact that are more up to date).
2. Create the ui/ux for deleting permanently transactions and work out the issues related to that (how are line items affected? How are attached registrations affected) and once that is worked out, then allow permanently deleting contacts but ONLY if all related transactions/registrations are deleted.

[tn3rb]

needs issues created from all of the original codebase tickets

[joshfeck]

https://secure.helpscout.net/conversation/959326568/696772/

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has been stale for a significant period of time without any activity.