Privacy component

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

A bug scrub is held for the Privacy component every Monday @ 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.

93 open tickets in the Privacy component

93 open tickets defect (bug) enhancement feature request
5.4 1 1 0
5.5 3 1 0
Awaiting Review 11 31 0
Future Release 9 35 1

93 open tickets. Last 7 days: -1 ticket

9 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
  • #46884  Add option to allow individual child-site Privacy Policy pages on multisite administration multisite privacy
  • #47495  WP_Privacy_Request_Table should not show views that have a count of 0.
  • #47940  Introduce privacy tools (Export/Erasure) to the Network Admin for network-wide handling administration multisite privacy
  • #48265  The privacy export files cleanup can run unlink on directories throwing an error.
  • #49319  Admin triggered download of personal data export give notice of user sent link which is invalid ui
  • #49381  Add Javascript Documentation to privacy-tools.js javascript docs

6 tickets slated for 5.5

View list in Trac

  • #44038  Change personal data export path stored in request meta to relative paths administration
  • #44176  Un-map Privacy Capabilities
  • #44222  Add Archive state to privacy requests administration
  • #44264  Give progress indication for export and erasure ui javascript
  • #44314  `user_confirmed_action_email_content` filter run on two different strings
  • #46304  On the privacy request table buttons switch to break-word for legibility ui

93 open tickets

Open bugs: 24. 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: