Bug 11458 – XMLBrowser Jive search minimum should be 1

Bug 11458 - XMLBrowser Jive search minimum should be 1

Summary:

XMLBrowser Jive search minimum should be 1

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	XML
Version:	7.3.3
Platform:	PC Windows XP

Importance:	-- normal (vote)
Target Milestone:	7.4.0
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-03-24 14:08 UTC by James Richardson
Modified:	2009-10-05 14:31 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description James Richardson 2009-03-24 14:08:51 UTC

Searching on single entry fields fails  

xmlbrowser's input is len 3, should be 1

Currently, IP3K can have an input len of 1 with out failure

Comment 1 Chris Owens 2009-03-30 17:32:44 UTC

Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out.  If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it.

Thanks.

Comment 2 Chris Owens 2009-03-31 08:55:14 UTC

For some reason Bugzilla did not change the target when I did this yesterday.  Or maybe it was me.  In either case, I'm trying it again.

Comment 3 James Richardson 2009-10-05 14:31:49 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.