2014-02-05, 09:27
(2014-02-05, 05:40)MilhouseVH Wrote: In the meantime, I've added a property @urlencode=yes|no (default no), which will encode the search term on the "s" option, matching against any encoded urls you may have. This may help you a bit, but the correct fix is to stop the urls from being encoded in the first place. The new property will be in the next release.
I've come up with a workaround that doesn't require the @urlencode property - it will search the database twice, once for the non-encoded search term and a second time with the url encoded search term, then combine the results. Obviously it won't perform both searches if the search term is unchanged after being url encoded.