b66ae2b4c1
When dealing with personal data exports and erasure requests, it is important to have a log of all the requests for a specific person. This is often required to confirm when and how many times requests were completed and fulfilled properly. This change allows a new request to be created after a previous data request has reached completed status (`request-completed`) instead of requiring admins to delete or re-initiate the existing request. The latter approach removes the historical log of requests for that user when creating a new request. Full unit tests for the `wp_create_user_request()` function are also included. Props garrett-eclipse, cc0a, birgire, desrosj. Fixes #44707. git-svn-id: https://develop.svn.wordpress.org/trunk@44906 602fd350-edb4-49c9-b593-d223f7449a82 |
||
---|---|---|
src | ||
tests | ||
tools | ||
.editorconfig | ||
.gitignore | ||
.jshintrc | ||
.npmrc | ||
.nvmrc | ||
.travis.yml | ||
appveyor.yml | ||
composer.json | ||
composer.lock | ||
Gruntfile.js | ||
jsdoc.conf.json | ||
package-lock.json | ||
package.json | ||
phpcs.xml.dist | ||
phpunit.xml.dist | ||
webpack.config.js | ||
wp-cli.yml | ||
wp-config-sample.php | ||
wp-tests-config-sample.php |