Lower limit from 500 to 400 when searching for visits in GDPR data subject search #12803
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I searched for visits in the data subjects export/delete feature (Admin => GDPR tools).
It found 500 visits, when I then clicked on export, the request failed due to missing permissions. This was because the token_auth wasn't available in PHP even though it was sent as part of the request. It worked once I selected 10 less visits. I presume it might be the body length request limit or something that cut part of the request body. Changing it to 400 should improve this but eventually might need to lower it even further and if needed advice users to increase request limit (if that was the problem).