BugFix for double encoding of posts that get trashed and restored #22
Conversation
This file contains 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
Fixes double encding og shortcode content when trashing then restoring posts.
|
I don't think this is an issue any more, at least with Gutenberg blocks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
Trashing and untrashing posts double encodes SH shortcode content
Steps to reproduce:
Example short code
`[php]
[/php]`
Expected output:
The user should be able trash and restore without altering the content of the shortcode
Actual Output:
The content of the shortcode get double encoded.
Tested with: WordPress 3.6-beta3-24430