Created attachment 359 [details]
word doc with screenshots and steps to reproduce

We can't seem to reproduce this.  Can you try the latest 6.0 release and see if it's still happening?  If so, 
please attach the error message again along with the source to the page that's causing the error?

Installed nightly build "SlimServer_v2005-03-24.exe".  Still have the same
script error issue.  I added a screen shot to the attached Word file
showing the music folders specified path, which the software says doesn't
exist.  Depending on which subfolder I am trying to access, I may or may
not get the script error.  For example, the steps I detail in the Word doc
attached gives a script error window after I select "Browse Music Folder"
followed by "Classical".  The error shows up only after clicking on
"Classical" and not when clicking "Browse Music Folder" or any subsequent
selections after "Classical" (i.e. the script error shows up only once and
that's after "Classical" is selected).  If I select "Classic Rock & Rock"
in Step 2 of the Word doc, I do not get an error but the screen shown in
Step 4 appears, so I never can see any of the subfolders in "Classic Rock &
Rock" and the software indicates there is no music folder selected (when in
fact D:\Music\0. Music is shown as the pathway).  All of the subfolders
listed after clicking "Browse Music Folder" behave in one of the two ways
detailed above.

Right now the "Browse Music Folder" and "Browse Playlists" are the only
options having these issues.  Browsing by Albums, Artists, Artwork, Genres
and Years do not have any problems (weird???).

(See attached file: SlimServer 6.0b3 Issue.doc)

Any chance the name of the music folder itself is causing some problem
because it contains the number 0 as a prefix (0. Music)?  This wouldn't
exactly explain why all the other browsing options work, unless the code
looks at the pathway differently.

Doug

Kevin:  Can you get the HTML source (from the browser) for the page that's creating the error?  There 
isn't any javascript in those pages as far as I can tell, so there's something on his particular installation 
that's causing the HTML to get corrupted, it would appear.

trying to...

Created attachment 379 [details]
page source from Doug

hopefully the CR's introduced by e-mailing/cut-n-pasting in to a file don't
make a difference...

OK, this is Default2 (Jacob Potter's effort to put some life into the Default
skin), which is not yet ready. I'll assign the bug to Jacob, but remove the 6.0
target milestone.

Does the same issue happen with the ExBrowse2 skin? I agree that Default2 isn't
ready for 6.0, but a lot of the browse code is pretty much the same between the two.

I've reproduced this. (yay VMWare!) Fix later today.

Fixed in svn 2753.

Doug says the error no longer comes up for him.  Thanks!

This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!