Participating Frequently

Answered

Scripts Not Functioning After Update to InDesign CC 2025

Forum|Forum|1 year ago
October 14, 2024
4 replies
12384 views

I have a load of scripts used to produce different PDF's. These will not work in the New InDsesign 2025.

Attched screenshot of error message.

This is one of the codes which I have used for over 10 years until the new version.

tell application id "com.adobe.indesign"

set _NoCrops to PDF export preset "No Crops"

set _Crops to PDF export preset "Crop NO Text"

set _dest to path to desktop as string

tell active document

set _Name to name

if _Name ends with ".indd" then

set _Name to text 1 thru -6 of _Name

end if

set noCropPath to _dest & _Name & " PROOF" & ".pdf"

set cropPath to _dest & _Name & " PRINT" & ".pdf"

export format PDF type to noCropPath using _NoCrops without showing options

export format PDF type to cropPath using _Crops without showing options

end tell

tell application "Finder"

set label index of file noCropPath to 7

set label index of file cropPath to 2

end tell

<Title renamed by MOD>

Scripting

Correct answer leo.r

I think i might be in way over my head here as I have no idea what to do with that i'm sorry.

I think i might be in way over my head here as I have no idea what to do with that i'm sorry.

By @Luke25170286g4xv

In your particular script, all you need to do is change

export format PDF type to mgFilePath using "HR PDF" without showing options

to

export format PDF type to (POSIX path of mgFilePath) using "HR PDF" without showing options

L

Luke25170286g4xv

Participating Frequently

Hi all, apologies for tagging along with this post but i'm also having a similar problem since updating to Indesign 2025 (v20). We run a script which outputs indiviual pdf pages from a multi page document, named using a specific filename on a seperate layer into a HR Folder in the same folder location as the active indesign doc. This has worked for years prior, and still does with Indesign 2024 so just wondering what the fix could be here? Currently holding back on full update to 2025 but with a lot of other colleagues starting to update it's becomming a bit of a problem.

I run the script and it still runs as it should without any error messages however, in the HR PDF folder that it creates it is always empty with no PDF exported? Any help would be massively appreciated. Script we're using is attached below for ref - thank you!

Robert at ID-Tasker

Brainiac

@Luke25170286g4xv

HFS / POSIX part:

https://helpx.adobe.com/uk/indesign/kb/user-dictionaries-missing-hfs-path-dropped.html

L

Luke25170286g4xv

Participating Frequently

Thanks @Robert at ID-Tasker , explains it clearly for a novice like myself to understand! So knowing that, is there a way to adjust/tweak the current script for it to work in POSIX path Style at all?

LawtonKARAuthor

Participating Frequently

The probelm is that InDesign isn't producing the PDF's.
I have removed the last part of the code, this elimates the error code, because it can't find the PDF's on the desktop.

Looking at other comments about paths need changing, this line may be the problem
'set _dest to path to desktop as string'.

Can anyone advise how the path should be up dated to work in v20.0.

leo.r

Community Expert

Looking at other comments about paths need changing, this line may be the problem
'set _dest to path to desktop as string'.

Can anyone advise how the path should be up dated to work in v20.0.

By @LawtonKAR

for a quick solution, just use POSIX path of cropPath

i can't go further into depth about posix paths right now, but you can look up something like 'posix paths in AppleScript'

C

CarlForde

New Participant

I have a similar problem, but POSIX path didn't fix it for me.

The problem arises when InDesign is invoked from PHP running under Apache. When all the files are owned by A and Apache is running as user A all works as expected.

I'd rather not run Apache as a user with admin rights. Any ideas?

By @CarlForde

Frankly, I don't know much (well, anything) about running AppleScript from PHP under Apache. You didn't mention if the problem started after updating to InDesign 2025, or a macOS update, or something else. But if running as a user with admin rights solves the problem, then maybe it's the best solution.

Apple also keeps introducing all kinds of security changes which may affect your scenario, too. In any case, you may have better luck asking this question on stackoverflow.

We are replacing a Mac mini running Ventura 13.2.1 and InDesign 2023 18.2.1 with a new Mac mini running Sequoia 15.2 and InDesign 2025 20.1. Having Apache running as an admin user is bad practice from a security point of view. So I'd rather not do that.

Robert at ID-Tasker

Brainiac

You've the same problem as described in this thread:

https://community.adobe.com/t5/indesign-discussions/data-merge-issues-when-upgrading-to-indesign-19-4/m-p/14574309#M571330

M

mstavri

Participating Frequently

I have same issue in a way: a script that works perfectly with Indesign 2024 it crashed completely with Indesign 2025. I changed the paths to POSIX but with no luck.

the script takes a list of indd files from a specific folder then

1. creates a package

2. export an idml file

3. export a preview rgb pdf

4. converts some color to a specific cmyk value

5. export print pdf

6. reactivate a layer

In Indesign 2025, after updating paths to POSIX:

1. creates a package corectly

2. fails to export an idml file. even the path is correct but does not save the file, and there is no error message

3. fails to export a preview rgb pdf:

error "Adobe InDesign 2025 got an error: Failed to Export the PDF file." number 9485

If it helps I can share the script

Thanks

Robert at ID-Tasker

Brainiac

@mstavri

Which Mac OS version?

leo.r

Community Expert

You must use POSIX paths starting with InDesign 2025 (as opposite to legacy comma-separated HFS paths).

leo.r

Community Expert

p.s. would be nice if Adobe communicated this change more obviously to the regular users.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded