As some of you know, we’ve been hard at work getting Easy Digital Downloads (and its extensions) ready for the GDPR deadline. Over the last week, all the work we’ve been doing has culminated into what will be version 2.9.2 of Easy Digital Downloads. With this release, we’ve added a host of hooks and filters, which allow developers integrating with Easy Digital Downloads to process their data for export and erasure alongside of Easy Digital Downloads, instead of having to write all their own routines to do so.<\/p>\n
We’ve also included some helper functions to make your export and erasure integrations easier to write.<\/p>\n
Filter:<\/strong> This filter will allow developers to put any custom information into the data export for a customer record. This filter supplies you with the data already chosen for export for the customer, as well as the EDD_Customer object itself. Using this filter should return the Filter:<\/strong> This filter will allow developers to supply additional information for a specific payment (order) that is being provided to the export. This filter supplies you with the data already chosen for export, as well as the EDD_Payment object. Using this filter should return the Filter:<\/strong> Allows developers to supply additional information for the file download log export. This filter will supply you with the existing data, as well as the download log post object, and all the post meta found for the log, so you do not have to look it up again. Using this filter should return the Filter:<\/strong> Allows developers to supply additional information for the API access log export. This filter will supply you with the existing data, as well as the API access log post object. Using this filter should return the Function:<\/strong> Function:<\/strong> The function does have a filter ( Filter:<\/strong> When a customer requests to be deleted, there may be a business need to not allow this anonymization or deletion. By default Easy Digital Downloads will proceed with its determination if the customer should be processed, but before it does, it allows extensions to tell it if the customer should be processed.<\/p>\n The return of this should be in the following array format:<\/p>\n Filter:<\/strong> During the erasure process, all payments associated with the customer found are processed to take one of three actions (and the string used to reference them in the code) :<\/p>\n The status of the payment typically determines what action should be taken, and the action for a specific payment status can be modified by store owners in There are, however, times where an extension may need to override that action, which is where this filter becomes useful. With this filter, developers can inspect a payment and determine if it is allowed to be anonymized based off their own criteria, and tell the eraser to leave it alone, by performing no action on it.<\/p>\n The return of this should be in the following array format:<\/p>\n Action:<\/strong> When a customer requests to be deleted, Easy Digital Downloads first runs anonymization on them (and later determines if they can be fully deleted). After the anonymization is completed, this action is run, supplying the EDD_Customer object, so developers can take any further action necessary. It passes in the EDD_Customer object of the customer being processed.<\/p>\n Action:<\/strong> After Easy Digital Downloads has processed the payment for anonymization, but before saving the payment, this action is run, passing in the EDD_Payment object, allowing developers to make further changes. It passes in the EDD_Payment object of the payment being processed.<\/p>\n Action:<\/strong> In the event that a payment is required to be anonymized (not deleted), the file download logs associated with it are anonymized as well. This action will allow further anonymization of a file download log, if necessary. It passes in the WP_Post object of the $log.<\/p>\n Action:<\/strong> When a user requests deletion, if they have any API Access logs in the database, this action will allow you to take further action after they are deleted. It passes in the WP_Post object of the $log.<\/p>\n So that’s a wrap on our updates to Easy Digital Downloads core for the GDPR release. As with all software projects and legal regulations, this will evolve as the ecosystem deems necessary. All of these hooks, filters, and functions can be found in the As some of you know, we’ve been hard at work getting Easy Digital Downloads (and its extensions) ready for the GDPR deadline. Over the last week, all the work we’ve been doing has culminated into…<\/p>\nedd_privacy_customer_record<\/code>
\nCode:<\/strong> <\/p>\n$export_data = apply_filters( 'edd_privacy_customer_record', $export_data, $customer );<\/pre>\n
$export_data<\/code> array. Items added should be in the following form:<\/p>\n\r\n$export_data[] = array(\r\n 'name' => __( 'Name for the data' ),\r\n 'value' => $value,\r\n);\r\n<\/pre>\n
edd_privacy_order_details_item<\/code>
\nCode:<\/strong> <\/p>\n$data_points = apply_filters( 'edd_privacy_order_details_item', $data_points, $payment );<\/pre>\n
$data_points<\/code> array. Items added should be in the following form:<\/p>\n\r\n$data_points[] = array(\r\n 'name' => __( 'Name for the data' ),\r\n 'value' => $value,\r\n);\r\n<\/pre>\n
edd_privacy_file_download_log_item<\/code>
\nCode:<\/strong> <\/p>\n$data_points = apply_filters( 'edd_privacy_file_download_log_item', $data_points, $log, $log_meta );<\/pre>\n
$data_points<\/code> array. Items added should be in the following form:<\/p>\n\r\n$data_points[] = array(\r\n 'name' => __( 'Name for the data' ),\r\n 'value' => $value,\r\n);\r\n<\/pre>\n
edd_privacy_api_access_log_item<\/code>
\nCode:<\/strong> <\/p>\n$data_points = apply_filters( 'edd_privacy_api_access_log_item', $data_points, $log );<\/pre>\n
$data_points<\/code> array. Items added should be in the following form:<\/p>\n\r\n$data_points[] = array(\r\n 'name' => __( 'Name for the data' ),\r\n 'value' => $value,\r\n);\r\n<\/pre>\n
Erase\/Anonymize Data<\/h3>\n
Helper Functions<\/h4>\n
_edd_privacy_get_customer_id_for_email( $email_address )<\/code>
\nPurpose:<\/strong> Since each registered eraser callback in the WordPress data eraser process is passed the email address, it is possible that a customer may already be modified when your eraser runs. Therefore, early in the process, Easy Digital Downloads finds, and stores the customer id for the email address requesting erasure. By using the _edd_privacy_get_customer_id_for_email<\/code> function, you can rely on our early lookup, so that you can continue to look up by customer id, not the email address, to avoid having any issues due to a customer already having their email address anonymized in a previously registered eraser callback.<\/p>\n_edd_privacy_get_payment_action( EDD_Payment $payment )<\/code>
\nPurpose:<\/strong> As you process data erasures, it may be necessary for you to look up what type of action is supposed to be performed on an EDD_Payment object. This helper function looks up the actions specified in the Downloads > Settings > Privacy > Export & Erase<\/code> section, and then allows extensions to filter the action based off their own criteria.<\/p>\n'edd_privacy_payment_status_action_' . $payment->status<\/code>) which allows the customization on a per-extension basis. An example use case is, normally a completed payment would allowed to be anonymized, but if our Simple Shipping extension is enabled, and the payment has not yet been shipped, we should not allow this payment to be anonymized, as the store owner still needs data from it to be able to correctly ship the item(s) ordered.<\/p>\nFilters<\/h4>\n
edd_should_anonymize_customer<\/code>
\nCode:<\/strong><\/p>\n\r\n$should_anonymize_customer = apply_filters( 'edd_should_anonymize_customer',\r\n array( \r\n 'should_anonymize' => true,\r\n 'message' => '' ),\r\n $customer );\r\n<\/pre>\n
\r\narray( \r\n 'should_anonymize' => true, \/\/ If this customer should be anonymized \r\n 'message' => '', \/\/ If should_anonymize is false, supply a reason\r\n)\r\n<\/pre>\n
edd_should_anonymize_payment<\/code>
\nCode:<\/strong><\/p>\n\r\n$should_anonymize_payment = apply_filters( 'edd_should_anonymize_payment', \r\n array( \r\n 'should_anonymize' => true,\r\n 'message' => '' \r\n ),\r\n $payment\r\n);\r\n<\/pre>\n
\n
Downloads > Settings > Privacy > Export & Erase<\/code><\/p>\n\r\narray( \r\n 'should_anonymize' => true, \/\/ If this customer should be anonymized \r\n 'message' => '', \/\/ If should_anonymize is false, supply a reason\r\n)\r\n<\/pre>\n
Actions<\/h4>\n
edd_anonymize_customer<\/code>
\nCode:<\/strong><\/p>\ndo_action( 'edd_anonymize_customer', $customer );<\/pre>\n
edd_anonymize_payment<\/code>
\nCode:<\/strong><\/p>\ndo_action( 'edd_anonymize_payment', $payment );<\/pre>\n
edd_anonymize_file_download_log<\/code>
\nCode:<\/strong><\/p>\ndo_action( 'edd_anonymize_file_download_log', $log );<\/pre>\n
edd_delete_api_access_log<\/code>
\nCode:<\/strong><\/p>\ndo_action( 'edd_delete_api_access_log', $log );<\/pre>\n
Conclusion<\/h3>\n
includes\/privacy-functions.php<\/code> of Easy Digital Downloads version 2.9.2 or later.<\/p>\n","protected":false},"excerpt":{"rendered":"