Hello @uriahs-victor
That’s a great question regarding the .DS_Store files created by macOS.
To see how we can best prevent this, could you please provide us with details about your exact workflow?
Specifically, could you describe:
- Your Workflow: What steps do you take on your Mac (which files do you interact with, and where) that result in the creation of the
.DS_Store files?
- Which specific files or folders are you backing up/migrating that contain these files?
- Where exactly do the
.DS_Store files appear on the server after the restoration is complete?
Understanding your precise workflow will help us evaluate possibilities in our plugin’s process to implement an automatic deletion or exclusion rule.
Thanks,
All the best,
I’m a dev so I build sites locally and create any custom plugins needed for the site locally. I use LocalWP, I think MacOS adds the .DS_Store to the folders of the custom plugins I might interact with. But I’m not sure what the pattern is. I just know that I’d find .DS_Store files when browsing the site after its been migrated to live.
I’m not sure at what point MacOS adds the .DS_Store files to a folder.
Hi there. We’ll look into this and get back to you shortly.
Hello @uriahs-victor
Just a quick update:
After researching this issue, we’ve decided to address it directly by adding a built-in feature to the plugin that will automatically exclude .DS_Store files from both the backup and restoration process.
This feature will be included in the next public release.
Thank you very much again for bringing this to our attention!
All the best,
Hello @uriahs-victor
Just a quick update: we’ve released version 0.9.122 of the WPvivid Backup Plugin, which now automatically excludes macOS .DS_Store files during backups and migrations.
Please update the plugin to the latest version and let us know how it works for you. Thanks for bringing this to our attention, we really appreciate the feedback!
All the best,
