[wp-trac] [WordPress Trac] #44379: GDPR filters should provide either $request or $request_id
WordPress Trac
noreply at wordpress.org
Fri Jun 15 23:11:17 UTC 2018
#44379: GDPR filters should provide either $request or $request_id
-----------------------------+------------------------------
Reporter: garrett-eclipse | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Privacy | Version: trunk
Severity: normal | Resolution:
Keywords: | Focuses: privacy
-----------------------------+------------------------------
Description changed by Otto42:
Old description:
> Hello,
>
> While discussing #44376 and reviewing #44235 I realized that the GDPR
> email filters should provide either the $request object or $request_id so
> if users are trying to replace $email_data using the filter they can
> recreate some of it that relies on the request.
>
> That affects these filters;
> user_confirmed_action_email_content
> user_request_action_email_subject
>
> By supplying the request (id or object) in the filter then customizations
> can be made which insert request specific information, etc.
>
> For instance if you want to replace the confirm_url with a custom one you
> would want the request information on that custom confirm_url so your
> custom interception function knows what request is being confirmed.
>
> Hope that makes sense,
> Cheers
New description:
Hello,
While discussing #44376 and reviewing #44235 I realized that the GDPR
email filters should provide either the $request object or $request_id so
if users are trying to replace $email_data using the filter they can
recreate some of it that relies on the request.
That affects these filters;
* user_confirmed_action_email_content
* user_request_action_email_subject
By supplying the request (id or object) in the filter then customizations
can be made which insert request specific information, etc.
For instance if you want to replace the confirm_url with a custom one you
would want the request information on that custom confirm_url so your
custom interception function knows what request is being confirmed.
Hope that makes sense,
Cheers
--
--
Ticket URL: <https://core.trac.wordpress.org/ticket/44379#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list