[wp-trac] [WordPress Trac] #44707: The user should be able to create additional requests when previous duplicates are complete or archived
WordPress Trac
noreply at wordpress.org
Fri Mar 15 16:27:02 UTC 2019
#44707: The user should be able to create additional requests when previous
duplicates are complete or archived
---------------------------------------------+----------------------
Reporter: garrett-eclipse | Owner: desrosj
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 5.2
Component: Privacy | Version: 4.9.6
Severity: normal | Resolution: fixed
Keywords: has-patch has-unit-tests commit | Focuses: privacy
---------------------------------------------+----------------------
Changes (by desrosj):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"44906" 44906]:
{{{
#!CommitTicketReference repository="" revision="44906"
Privacy: Allow new requests to be created after a user’s existing one has
been completed.
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.
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/44707#comment:30>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list