Bug 16370 - XMLBrowser search - does not work with periods/dots in search term
: XMLBrowser search - does not work with periods/dots in search term
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 7.5.0
: PC Windows (legacy)
: -- normal (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-17 13:55 UTC by Adrian Smith
Modified: 2016-03-10 08:05 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Smith 2010-07-17 13:55:11 UTC
Slim::Web::XMLBrowser does not handle '.' in the search term correctly.  This needs escaping in some way as otherwise when the index level is split the search term is treated as multple levels of the index.

Slim::Control::XMLBrowser escapes the search term before adding to the index - this is probably the solution.
Comment 1 Adrian Smith 2010-07-17 14:14:04 UTC
Alan - suspect this still exists in onebrowser branch, so ccing you as the default routing seems to go to noone?
Comment 2 SVN Bot 2010-07-19 00:52:24 UTC
 == Auto-comment from SVN commit #31065 to the slim repo by ayoung ==
 == http://svn.slimdevices.com/slim?view=revision&revision=31065 ==

Bug 16370.
URI-escape search terms added to crumbs, etc.
Do not put actual search feed, or a feed with a 'url' element which is a ref in streaminfo, even if the feed has no items.
Comment 3 Alan Young 2011-02-10 04:26:59 UTC
It looks to me that this has been merged properly in one browser.

Is this fixed now?
Comment 4 Adrian Smith 2011-02-12 04:29:42 UTC
Alan,

I'm not sure this works fully at present.  If you search for something with a dot in it which has more than one page of results, clicking on the second page gets the first result (not the second page).  Also if you click on an item the search term in the breadcrumb loses the dot.

My test case is searching for artist "a.b" in my spotify plugin - but I am sure there are other cases to create this.

More fundamental question - will the onebrowser xmlbrowser changes be back ported to 7.6 (which was my assumption when suggesting this was fixed in onebrowser).  I think it would be useful to at least incorporate the xmlbrowser changes so we have a more consitent sent of xmlbrowser interfaces even if it is not used for other browsing.
Comment 5 Michael Herger 2016-03-10 08:05:11 UTC
*** Bug 17373 has been marked as a duplicate of this bug. ***