Did you restart LMS? I've looked at the code, and the *only* place this
can occur is fixed with that change.

I hadn't but now have and confirm that is fixed. I assume the LMS web
server must cache the files as well as the browser then?

You can lower the pain testing by running LMS with the --nobrowsecache parameter.

--

Michael
_______________________________________________
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to