I admit it: there was confusion on my part :). I should should have put my scripts in ~Library/Application Support/SqueezeCenter/scripts, whereas I was actually putting them in ~Library/Application Support/SqueezeCenter. The displaying on the web page of which scripts folder executescript is looking at is very useful for the confused!
The scripts now display fine as options, and I've turned on debugging for the executescript. I can see that the executescript claims to be running the relevent script files on each event. However, the script file does not actually seem to run. To test this with a simple script, I created a script file "test.sh" in the scripts directory, wired it up to the open event in the executescript plugin settings page, and played a track. The log indicates executescript claimed to run the script file, which had read/write/execute permissions for all users, and contained the following: #!/bin/bash /bin/echo "test" > /tmp/test.log However, the test.log file is never created. The log contains the following: [08-01-23 23:03:46.8663] Plugins::ExecuteScript::Plugin::commandCallbackOpen (265) Execute: File Open [08-01-23 23:03:46.8670] Plugins::ExecuteScript::Plugin::commandCallbackOpen (274) using server pref [08-01-23 23:03:46.8673] Plugins::ExecuteScript::Plugin::commandCallbackOpen (279) Execute: Executing test.sh I used the executescript you attached in your previous post. Thanks for your continued patience :) -- Creeky ------------------------------------------------------------------------ Creeky's Profile: http://forums.slimdevices.com/member.php?userid=9566 View this thread: http://forums.slimdevices.com/showthread.php?t=41941 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
