Skip to content
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.

Avoid use of wp_filter_post_kses to prevent lossy slash handling #2848

Closed
kadamwhite opened this issue Oct 17, 2016 · 1 comment
Closed

Avoid use of wp_filter_post_kses to prevent lossy slash handling #2848

kadamwhite opened this issue Oct 17, 2016 · 1 comment

Comments

@kadamwhite
Copy link
Contributor

As discussed in slack following #2840, there are other places than #2788 where @westonruter's comments around the lossy slash handling in wp_filter_post_kses come into play; we should standardize these to use the underlying wp_kses functions.

Quoting @rachelbaker,

if we are not trusting the slash handling of wp_filter_post_kses() then we should do that consistently, and switch to wp_kses_post() or wp_kses() with the {filter_name}

@rachelbaker rachelbaker added this to the 2.0 milestone Oct 18, 2016
desrosj added a commit to desrosj/WP-API that referenced this issue Oct 19, 2016
@nylen
Copy link
Member

nylen commented Nov 3, 2016

This is being addressed at https://core.trac.wordpress.org/ticket/38609 along with unfiltered_html

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants