Indesign 2021 (16.0) IDLK file do not lock
It is currently possible that two users are able to open the same Indesign file. I am working on a network volume via VPN and it was possible for my colleague to open the same file i was working with. The *.idlk file was generated but it seems that it would not be recognized from the other Indesign my colleague was using.
I tried to reproduce this issuue with Indesign 2020 and all worked fine as expected.
This is an enormous issue for collaboration with other colleagues at the same projects.
The fix of the issue is now available in the latest InDesign 2022(v220.127.116.11). 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 Team
same here: working on latest version of DSM synology NAS, worked fine till udpate....
No news are bad news.
This issue is really problematic for who work on a network team.
ADOBE PLEASE FIX IT
Aaron Phillips commented
Our team STILL has to use InDesign 2020 because of this issue. Is there any ETA on it getting resolved yet?
Richard Jansman commented
Our employees are working from home via VPN. When they open indd files on our Acronis file server it opens the indd file two times and one ldlk file is opened. Many times problems to save the file. After closing Indesign the can save the file on the network share.
Reto B commented
Important! Please fix this asap. Locking files is essential!!!!
Good morning Adobe programmers, please wake up.
This problem is annoying. In the former version the lock file worked.
I thought, CS2021 is an upgrade, not a downgrade.
Edy M. commented
Not fixed after 8 month?
Looking for a LockFile needs that long?
Oh, by the way: what do Adobe programmers professionally?
New England Indesign User commented
When will this be fixed? it is very dangerous for a file to not be locked upon opening when working on a network share.
When working and opening multiple files a day, editing, etc, only to find out the file is "read-only" because someone else had it open on the server. Yes, I know we can look and see if the file is opened to try to avoid this situation, but this is very bad to try to retain the integrity of files. Please fix this bug, and make an update available.
Lars Aa commented
Any updates on this issue?
I am slightly concerned that no further update has been released to fix this issue considering Adobe is a massive organisation covering many industries the fact that such a serious issue has not yet been resolved.
Jörgen Stahle commented
Not fixed yet???
This is a huge problem! Needs to be resolved As Soon As Possible. We are exploring alternatives to move away from Adobe since this is taking so long to resolve. High annual subscription costs should have resolved these major issues by now!
6 months later and this is still an issue.
Can anyone at Adobe explain why we are paying an annual subscription for software that has bugs that are not addressed?
I want to add that we have also had the problem of multiple users in the same file. Not everyone notices right away that they are in read only mode, and then of course there is the issue with multiple versions and how do we make sure that all the changes have been done correctly. This has a serious impact on proofing and quality control goes from simple to very complex. We use a local server. Please fix this.
This needs to be fixed ASAP, Adobe, PLEASE!
OG post is from November 2020. Now it's May 2021. Still not fixed, it seems
We just upgraded and are facing the same problem - a "read-only" (schreibgeschützt) will not keep multiple Users from opening a File - older Files from a previous Version of ID also do not display a "idlk" when open - only after saving from ID16.1 and reopening them will show these Files. Please fix this - in an fast paced Work environment and including Home Office - this is turning into a Nightmare of preventable errors.
it is absolutely unacceptable that since October 2020 nothing happened! For every team working with ID this is a serious issue!
This is still an issue. Adobe, help!
Any updates on this issue?