Bug 2867 - customer reported problem with favorites on squeezenetwork
: customer reported problem with favorites on squeezenetwork
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Favorites
: unspecified
: All Other
: P2 normal (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-24 12:28 UTC by Kevin Pearsall
Modified: 2009-09-08 09:12 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2006-01-24 12:28:28 UTC
2. As you know there is a problem with SQN-Favourites. If you put in a lot
of favourites and then delete Favourite no.2 then Fav no.2 doesn't exist
anymore and Fav. no 1 couldn't be moved down anymore.
Comment 1 Sean Adams 2006-02-06 12:53:20 UTC
This sounds like the same issue this customer is reporting:

http://forums.slimdevices.com/showthread.php?p=84350#post84350

"

I am new to Slimdevices and currently I have one SB3 that is connected through a wireless AP to Squeezenetwork. It works otherwise just fine. I added many radio streams, mainly from Shoutcast, as squeezenetwork favorites.
As I was doing this, I have deleted some and added new ones. After a while I noted the numbering of the favorites is not sequential and they can not be reordered. For example: currently I have favorites on location 2,3,5,6,8,12 and so an. The numbers 1,4,7,9-11 are missing and I can not move items up or to mmake it to reorder.
To delete them all and start fresh seems as the only option, but I have so many (>25) favorites. Maybe that is a problem?

Some import/export option would be nice to be able to easily syncronize between say squeezenetwork and local slimserver...
Thanks for any ideas. Lleo_ "
Comment 2 Andy Grundman 2006-02-06 12:54:37 UTC
Fixed in trunk.
Comment 3 James Richardson 2008-12-15 12:15:01 UTC
This bug has been fixed in the latest release of SqueezeNetwork!

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