Photoshop startup scripts location controlled by the environment variable

photoshop

#1

Hi - is it possible to point Photoshop a specific startup scripts location through some environment variables?


#2

As far as my experience shows, no. Photoshop 100% expects scripts to exist within specific folders contained within the application installation folder. This is a pain to deal with on Windows machines that have UAC enabled as it is not allowed for process to blindly write to c:\program files (and other locations) when UAC is on. The correct behavior is for the application to look for items such as scripts and plugins in folders under %appdata% or %localappdata%. It’s amazing that Autodesk gets this right and Adobe couldn’t care less.

What you can do is create a symbolic link in <photoshop folder>\plugins\scripts that is linked to a folder located elsewhere. Photoshop has no problem parsing the symlink and pulling the scripts in that way. That’s what I used to get around the problem. While the installer tool for Volition’s scripts still needs to have Admin privs to create the symlink, after it is done everything works fine from a user account with UAC enabled.


#3

Autodesk sometimes gets this right.
Maya 2017 went ahead and installed some plugins directly to my C drive, like we’re back in the win3.11 days.

But yeah adobe is much worse. Hadn’t thought of doing the symlink though, need to try that.


#4

Roundabout way of doing it, but when running a .jsx through photoshop, the script has the same access permissions as the program so you should be able to create a symlink within the scripts directory using an install.jsx file or some such:

I’ve done something going the other way piggybacking photoshop permissions to have an install.jsx that copies scripts into the photoshop folders. Works with CEP extensions, too.


#5

symlinks are the way i’ve done this, too.