Bug 659 - Options -> Set Music Library Folder does not trap invalid folder path
: Options -> Set Music Library Folder does not trap invalid folder path
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Slimtray
: 5.x or older
: PC Windows XP
: P2 minor (vote)
: Future
Assigned To: Vidur Apparao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-14 16:40 UTC by Bill Burns
Modified: 2008-12-18 11:55 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 Bill Burns 2004-11-14 16:40:20 UTC
Running SlimServer as a service, assigning the Music or Playlist folder to a 
mapped drive letter using the Server Settings web page gives this error message 
(this is not the bug): 

"Oops - "Z:\" doesn't seem to be a valid directory. Try again."

Using the UNC-style path "\\server\folder" does work.

The possibility of a mapped drive letter not working is mentioned in the FAQ, 
even when Slimserver's service has been modified to login as a user account, so 
this error message is not unexpected.

This is the bug: If instead of using Server Settings I use Options -> Set Music 
Library Folder to set the path, I can browse to "Z:\", and this is accepted as a 
valid entry.

Though there is no error message, the invalid path doesn't work, and Slimserver 
will not build the music library index.  There's no clue for the user as to why 
the scan didn't work.

Fix: Selecting an invalid path in Options -> Set Music Library Folder should 
generate the same error message as entering an invalid path in Server Settings.
Comment 1 Blackketter Dean 2005-03-11 16:02:59 UTC
Let's pull the menu item from the windows gui and rely on the server settings interface.
Comment 2 KDF 2005-08-08 10:37:08 UTC
no longer an issue as of 6.1.1
Comment 3 James Richardson 2008-12-15 13:05:59 UTC
This bug appears to have been fixed in the latest release!

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

Make sure to include the version number of the software you are seeing the error with.
Comment 4 Chris Owens 2008-12-18 11:55:32 UTC
Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.