[wp-meta] [Making WordPress.org] #1250: DevHub: The RegEx in fix_unintended_markdown() filter is catching post content
Making WordPress.org
noreply at wordpress.org
Tue Aug 9 22:52:06 UTC 2016
#1250: DevHub: The RegEx in fix_unintended_markdown() filter is catching post
content
---------------------------+---------------------------
Reporter: DrewAPicture | Owner: drewapicture
Type: defect | Status: closed
Priority: normal | Milestone:
Component: Developer Hub | Resolution: fixed
Keywords: has-patch |
---------------------------+---------------------------
Comment (by coffee2code):
In [changeset:"3796"]:
{{{
#!CommitTicketReference repository="" revision="3796"
developer.wordpress.org: Use a better approach to preventing
`fix_unintended_markdown()` from running against explanations.
* Revert [1914].
* In `get_explanation_field()`, don't run value through 'the_content'
filter. It's not applicable for all fields. And post_content is already
passed through the filter in the template prior to display (thus this also
prevents double-filtering).
* Temporarily unhook `fix_unintended_markdown()` from 'the_content' filter
when outputting the explanation content.
* Hook 'the_content' for `fix_unintended_markdown()` at a priority of 1.
Also, it's a filter, not an action.
See #1250.
}}}
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1250#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list