Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
To be able to do much of anything useful with the tokens provided by tasks, we need entity tokens. We need them to create meaningful email messages like the following:
[gdpr_task:owner:field_first_name] [gdpr_task:owner:field_last_name]
A data request has been submitted to provide an export of your data. It is currently in [gdpr_task:status] status.
Visit <a href="[site:url]user/[gdpr_task:owner:uid]/gdpr/requests">My data requests</a> to see your exported data once it has been reviewed and processed.
Proposed resolution
Review it.
Remaining tasks
User interface changes
API changes
If someone is using the current tokens, this could cause issues as the previously named tokens now provide chained entities for the user relationships.
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#2 | 3026973.patch | 3.76 KB | heddn |
Comments
Comment #2
heddnComment #4
lbesenyei CreditAttribution: lbesenyei at Brainsum for Brainsum commentedThanks for the patch.
There is one part that needed to be changed.
Since we're using strings as status values the "entity_metadata_status_options_list" had to be replaced with a custom callback.
Comment #6
lbesenyei CreditAttribution: lbesenyei at Brainsum for Brainsum commented