Privacy component

A weekly meeting for the Privacy component is held every Wednesday @ 19:00 UTC.

A bug scrub for the component is held every Monday at 15:00 UTC.

Both meetings are held in the #core-privacy room on Slack.

Recent posts on the make/core blog

View all posts tagged privacy.

94 open tickets in the Privacy component

94 open tickets defect (bug) enhancement feature request
5.3 2 6 1
Awaiting Review 10 29 1
Future Release 9 36 0

94 open tickets. Last 7 days: +0 tickets

6 tickets that have no replies

View list on Trac

  • #46536  wp_create_user_request should sanitize the action_name using _wp_privacy_action_request_types
  • #46560  Personal Data Export email unit tests found in erasure fulfillment
  • #46619  Introduce 'Mark as Completed' action and bulk action to the privacy export requests ui administration
  • #46687  Make Privacy Policy Guide easier for users ui administration privacy
  • #46884  Add option to allow individual child-site Privacy Policy pages on multisite administration multisite privacy
  • #47250  i18n: Merge similar translation strings in privacy policy administration

9 tickets slated for 5.3

View list in Trac

  • #43890  Allow Admin to Skip e-mail confirmation for Export/Anonymization
  • #43895  Organize privacy functions into logical files and classes
  • #44133  Should the Data Export indicate when we have no information on the user administration
  • #44314  `user_confirmed_action_email_content` filter run on two different strings
  • #44588  Denote the Copy action is complete by updating the Copy button to state 'Copied' administration
  • #44669  Privacy Notification doesn't clear after dismissing notification
  • #44839  Privacy-data-requests-tables: Remove inline CSS, move it into a css file instead
  • #45491  Personal Data Report – item descriptions administration
  • #46303  Update wp_privacy_send_personal_data_export_email to provide the same filters as _wp_privacy_send_erasure_fulfillment_notification

94 open tickets

Open bugs: 21. View list on Trac

Help maintain this component

Component maintainers:

Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.

Contributors following this component: