Skip to content

Conversation

@dereksmart
Copy link
Contributor

Fixes #1673

Adding more strict checks whether to strip slashes when content is parsed/transform()ed for the front end, also adds slashes back for the text in the editor.

@mattwiebe might want to take a look, since this is his baby.

@dereksmart dereksmart added [Type] Bug When a feature is broken and / or not performing as intended [Feature] Markdown labels Mar 2, 2015
@georgestephanis
Copy link
Contributor

Incidentally, I'm not sure if he's back from paternity leave yet, paying attention to his /other/ baby.

@mattwiebe
Copy link
Contributor

I'm back today, actually!

If it fixes the issue, I'm happy. Un-/re-slashing is a steady descent into insanity. 😛

@jeherve jeherve added this to the 3.4 milestone Mar 4, 2015
samhotchkiss added a commit that referenced this pull request Mar 4, 2015
Markdown: don't strip slashes in code blocks
@samhotchkiss samhotchkiss merged commit cf8d324 into master Mar 4, 2015
dereksmart added a commit that referenced this pull request Mar 5, 2015
Adding wp_slash caused more problems than it fixed.
See #1703 for more info
@dereksmart
Copy link
Contributor Author

reverted in ff0b0f7

Will leave more info in #1673

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Feature] Markdown [Type] Bug When a feature is broken and / or not performing as intended

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Backslashes gets stripped from the Markdown code blocks

7 participants