Today I had a chance to help a print publication solve a workflow challenge that is apparently very common.
If you open an Adobe InDesign layout file from a local folder on your computer, the software creates an Adobe InDesign Lock File (.idlk) in that folder, which prevents the same file from being opened by another copy of InDesign. But if the file exists in a folder that is shared via network or cloud service, InDesign does not create a lock file when the InDesign file is opened for editing. This includes Adobe’s own “Creative Cloud” file sharing option.
There may be good technical reasons for not creating or syncing lock files across network folders, but the end result is that multiple users can decide to open the same file at the same time, and whomever saves their changes last will “win,” with the other user’s changes being lost.
In researching this, I found it was not some edge case. There seem to be many newsrooms and other organizations struggling with this every day. They work around it by doing things like copying the InDesign files to a local folder, making their changes, and then uploading back to the shared folder, hoping that the internal communication about such things is sufficient along the way. This Adobe Community Support forum thread illustrates the pain points involved.
Thankfully, Adobe InDesign is a scriptable software tool, and so
Max Schmidt and the folks at t3n created a script that creates a locking system for network shared InDesign files. And there was much rejoicing!
After installing the script on all the devices that will be accessing shared InDesign files, anyone trying to open a file that someone is already editing gets an error message and then the file is closed. (I submitted a Pull Request to expand the README documentation so the installation process is a bit clearer.)
In the long run, Adobe needs to solve this problem in a more standard way for its users. But this script is a great alternative option and I hope bringing some additional attention to it helps out other publications or news rooms that might be struggling with the same challenge.
Updated April 26, 2023: the current version of the script we are using is here:
We found that we had to place this version in the Startup Scripts directory for it to keep working.
We’re working with INDD files stored on a server, we don’t have that problem, we still have locked files. We’re on windws 10, INDD 18.2 and 18.3 (recently installed – may 2023)
Very interesting, thank you.
I work with companies struggling with this on Google drive. This is even worth than on samba share since local caches are synchronized asynchronously. I wonder if someone has already forked the script to use an api to propagate the locks .
Dumb question: Does this script work on both Mac and Windows? We are having trouble with this using Synology, but I found a solution.
We use it on both Windows and Mac machines. Feel free to drop me a note about any specific issues you’re having and I’ll try to help.
Thank you very much for sharing the script. I’m trying to make it work in a project stored on OneDrive, but it’s impossible for me. However, when I work on the local hard drive, it works perfectly. Do you have any idea how I could try to make it work?