Fix lnding page content showing escaped html #1241
Merged
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.
What type of PR is this? (check all applicable)
Description
This PR swaps a location relying on
esc_html
to usewp_kses_post
instead so that escaped html does not appear in the output of parameterized landing pages.Related Tickets & Documents
Proof of Functionality
Accessibility checklist
If your PR includes UI changes, please utilize this checklist:
Error
andWarning
issues?For more info, check out the
Accessibility Checker Documentation.
Quality assurance
[optional] Are there any post deployment tasks we need to perform?
Additional Notes