Hello everyone,
I am usually working files directly on Synology server using samba. I do this because I want to have the snapshot functionality Synology offers.
From my experience working with RW on Synology using samba, it does not work well. Automated backup files when publishing are not written and occasionally, before saving, I got the error titled
This document’s file has been changed by another application since you opened or saved it.
Is this expected ? Is there a workaround
Sorry, I don’t know what Synology is but I get that msg all the time. In my case it’s coming from RapidWeaver itself. If I publish and then do a save I find that RW is already doing an “auto” save due to the publishing. When this happens I get that msg above. So any time RW is saving and you save too you’ll see that. I’ve learned to wait a about 10 seconds after publishing to save (I don’t trust that RW does in fact save and there is no msg). Since then I’ve not received the msg. That’s my experience here anyway. Your’s may vary… Hope that helps.
Hello @1611mac
Thank your for participating in this topic.
Synology is a Network Drive, which means that a file can be accessed by multiple people. When accessed using samba, it means that CRUD privileges are usually assigned to the user and not to others e.g. client machine system user for example.
This is why I raised the question including the context of using it within a NAS. I understand this issue is not related to the NAS, which was my question after all !
Cheers !
RapidWeaver project files are actually a special kind of Mac folder called a package. You can actually right-click the project files and select to view the package content.
It’s the Mac OS GUI that makes these special folders(directories) look like a single file. External file systems (even the terminal on your Mac) process each individual file (could be hundreds) within the package (folder) independently, so the project file gets “out of sync” and becomes unusable.
Many other people have had issues with project files becoming corrupted and unusable when they store them on cloud services (Dropbox, OneDrive, etc) and NAS drives.
I’d suggest you keep RW project files on a local hard drive while working on it. As for backup, you can set up your NAS Drive to use TimeMachine. That gives you the an hourly backup(snapshot) for the preceding 24 hours.
Noted, thank you for you reply
Just test if you get the same error when working on a local file.
That would mean everyone got this error when saving again after publishing. There must be something else going on.
And that is why I included the following blurb in the post.
I get this error message a lot. No NAS involved - just RW files on my HD. If I save the file, and then publish, that’s usually when it pops up. At least it’s not a crash, I say to myself.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.