[fix] [issue #56] encoding issue for blog entries on front-page #76
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
added 2 commits
November 22, 2014 17:58
Wordpress already provides a truncated summary with a link to the post (Continue reading ->). so there no need to strip the tags, truncate the text and add a link to the post.
pascaldevink
pushed a commit
that referenced
this pull request
Nov 22, 2014
[fix] [issue #56] encoding issue for blog entries on front-page
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.
The Wordpress RSS already provides a truncated version of the blog post. It also includes a link to the post. So let Wordpress do the heavy lifting. Otherwise if the description is truncated + tags are stripped the text will look a bit weird. You have the text "Continue reading" + the link "More".