Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Shared links should retain link when file is modified.
Older versions of Dropbox maintained the link to the shared file even if it was updated as long as the file path was not changed and the file name remained the same.
This new version requires you to share a new link each time a file is modified.
It becomes a hindrance when collaborating and lengthens the cycle when a simple refresh would suffice.
7 Replies
Replies have been turned off for this discussion
- Hannah
Dropbox Community Moderator
Hey TrevorBarrett, thanks for reaching out to us!
Would you mind giving us some specific examples of the behavior you're seeing?
What do you see, when you click on a link after you've edited the file?Does it give you any errors?
Let me know.
- A link to preview a PDF FILE, is sent in text to client/collaborator who reviews and makes comments. These comments are implemented and the PDF is exported again replacing the previous.
If the client or myself click on the previous link an error message appears "This link does not exist". - Mark
Super User II
It shouldnt work like that - on mine it always updates and just replaces the file as long as the initial file is not deleted first.
How are you replacing it? What is things like the OS / set up (so desktop or web etc.)
TrevorBarrett wrote:... These comments are implemented and the PDF is exported again replacing the previous.
...
Mark wrote:...
It shouldnt work like that - on mine it always updates and just replaces the file as long as the initial file is not deleted first.
...
No, no, no... Dropbox always invalidates link when pointed file is REPLACED!!! The word "replace" is a keyword here. The invalidation can delay depending how long the old (replaced) file stays in trash. On invalidation delay, the link remains valid and point the old file (already deleted file) content. Dropbox shared link points file content, not file path!!! So even when you put new file on a path where was a file pointed by a link, it's still a new file - different file - and the link doesn't point it. Make difference between "update" and "replace"! In spite in common talking they are used as synonyms, the meaning (the precise meaning) is completely different. When you update some file, it stays the same file and that's why the link stays valid too; otherwise no. 😉
Unfortunately lot of programs, when save particular file, the existing file content is NOT updated and if there is existing file it's deleted (might be renamed before that) and a new file with the same name is created (keywords - new file - new link will be needed). Almost always the users are not informed about that. Including Dropbox itself doesn't inform users that when particular file is synced from cloud to local machine, the existing file locally is wiped out, NOT UPDATED; this has been confusing for lot of users (there are many threads on the forum). Big weakness in Dropbox application documentation, but it's not something new and as mentioned not only Dropbox application related. In particular case the replacement is done by corresponding editing application.
Hope this clarifies matter.
- Mark, I agree with you. I've used Dropbox for years and it always worked on file revisions as long as the file name remains the same. In fact as recently as June 6, I made revisions and the links still work. Something was changed so that it no longer works.
- Здравко
Thanks for your response but I disagree with you. Dropbox has been out collaboration tool since it's inception. Our typical workflow is is to export a PDF from InDesign and save it to a location in Dropbox, any revisions simply overwrite the existing file.
I currently have text links originally sent on April 4 and then revised (replaced) on April 13 and they both work pointing to the existing and current version.
Something has changed that is not allowing this to happen; which means links have to be resent for every edit, where in the past clicking the link would show you the updated version. - Mark
I've just tested here again and as I said a simple replace of the file works. As it always has - even if I replace from another location.
TrevorBarrett could you try saving your file to say the desktop first and then overwriting the old one?
