Jörgen Stahle
My feedback
4 results found
-
74 votes
The fix of the issue is now available in the latest InDesign 2022(v17.0.0.96). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.
—
Adobe InDesign TeamAn error occurred while saving the comment An error occurred while saving the comment Jörgen Stahle
commented
This problem still persist with Indesign 16.1.0.20 (Mac) – five moths after it was reported by xxFEXxx!!
To describe what happens for us with documents on shared file volumes (both smb and afp):
• User 1 opens an indd document. A lock file is created.
• User 2 opens the same document. The lock file disappears, and the document opens for user 2. However, the document is write protected.Jörgen Stahle
supported this idea
·
-
3 votes
An error occurred while saving the comment Jörgen Stahle
commented
*** PROBLEM SOLVED *** due to great help here: https://community.adobe.com/t5/indesign/serious-indesign-server-slow-down-with-catalina/m-p/11599775.
At least it is solved for us and can propably be permanently solved by Adobe
1. There is a simple workaround: Making InDesign Server the front application brings back good performance.
2. This workaround should be a pretty good lead for Adobe developers on what to to to permanently solve the problem.An error occurred while saving the comment Jörgen Stahle
commented
There is one very puzzling thing, that we have observed after I wrote this post :
At some, very rare occasions the script suddenly runs as quick as it used to do before the upgrade – just above 1 minute.
This have happened two times – out of around one hundred tries with the same script. In both cases it was executed by a soap call (with otherwise has become the slowest method with Catalina).
Then, running the same script several times directly after such an occasion, gave us same disappointing results as usual: around 3:30 and sometimes more, from soap.
This tells me there is a potential to run InDesign Server scripts as fast with Catalina as with Mojave – but, in most cases, the script is heavily disturbed by something...Jörgen Stahle
shared this idea
·
-
1 vote
An error occurred while saving the comment Jörgen Stahle
commented
However... Indesign scripts became very slow with the upgrade to Catalina.
The time for processing documents is 3-5 times longer - with huge variation between different executions of the same script.An error occurred while saving the comment Jörgen Stahle
commented
PROBLEM SOLVED!
We added `bash` to the Full Disk Access list in the systems integrity panel – problems gone!
I did add `launchd` and `sh` there before – but not bash.
Maybe Adobe and Apple could do more here to guide the people setting up Indesign servers.Jörgen Stahle
shared this idea
·
-
4 votes
An error occurred while saving the comment Jörgen Stahle
commented
However – strangely enough – a 'file' reference also works when defined by the script outside the InDesign tell block. So this also works:
set imageFile to POSIX file "/path/to/IMG_2592.jpeg"
--> file "Macintosh HD:path:to:IMG_2592.jpeg"set textFile to POSIX file "/path/to/test.txt"
--> file "Macintosh HD:path:to:test.txt"tell application id "com.adobe.indesign"
tell rectangle 1 of document 1
place imageFile
end tell
tell text frame 1 of document 1
place textFile
end tell
end tellAn error occurred while saving the comment Jörgen Stahle
commented
The different ways to refer to a file seems to be fever with InDesign on Catalina . Using 'file' directly in the Indesign tell block does nor work for example. But using 'alias' with a HFS-path still works:
tell application id "com.adobe.indesign"
tell rectangle 1 of document 1
place alias "path:to:image.jpeg"
end tell
tell text frame 1 of document 1
place alias "path:to:text.txt"
end tell
end tellAn error occurred while saving the comment Jörgen Stahle
commented
Confirming the problem. I haven't found any workaround.
Not fixed yet???