Needs review
Project:
Linkit
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Jun 2018 at 12:04 UTC
Updated:
5 Jan 2019 at 03:18 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #2
ishani.addweb commented@granholm, Thanks for providing the steps for the easy way of identifying an issue. I tried with the same steps, but not being able to reach with an issue. Please review my attached screenshot. Can you please elaborate more so that we are on the same page.
Thanks again!.
Comment #3
ishani.addweb commentedComment #4
idebr commentedComment #5
idebr commentedComment #6
idebr commentedAttached patch implements HTML entity decoding for the title when added to a Link field.
Comment #7
idebr commentedComment #8
granholm commentedSee next comment.
Comment #9
granholm commentedTested patch linkit-fields_title_double_encoded-2980959-6.patch, and the problem persists when you don't search for an internal article, but paste the url into the search field. If there are quotes (or any other special characters) in the headline, they will be double encoded, like this:
Comment #10
granholm commentedThis patch to Better Autocomplete should fix the double encoding when pasting an internal url to the search field.
Comment #11
anonI wont update BAC as its actually a lib included the wrong way into linkit.
However, it turns out that we are "check_plain-ing" alot more then we need.
If we use filter_xss instead we still provides the security we need and can have the same results for both a search and a url paste.