WordPress.org

Make WordPress Core

Opened 18 months ago

Closed 18 months ago

Last modified 18 months ago

#44178 closed defect (bug) (worksforme)

Filtering the latest emails due to the upcoming GDPR rule

Reported by: Dono12 Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.9.6
Component: Privacy Keywords:
Focuses: Cc:
PR Number:

Description

I've been trying to convert wp_send_user_request into an HTML email format.
I've had some success so far but I'm having trouble getting the various $action_names
don't know if this is due to a bug.

<?php
switch ( $action_name ) {
                case 'export_personal_data':
                        $description = __( 'Export Personal Data' );
                        break;
                case 'remove_personal_data':
                        $description = __( 'Erase Personal Data' );
                        break;
                default:
                        /* translators: %s: action name */
                        $description = sprintf( __( 'Confirm the "%s" action' ), $action_name );
                        break;
        }

also the user email doesn't
show in my custom email.

Another possible bug:
I'm also getting duplicate emails. The original which is empty only showing the number one and the one I created using filter, "user_request_action_email_content". I've already tried copying all the content within the function wp_send_user_request
into my custom HTML formatted email function but it only breaks at the point of sending, (Send Request).

Since I'm pressed for time, as we all are, I would appreciate it if someone can back to me soon.

Change History (2)

#1 @Dono12
18 months ago

  • Resolution set to worksforme
  • Severity changed from major to normal
  • Status changed from new to closed

Sorry I was wrong. got it going by echoing the content in my custom email. IE: echo $email_datadescription? and so on. This can be marked as solved or deleted.

Again sorry.

#2 @johnbillion
18 months ago

  • Milestone Awaiting Review deleted

No problem!

Note: See TracTickets for help on using tickets.