Andreas,
I'd really like to see the output of --d_plugins logging when starting
SlimServer with SlimScrobbler installed in the normal plugin location
as I was sure I had fixed this problem.
James
--
James
James's Profile:
Seems like the plugin still has to be installed *within*
SlimServer.prefPane (right click, "show package contents", put the
SlimScrobbler folder into server/plugins).
Finally.
Andreas
--
AndreasG
AndreasG's Profile: htt
Well, now the plugin is recognized by SlimServer but it doesn't submit
any tracks... I entered my account info 3 times to make sure it is
correct... Submissions with iTunes and the "official" last.fm
application work fine.
*Sigh*
Andreas
--
AndreasG
---
aubuti;138838 Wrote:
> I changed the EOLs to Unix style and all was fixed.
>
Yes! That did it.
(For those interested: I used a tool called LineBreak for the
conversion, it can be found at
http://www.trancesoftware.com/software/)
Thanks!
Andreas
--
AndreasG
At first my linux-based slimserver wouldn't recognize SlimScrobbler
0.36. After searching some threads it appeared that it might be a
problem with the end-of-lines (EOLs). Turns out that the plugin files
used DOS/Win EOLs (cr/lf) instead of Unix (lf). James says he thinks he
has fixed it now, but
ceejay;138640 Wrote:
> - run slimserver with the --d_plugin flag and see what errors are
> generated on startup
>
Would I see the errors at startup (if there were any)? Or do I have to
look in some log file? There are no obvious errors reported.
ceejay;138640 Wrote:
>
> - make sure you have
- run slimserver with the --d_plugin flag and see what errors are
generated on startup
- make sure you have completely cleared out the old plugins before
installing the new ones
- i'm fairly sure that putting plugin.pm straight into the plugins
directory won't work as slimserver won't know what