InDesign 16.0 Ignores Lock File on Network Share
InDesign 16.0 on MacOS 10.15.7, several different machines, all experience this issue where InDesign has changed its behavior regarding locked files. Our machines are networked and share a drive across a gigabit intraoffice connection to collaborate on work. It's important for our workflow that work is done sequentially, with one person handing off a project to another. There is no non-sequential work.
On previous versions of ID, when trying to open a .indd file while a corresponding .idlk file is present, InDesign would give an error. This was the expected behavior, as it prevented two people working on the same file at the same time without knowing it. This prevented any possibility of lost or duplicated work.
In rare circumstances, it was possible for two users to open a file at the same time, before the .idlk file could be created and uploaded to each machine. In these instances, the slower user would be served a Read-Only version of the file by the server, and if they didn't notice, they'd have to save as another file to avoid losing their work. This was also the expected behavior and was rare enough to not matter.
Since InDesign 16, the first behavior no longer exists at all. .idlk files appear to have no purpose. Two users can open the same file, whether a corresponding .idlk file exists or not, and one will end up in Read-Only mode, every time, no errors.
I have verified that .idlk files are being created when files are opened, and are visible across all machines, but it doesn't prevent other users from opening that same file. Nothing has changed in our network configuration, the only change since this began was the upgrade to v16.
Thanks for reporting. We will review it
OG post is from November 2020. Now it's May 2021. Still not fixed, it seems
Need a fix to this issue. Team of 4 working with ads on a shared server, often opening other peoples work to copy products to our own publications. We need the security of at least a notification, if not just removing the possibility to open already open documents. The «Read Only» is not enough, as you actually can make edits to it.
iOS 10.15.7 (Catalina)
Gav Bainbridge commented
Same problem, also affecting macOS 10.14.6 and InDesign 16.1. We use Book files so that multiple users can see which files are open in the Book. This doesn't work anymore, InDesign Book doesn't recognise the files as open even with the lock files there. Has been working fine all the way back to CS3, come on Adobe, stop breaking stuff.
Yes we are working in a cloud environment and are having the same issue. Lock file appears not be working at all. My co-worker can open, save and overwrite the same file I have open. Hope this gets resolved soon!
Maria Gee commented
Same issue in our shop. Hoping for an update to correct this soon.
Is there any news on this because the latest up-date hasn't fixed this issue? Indesign 16.1
Come on indesign team - the new update hasn't fixed this issue!
Having a warning dialog appear to inform a user that the document is already open by another user is a very important part of any workflow where multiple users access the same file. The "read only" status of such a file is subtle and easily missed. Please Adobe add a warning dialog for this situation!
Wir haben das gleiche Problem mit insgesamt acht Rechnern, verbunden über einen Server. Hoffen wir also das Beste.
Gareth Simcock commented
We are having the same problems. All previous iterations of InDesign allowed users to experience a warning that a document was currently open. The latest version of Indd allows multiple users to open the same document over the network without such a warning. The initial user is the only one who can save the document, all others have a 'read only' message in the filename - not massively obvious when in a busy and deadline heavy workplace.
Maria Gee commented
Our team is having the same issue. Hoping someone can shed some light on this and help us resolve.
Same problem here. Small team working off a server and InDesign is automatically generating read-only copies rather than an error message saying the file is locked.
This is driving me crazy! I hav a publication team of 20 people who are working on files at the same time. I need them to not open if someone else has the IDD file open. UGH