Fix for success handler for gdpr-privacy-preferences-frm submission#5
Merged
a6software merged 1 commit intodevelopfrom Feb 8, 2019
Merged
Conversation
jenkoian
approved these changes
Feb 7, 2019
This file contains hidden or 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
2 participants
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.
Copy of upstream PR - trewknowledge#244
response.statusis undefined, so usexhr.statuscheck instead - however may not be neededwindow.location.reloadto load page from server, rather than local cacheIt may be that the
200 === xhr.statuscheck is not required. This is the success handler function, so a successful outcome is assumed(?)I haven't updated the
else/displayNotificationfunction, as I'm not sure what the expected contents of theresponse.data...object would be. Perhaps hardcoded with translated error strings?