My error was that I thought I could reuse the same 3 parameter hashes
for every playlist. Now that I've defined a bunch of them with different
IDs it works. Thank you for your help!
One more thing: there's an optional url parameter: "will be a link in
the web interface which the user can click on to get to the settings for
the playlist." 
I thought I could use this to include a short description (html text) of
each playlist when people click on the name of the playlist in DPL. But
somehow URLs like -plugins/RatingsLight/rated.html- always return 404.
I've tried a bunch of URL variations (up and down the folder hierarchy)
but I must be missing the correct one. Do you happen to know the correct
one?

BTW about the scanner/locked db problem: I've been rescanning my library
over and over again (wipecache and standard) and setting/displaying
ratings. There are almost always errors involving the locked db.
Sometimes not even the indispensable $track->url is possible when the db
is locked. Maybe Trackstat didn't have that exact problem because it had
its own database. 
So to avoid unnessary errors and prevent users from thinking they have
successfully rated a song when they haven't I think I might disable
setting ratings until a scan is done and in the meantime display a
message where needed. 
I hope this won't come across as too harsh. I feel it's safer. Since
RatingsLight has about 2 users hopefully not that many people will be
rating songs with RL during a LMS scan and then be terribly outraged.
:-)


------------------------------------------------------------------------
afriend's Profile: http://forums.slimdevices.com/member.php?userid=39306
View this thread: http://forums.slimdevices.com/showthread.php?t=113344

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to