Applescript won't function as folder action

Hello There,
Not long ago I discovered a script created by Matt Broughton that printed a file as RAW to a lpr printer. It solved a huge problem for me. It works well as a droplet, but I can't get it to function as a folder action. Here is the script:
on open printJobs
set trapFile to quoted form of POSIX path of (printJobs as string)
do shell script "lp -d printerqueuename -o raw " & trapFile
end open
The goal is to be able to print multiple files. Either a droplet that can handle several items or a functioning folder script.
After fooling around with this for a few months, I've discovered that I am a worthless scripter and can't manage to accomplish the goal.
I will be blunt: I need the script written for me.
Thanks for the help.

Folder Action scripts need to include a very specific handler since that's what the OS will call when the action is invoked.
So all you need to do is edit your script to put it in the appropriate handler.
Right now it's using the 'open' handler, so will run based on files that are dropped on the script. That's not what you need here. As a folder action you need a 'on adding folder items to' handler since that's what's called when items are added to your folder, e.g:
on adding folder items to the_folder after receiving the_files
  repeat with each_file in the_files
    set trapFile to quoted form of POSIX path of (each_file as text)
    do shell script "lp -d printerqueuename -o raw " & trapFile
  end repeat
end adding folder items to
Note the addition of a repeat loop which is needed since there may be multiple files added to the folder at once.

Similar Messages

  • Quicktime export using applescript/folder actions

    I have about 500Gig of encoded H264 footage.
    I want to be able to "bulk" change video properties on all of the video so that when I view it in front row it isn't letter boxed.
    I can do this manually, save as a .MOV and all is fine.
    anyone tried something like this as an applescript?
    I have scripted eyetv quite a bit so I`m quite familiar with applescript, just being lazy I suppose!
    any help greatly received !
    * looking in the quicktime applescript library *
    Steve

    The nature of your question implies that you're unfamiliar with Folder Actions...
    I'd like to skip them or write the AppleScript in a way that handles this.
    By their very nature, Folder Actions are passed a list of newly-added files. Your Folder Action script should look something like:
    on adding folder items to my_folder after receiving the_files
      -- your code goes here
    end adding folder items to
    where, in this case, the_files is a list of the newly-added files. It won't include pre-existing files, so all you need to do is iterate through the_files and you're set. Something like:
    on adding folder items to my_folder after receiving the_files
              tell application "iPhoto"
                        repeat with each_photo in the_files
                                  try
                                            import each_photo to album "Europe 2012"
                                  end try
                        end repeat
              end tell
    end adding folder items to
    The only caveat here that I can think of is the fact it's a DropBox folder, so there might be some odd latency in the files appearing in the directory, but I don't use Dropbox to know.
    Note that in the above I import each photo independently, via a repeat loop. This might not be necessary, and you might be able to pass the entire the_files variable to the import command to have all the images imported in one go - I haven't tried that, though.

  • AppleScript Folder Actions

    I'm new to this group, and my question may have been answered a long time ago as I'm using OS 10.5.8. I've been teaching myself AppleScript, and have been using "AppleScript - The Missing Manual" by Adam Goldstein and "AppleScript 1-2-3" by Sal Soghoian and Bill Cheeseman. All has gone well until now. I'm working on a couple of folder actions and have hit a wall. I've successfully written "on opening..." and "on closing..." actions. However, I have been 100% UNsuccessful at writing "on adding folder items to..." scripts. Action scripts are saved in the proper location, are attached properly, and folder actions are enabled. I turned a primary "on adding..." script (one I started out to do) into a droplet, and it functions perfectly when files are dropped on it. Help in explaining to me "the error of my ways" would be appreciated.

    If there is an error in a folder action script, it tends to fail silently - for example, your *opening folder* script will fail because you are not coercing theCount (a number) to text (display dialog doesn't like lists, which is what you are getting by concatenating a string to a number).
    Since you have a droplet that works correctly, you can just add a folder action handler to that script. I use a folder action template that includes handlers so that it can be run and tested from the *Script Editor* (it can also be used as a droplet). In the following example, the doStuff handler is what does the stuff, and the other handlers (including the folder action) just pass items to it.
    <pre style="
    font-family: Monaco, 'Courier New', Courier, monospace;
    font-size: 10px;
    font-weight: normal;
    margin: 0px;
    padding: 5px;
    border: 1px solid #000000;
    width: 720px; height: 340px;
    color: #000000;
    background-color: #FFD891;
    overflow: auto;"
    title="this text can be pasted into the Script Editor">
    on run -- application double-clicked or run from the Script Editor
    tell application "Finder" to try
    set someItems to (the selection) as alias list
    on error errorMessage number errorNumber
    set someItems to (the selection) as alias as list
    end try
    if someItems is {} then set someItems to (choose file with multiple selections allowed)
    doStuff for someItems
    return
    end run
    on open theFiles -- items dropped onto the application
    doStuff for theFiles
    return
    end open
    on adding folder items to this_folder after receiving these_items
    handle items added to a folder
    parameters - this_folder [alias]: the folder added to
    these_items [list]: a list of items (aliases) added
    returns nothing
    doStuff for these_items
    return
    end adding folder items to
    to doStuff for someFiles
    do stuff with each file in someFiles
    parameters - someFiles [list]: a list of files to do stuff with
    returns nothing
    repeat with anItem in someFiles
    try
    -- do stuff, for example:
    tell application "Finder"
    set theName to name of anItem
    considering case -- case sensitive match
    if "-P" is in theName then
    move anItem to alias "HD:Users:myself:Property:All Property"
    else if "-GP" is in theName then
    move anItem to alias "HD:Users:myself:Photography:General Photos"
    else
    log "no match"
    end if
    end considering
    end tell
    on error errorMessage number errorNumber -- oops
    log errorMessage
    -- activate me
    -- display alert "Error " & errorNumber message errorMessage
    end try
    end repeat
    return
    end doStuff
    </pre>

  • AppleScript: Set folder name of Folder Action?

    Problem:
    How to get the folder name that the running Folder Action script is attached too. Script is functional, stdin bash script with AppleScript via osascript. I just want the folder name, not the POSIX path to it. The System Events dictionary suggests this is possible. I don't want to hardcode the action's assigned folder in the bash script if I can get it dynamically from AppleScript. I know how to return it to bash. AppleScript newbie that has spent several hours googling and testing already.
    Tried:
    tell application "Finder"
         --AppleScript Editor can't get container -- no surprise. Folder action does work
         get POSIX path of (container of ((path to me) as text))
         set workingDir to quoted form of result
         display alert "Current Folder: " message workingDir as critical
    end tell
    tell application "System Events"
         activate
         --AppleScript Editor can't get name of folder action. Folder action does not work
         set currentDir to name of folder action
    end tell
    Appreciation for time and solution in advance.

    twtwtw wrote:
    In that case I suggest you make your life easier.  delete the osascript bit and just return a 0 or 1 from the shell script.  That integer will be passed on to the next action, so add an applescript action that checks to see if the input is 0 or 1 and displays a dialog if necessary:
    on run {input, parameters}
              if input as integer > 0 then
      -- error
      display alert "whatever"
              end if
    end run
    The only reason I posted in the first place was to assess if it was possible to dynamically discover the folder name of the folder action using AppleScript through an osascript request. If the bash script has to be scrapped and entirely rewritten as a Applescript action -- just to obtain the folder name, then that answers my question.
    The purpose of the osascript was to provide an OS X style, user friendly dialog that displays any martian files the bash script ignored. It was the least amount of coding for the result.
    I believe that your input example from above would take the exit status from the preceding shell script. How is my invalidFiles variable passed then? In the shell script, I can pipe the invalidFiles printf line to pbcopy to put that content on the clipboard. After the script is done, I can retrieve that information with a pbpaste command. I wonder if this information is available to your trailing AppleScript action for inclusion in the display alert statement?

  • Processing a File (From a Folder Action) Through an AppleScript

    I have a Folder Action enabled which automatically uploads images placed in a folder to a FTP server. It works great when I'm at home on my own network, but if I'm somewhere with a firewall that prohibits connecting to my FTP server (i.e. work) or if I am not connected to the internet, the folder action will still run but my images will never get uploaded.
    I've attached a screenshot of my workflow. The folder action gets the image added to the folder, copies the original to a different folder, and then scales the image down to a smaller size before uploading it. I'm using the upload workflow action from Transmit.
    I figured I could use an AppleScript to check whether or not my computer can reach the ftp server and then wait until it was connected to run the rest of the workflow if it can't reach the server:
    repeat with i from 1 to 86400
        try
            do shell script "ping -o ftp.examplewebsite.com"
            exit repeat
        on error
            delay 5
            if i = 86400 then error number -128
        end try
    end repeat
    The only problem is, I'm pretty inexperienced with AppleScript and am not really sure how or where to insert it into my workflow to get the image to "pass through" the AppleScript. Currently, whenever I include this AppleScript in my workflow, before the Upload action, for example, the image ends up not getting passed through the AppleScript and it doesn't get uploaded as a result.
    Hopefully this a fairly simple question and someone can help me out, or if there's an easier way to delay running a folder action until I can connect to the server someone will let me know. I can clarify anything if necessary.

    Good job
    I just saw this…
    applescript in automator - stop a workflow
    It kills the workflow based on a test, so I tried this…
    Here is the text if you want to copy & paste. It will fail on Apple.com & stop the workflow. Success should allow it to continue.
    on run {input, parameters}
      try
      set pinged to do shell script "ping -c 3 -q  apple.com "
      if pinged is equal to 0 then
      return input
      end if
      on error
      error number -128 -- exit by user-cancel
      end try
    end run
    on run {input, parameters}
       display dialog "Rest of script will now continue..."
      return input
    end run

  • Help Needed: Automator Applescript for Folder Action - Encode Video

    Hi !
    I have created an Automator Applescript for a Folder Action to do the following:
    When a new video file is moved to the target folder (i.e. Download of Vuze is done), automatically launch the Applescript Action that does the followin g(Applescripted):
    1) Using "run shell script" and FFMPEG on a UNIX command line, determine Width/Height, Framerate, Bitrate
    2) Calculate encoding parameters (slightly reduced bitrate, reduced Aspect etc.)
    3) Using "run shell script" with ffmpeg on the command line and the calculated parameters to encode the video file
    At the same time, the action is written to a log file so I know if a file is recognized, when encoding started etc.
    It works fine if I save this Action as an .app, make an alias on the Desktop and drop video files on it.
    It also works fine if I attach the script to a folder as a folder action and drag a video file in there.
    However, when I attach the script as a folder action to the Vuze download folder, it encodes only some video files, i.e. if there was a download of 5 files, chances are good that it will not encode 1 or 2 files out of those 5.
    If for example a second download finishes while the encoding for the first download is still going on, sometimes the second file starts encoding after the first encode finishes, sometimes it does not, the file does not make the log file at all, i.e. the folder action missed it or the automator action dropped it because it was still encoding. Still, sometimes it happens, sometimes not.
    As I need a solution that is 100% accurate, I would like to ask if there are any ideas on how to do this better maybe? As I am not an Applescript Guru, I would need some help to know what works and what doesn't and what the syntax is.
    My main idea right now:
    Similar to how ffmpegX works with its "process" application, have a second script (as .app) that receives the files to be encoded from the automator action and puts them in a queue, then proceeds to encode this queue while the main automator action is free to receive the next file.
    Writing this second app is quite straightforward (a modified version of my current script) but I have some questions I need help with:
    1) How do I call another applescript from within an existing applescript that launches the new applescript in a new process?
    2) How do I pass parameters to this new applescript?
    3) In case of this "Queueing" Idea, once I called the external applescript the first time, how do I make sure when I call next time, that I don't open a second instance of this script but rather pass another queue item to the original instance to be processed?
    Or in general: Is there a better way to achieve this automatic encoding solution that I have not thought about?
    Alternatively:
    Does anyone know how to call the "process" application that comes with the ffmpegX package with the correct parameters to use as a queueing / processing tool?
    Thanks!
    Joe
    Message was edited by: Joe15000
    Message was edited by: Joe15000

    To do this, I created an Automator workflow with an Applescript snippet to change the 'media kind'.
    Here is the 'Run Applescript' workflow step code:
    on run {input, parameters}
              tell application "iTunes"
                        set video kind of (item 1 of input) to movie
              end tell
              return input
    end run
    Prior to this running, I have an 'Import Files into iTunes' workflow step.
    You can switch out 'movie' with: 'TV show', 'music video', or anything in ITLibMediaItemMediaKind.
    Good luck,
    Glenn

  • Need a Folder Action Script to automate running of Applescripts in iTunes

    I posted this in the OSX forum but thought i'd try here too:
    I have a couple of applescripts that I have begun using on some of my podcasts. Specifically they will deselect "Skip When Shuffling" and "Remember Track Position" (Thanks Doug!). I feel like it is getting tedious to have to remember to run these scripts every time the Podcast updates a new episode. I'm looking for a folder action script that will run these applescripts whenever a new item is added to their folder. While I try to puzzle one together (having never written one) does anyone have anything to fit these needs?

    Yes.
    I recently need one to do something else.
    I'll just give you the script I am using, you can hack at will...
    property TargetPlaylist : "Library"
    on adding folder items to this_folder after receiving added_items
    repeat with each_item in added_items
    tell application "iTunes"
    add each_item to playlist TargetPlaylist
    end tell
    end repeat
    tell application "Finder"
    move every item of this_folder to the trash
    empty the trash
    end tell
    end adding folder items to
    This script when attached as a folder action will add the items dropped into it to my iTunes library, then delete them.
    You can easily tear this one apart to get what you need done.
    Beavis2084

  • Folder action to package and create pdf Applescript folder action

    Hi
    Does anyone have an Applescript Folder Action to package Indesign CS5.5 files and make pdfs.
    Thanks, in advance.

    Hi Babs
    I ended up paying someone to create the script. They did a fantastic job creating a droplet that has options to package, create PDFs to presets, print to presets, create an IDML file, retrosave this to CS4 and create a thumbnail. Sounds like a lot but that is what I ended up needing for one client and I can use it on anything.
    Thanks
    Mac
    Sent from my iPhone

  • Attach Folder Action Won't

    When I right-click on a folder and choose "Attach a Folder Action..." from the contextual menu that appears, nothing happens. The only way to pull this off is to go into Folder Actions Setup app and add a folder (via the "+" button) and a script.
    Any suggestions on what I may be missing?
    Quad G5 (4x2.5G), 7800GT, 4.5GBram, BT&Airport   Mac OS X (10.4.5)  

    Sorry if I wasn't clear enough. The problem I am experiencing is that, when I right-click on a folder and see the contextual menu that pops up, then choose either the "Configure Folder Actions..." item OR the "Attach a Folder Action..." item, nothing happens. The menu goes away, yes, but that's it. Am I not supposed to get a window allowing me to set the folder actions for the folder I right-clicked on?
    If I run the "Folder Actions Setup" application, I can choose the folder I want to add an action to by clicking on the "+" button and navigating to the target folder, choosing it, then choosing the action I want (in the Folder Actions Setup window).
    So, I CAN add an action to a folder and have it function properly. It's just that the contextual menu method ("Attach a Folder Action") seems to be broken.

  • Folder actions no longer functions in 10.6

    I have a folder action script that lauches Photoshop CS4 and saves an image in a series of sizes and formats. This worked well under Leopard but just does nothing under Snow Leopard.
    Folder actions is enabled and the script attached.

    Hi Arctic Ackbar,
    I too am having the same annoying issue after upgrading to 10.6 and it still continues to plague me even after the latest update to 10.6.1.7
    I don’t know if yours does the same but mine starts to download the maximum three items (if I have three or more but its the same even if downloading just two items) and it starts to download all three but then only downloads around say 100-200kB of the other two and waits for the first to finish, then moves onto one of the semi-downloaded items.
    It then repeats this for all the remaining items in the queue so in essence I might as well just un-tick the simultaneous download option as it seems to slow the one download and general bandwidth of my internet down.
    Lets hope it gets fixed in the next update, however I won't hold my breath

  • AppleScript: how to reinstall "Folder Actions Setup"

    MacBook Air with Yosemite 10.10.3
    Although I can successfully use Script Editor and get AppleScripts to run, the /Applications/AppleScript folder is missing:
    Erins-MacBook-Air:~ Peter$ ls -l /Applications/App*
    /Applications/App Store.app:
    total 0
    drwxr-xr-x  9 root  wheel  306 Apr 11 14:53 Contents
    /Applications/Application Loader.app:
    total 0
    drwxrwxr-x  11 root  admin  374 Sep 16  2014 Contents
    Erins-MacBook-Air:~ Peter$
    I need to run the "Folder Actions Setup" app which is normally in the AppleScript folder.  I have reason to believe it was deleted in an attempt to recover disk space.
    In the app store, I tried to "upgrade" to Yosemite, and I got a message that since I already have Yosemite, I could simply use the "update" feature, but the entire upgrade installer is available if I really wanted to download it. I did that, and I ran through the entire process, which did some things, including changing my desktop image back to the default.  However, I still aint got no AppleScript folder.
    What next?

    Thanks.
    It would be nice if this weren't obsolete:
    https://developer.apple.com/library/mac/documentation/AppleScript/Conceptual/App leScriptLangGuide/reference/ASLR_folder_…
    I'm still learning my way around Folder Actions, but it seems that the GUI "setup" item is pretty minimal.
    If I successfully write a handler script for "on adding items to a folder...", and put it in the right place, apparently I can get everything working by ctrl-clicking the target folder in the Finder, and using the Services context menu to associate the target folder with the script I'm writing.
    This will be a bit obtuse for some people.  Perhaps Hazel fills this need better. 
    But thanks for the info!

  • Applescript to change file type using folder action

    Just found out my Adobe Acrobat is saving PDFs with the filetype "FDP" and creator "ORAC" which is obviously the reverse of what they should be.
    There doesn't appear to be a fix for this, and for me it's a problem because when I copy these PDFs onto our Xinet WebNative asset management server the files aren't recognised as PDFs, so don't display a preview in the web page.
    So, I wanted to use a folder action that will set the Creator and Type to the PDFs whenever they are put into a folder on the server.
    Unfurtunately, although I can get this to work when using a script in the form of an application (so I drop PDFs onto it, I cannot get it to work as a folder action. It doesn't set the creator and type even though the same commands in a application script do work.
    *This is the code to my script which works fine as an application:*
    ====================
    property FileType : ""
    property CreatorType : ""
    on open theFiles
    tell application "Finder"
    activate
    set FileType to "PDF "
    set CreatorType to "CARO"
    repeat with eachFile in theFiles
    set the file type of eachFile to FileType
    set the creator type of eachFile to CreatorType
    end repeat
    end tell
    end open
    ===================
    *and this is what I'm trying to use for a folder action:*
    ===================
    on adding folder items to my_folder after receiving the_files
    set pdfs to {"pdf"}
    repeat with i from 1 to number of items in the_files
    tell application "Finder"
    set this_file to (item i of the_files)
    set the file_path to the quoted form of the POSIX path of this_file
    --set the file_path2 to the quoted form of file_path --can combine if file_path isn't needed
    set this_fileType to name extension of (info for this_file)
    end tell
    if this_fileType is in pdfs then
    tell application "Finder"
    activate
    set FileType to "PDF "
    set CreatorType to "CARO"
    end tell
    end if
    end repeat
    end adding folder items to
    ==================
    I know it processes the file but it doesn't actually change the creator type.
    *If only Apple would fix this bug in the first place!*

    Your folder action script isn't using the same commands, and doesn't do anything about setting file types or creator codes at all. Something like this should do the trick:
    <pre style="
    font-family: Monaco, 'Courier New', Courier, monospace;
    font-size: 10px;
    font-weight: normal;
    margin: 0px;
    padding: 5px;
    border: 1px solid #000000;
    width: 720px;
    color: #000000;
    background-color: #FFEE80;
    overflow: auto;"
    title="this text can be pasted into the Script Editor">
    on adding folder items to my_folder after receiving the_files
    set pdfs to {"pdf"}
    repeat with each_file in the_files
    set this_fileType to name extension of (info for each_file)
    if this_fileType is in pdfs then
    tell application "Finder"
    set file type of each_file to "PDF "
    set creator type of each_file to "CARO"
    end tell
    end if
    end repeat
    end adding folder items to
    </pre>
    ... and by the way, Apple doesn't have anything to do with the file types, creator codes, or other application specific settings that an Adobe application sets for itself.

  • Automator folder action won't run entire folder contents

    Hi,
    Ok, I think I'm pretty well versed in Automator and getting things to work. But this is just escaping me.
    I've made a simple Photoshop Droplet (done this before). Open Automator, built a workflow for getting a folders contents and then opening the contents with the Droplet.
    Saved this as a folder action,...
    But when I drag multiple items to the folder, it only runs the very first item and stops,...
    If I drag one by one into the folder it will work fine,....
    I'm going to have to be dragging multiples all the time, it's a waste of time to do one by one,...
    I'm totally missing something here,.... please help!!
    I'd also like to move the contents of the folder, once the Droplet has run, to the trash
    But first I have to get this darn thing to run on the entire folders contents,.....
    Workflows I've tried:
    1 - Open finder Items (open in my Droplet) works one at a time
    2 - Get Specified Finder Items (point to my folder)
    Get Folder Contents
    Open finder Items (open in my Droplet) again, works one at a time
    Thanks!!
    Christopher

    Hi Curly, and a warm welcome to the forums!
    I don't know much about Automator, and this may be of no help, but...
    It's either just picking up/passing one variable, when it either needs an array of variables, or needs to loop back for the next one.

  • Applescript - Folder Actions Setup

    trying to make a folder action to move anything dropped in a folder to shared folder on another device.  code as follows:
    set destFolder to (":" & (path to desktop as string) & "Workflows:Sheetfed:")
    display dialog destFolder
    on adding folder items to this_folder after receiving added_items
              try
                        tell application "Finder"
      move added_items to destFolder
                        end tell
              end try
    end adding folder items to
    Nothing happens.
    Note:  I added the display to see the path when I was hand running.
    Do I need to use posix path for this, or maybe use command line??  Not sure what's best - easiest - most reliable
    Any assistance is greatly appreciated.

    Thank you.
    I have this:
    set destFolder to (":dx1070:Workflows:Sheetfed:")
    on adding folder items to this_folder after receiving added_items
              try
                        tell application "Finder"
      move added_items to folder destFolder
                        end tell
              end try
    end adding folder items to
    But still not doing it yet.
    Took off the leading colon on destFolder ie ":dx1070:Workflows:Sheetfed:", still no.
    Any more help would be great!

  • Folder Actions script no longer runs on new file creation

    Hope this isn't trivial.......first time posting here...hopefully in the right place.I'm not a total Mac OS X newbie...and surely no techie, either. Dabbled a wee bit with Automator and scratchin' my head on this one. Help, please!
    Any idea why folder actions not running when a new file is saved? A simple add-color-label script created in Automator was workin' fine before I did a Snow Leopard-to-Leopard downgrade clean-install & account migration from external HD (TimeMachine) backup. Folder actions are enabled and script runs only if I start it with Automator Runner. Previously, it would label the file as soon as I saved it....now it needs a manual start. Is this default behavior in Leopard? Or am I missing something or doin' something wrong? Or is this a consequence of downgrade? I was sure I had the same script workin ok in my original Leopard install - though possibly un-modified at that time.
    I have no clue why, but the new version I created recently (cpl wks ago?)worked the first time I added a new file but not thereafter...and in that instance it only labelled the file in Finder upon quitting Preview (file is a Grab saved as pdf).
    The reason for the downgrade was compatibility problems with Photoshop CS4 on SL (OS & app all updated yet crashin' at the drop of a hat) - maybe due to lack of RAM? (only 1GB). Saw quite a few posts regarding SL running CS4 problems, so now I'm back to running 10.5.8 ..again.. and PS actually runs smooth like it did before.
    Maybe these console messages are a help......or am I barkin' up the wrong tree?
    6/11/11 7:44:54 PM /System/Library/CoreServices/Folder Actions Dispatcher.app/Contents/MacOS/Folder Actions Dispatcher[91] CPSGetProcessInfo(): This call is deprecated and should not be called anymore.
    6/11/11 7:44:54 PM /System/Library/CoreServices/Folder Actions Dispatcher.app/Contents/MacOS/Folder Actions Dispatcher[91] CPSPBGetProcessInfo(): This call is deprecated and should not be called anymore.
    6/11/11 7:44:54 PM /System/Library/CoreServices/AppleScript Runner.app/Contents/MacOS/AppleScript Runner[264] CPSGetFrontProcess(): This call is deprecated and should not be called anymore. 
    6/11/11 8:19:12 PM Automator Runner[415] Error while processing arguments
    6/11/11 8:20:31 PM /Applications/AppleScript/Folder Actions Setup.app/Contents/MacOS/Folder Actions Setup[420] CPSGetProcessInfo(): This call is deprecated and should not be called anymore.
    6/11/11 8:20:31 PM /Applications/AppleScript/Folder Actions Setup.app/Contents/MacOS/Folder Actions Setup[420] CPSPBGetProcessInfo(): This call is deprecated and should not be called anymore.
    6/11/11 8:20:32 PM [0x0-0x5b05b].com.apple.systemevents[421] com.apple.FolderActions.enabled: Already loaded
    And for that matter....why does Automator throw these messages? All apps (except iWork '08 apps) and OS are up to date.
        - Just a few of the many actions not loaded:
    6/11/11 7:48:25 PM Automator[294] The action “Start iTunes Visuals” could not be loaded because the application “iTunes” is the wrong version.
    6/11/11 7:48:25 PM Automator[294] The action “Stop iTunes Visuals” could not be loaded because the application “iTunes” is the wrong version.
    6/11/11 7:48:25 PM Automator[294] The action “Update iPod” could not be loaded because the application “iTunes” is the wrong version.
    6/11/11 7:56:33 PM Automator[294] name = name was not found
    6/11/11 7:56:33 PM Automator[294] name = name extension was not found
    6/11/11 7:56:33 PM Automator[294] name = file type was not found
    6/11/11 8:00:29 PM Automator Runner[339] Error while processing arguments
    6/11/11 8:00:30 PM Automator Runner[339] The action “Import Files into iTunes” could not be loaded because the application “iTunes” is the wrong version.
    6/11/11 8:00:30 PM Automator Runner[339] The action “Add Songs to iPod” could not be loaded because the application “iTunes” is the wrong version.
    6/11/11 8:00:30 PM Automator Runner[339] The action “Add Songs to Playlist” could not be loaded because the application “iTunes” is the wrong version.
    6/11/11 8:00:30 PM Automator Runner[339] The action “Apply SQL” could not be loaded because the application “Xcode” was not found.
    Do I need to wipe the drive again and re-install everything?
    Any help is greatly appreciated. Apologies if this seems long-winded.

    Folder Actions are set up a bit differently in Leopard (they use an AppleScript wrapper), and several actions have been updated to use new technologies available in Snow Leopard.  Looking at some of your console logs, it looks like some actions or workflows were just copied over from Snow Leopard.  When changing versions like that, you should rebuild the workflows so that they link to the correct actions, and check added actions for any dependencies (an action won't be loaded if it requires resources that are not available).
    Resaving your Folder Action workflow as a Folder Action Plug-in should do the trick.

Maybe you are looking for