Fix - Finder: Indexer Parsers break search result descriptions #4327 #4345
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
|
First test in referenced entry: #4327 (comment) |
|
@Kubik-Rubik: Do you have better test instructions? I can't reproduce it at this moment. |
|
@test: I was able to reproduce the issue and the fix solves both issues mentioned in the original tracker. |
phproberto
pushed a commit
that referenced
this pull request
Oct 8, 2014
rdeutz
pushed a commit
to rdeutz/joomla-cms
that referenced
this pull request
Oct 24, 2014
…oomla#4327. Fixes joomla#4345 Fix - Finder: Indexer Parsers break search result descriptions joomla#4327
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.
See discussion here: #4327
How to test?
In the comments you can find a link to a page from where you can copy the article text (view source code and copy&paste). For the second issue just copy the example in the description of the linked entry.
Create two articles with the example content. Enter the content in an article and run the indexer of the smart search component. Then go to the frontend and search for the articles. After applying the patch you should not see parts of the HTML code in the first and no spaces in the second article!
Thank you for reporting @andykirk!