Copy link to clipboard
Copied
When I try to run Image Processor from within Photoshop or from Bridge, I get the message "JavaScript code was missing". I get the same or similar with other script functions (see screenshots) and when browsing to other scripts I have manually placed in the Presets>Scripts folder.
This is a brand new Mac. I have tried uninstalling and reinstalling Photoshop from Creative Cloud with and without removing preferences, as well as both v 26.0 and v 26.10. I have since installed v 25.12.4 and the scripts all run without problem. It seems like v 26 is unable to access the Applications folder or something? I have checked the scripts are present where they should be, and can be run if placed in another location.
The only related article I found was talking about a similar issue when launching Photoshop with Rosetta, which I am not doing.
System:
Photoshop v 26.0 and v 26.10
Macbook Pro M2 Max, OS 15.7
Copy link to clipboard
Copied
Hey @Matthew5E2A,
I'm moving your post to the discussion where we can get more eyes on your post, specifically because this is regarding scripting. In the meantime, can you share your system info for Photoshop? You can find this by going to Help > System Info, then copying and pasting it into a text file to attach here. When you say "can be run if placed in another location." What location are you moving it too?
^CM
Copy link to clipboard
Copied
Hi thanks for your response. System Info attached.
I find scripts such as Image Processor or Contact Sheet II can be copied to, for instance, my user folder and run via File>Scripts>Browse...
Also, using this method I can run the same scripts at their default location in the Photoshop 2024 (v 25) folder, from within Photoshop 2025 (v 26).
It seems a very strange problem. I can get round it to some extent by creating actions running these scripts at alternative locations, but I am still unable to run them from Bridge Tools>Photoshop, which is something I need to do a lot.
Copy link to clipboard
Copied
@CMass I know you said you moved it to get more eyes on it but surely this is a bug, not a discussion?
Find more inspiration, events, and resources on the new Adobe Community
Explore Now