Automator and Aperture in Leopard

I also have this bug on my Intel mini, but not on my G4 PowerBook. I've reported it, but no response.

The automator actions are missing in Leopard for some reason, leading to the Null value problem. The actions are all located in the Automator installer. If you open the package, you can find the actions and copy them all to /Library/Automator. Most things then work, although I still have a problem with 'Choose Album' and with the naming profiles.

Thanks, but where is the "Automator installer"? I don't see that on my Leopard DVD.

What has happened is that the Aperture Automator actions have been removed from /System/Library/Automator on installing Leopard (probably with Archive and Install).

I've been having this same issue and couldn't for the life of me figure out what was wrong.
The hint provided by the previous poster put me on the right track.

The Aperture Automator actions are located in the the Aperture application.

Steps to take for repairing the situation:

1. Open a Finder window and navigate to /System/Library/Automator
2. Open a second Finder window and navigate to /Applications/Aperture
3. Execute a Show package Contents of Aperture (you should get a third Finder window).
4. Now navigate to Contents/Library/Automator
5. Select everything (.definition and .action) in that folder
6. Copy with option drag to the folder in the window created in step 1.
You will be asked for the administrator password.
7. Close superfluous windows.
8. Start Automator and enjoy.

In short: copy the contents of /Applications/Aperture.app/Contents/Library/Automator to
/System/Library/Automator

I've done this and no longer get the NS Null error messages. I can now access the actions and will see if they actually work some time in the next few days.

Cause: Apple Leopard Installer.
Remedy: Apple should have warned beforehand that something like this would happen and should have provided the solution.

happy automating

Berend

thank you!

Thanks for that relatively easy and painless fix to this problem that has been going on for months. Apple's silence on this one has been very frustrating. Makes me think their feedback form is tied straight to a spam filter.

Thank you very much! This worked for me. I have a multistep import action that adds boilerplate text in various metadata fields, names the files sequentially, moves them to a different hard drive, and imports them by reference. It's now working perfectly! Thank you!