Hi
I set my Default location for new attachments
to In Subfolder under current folder
I set the subfolder name
to “_assets”
I restart Obsidian and those settings are back to “in the folder specified below”
I am using Win11 , 1.8.10
Hi
I set my Default location for new attachments
to In Subfolder under current folder
I set the subfolder name
to “_assets”
I restart Obsidian and those settings are back to “in the folder specified below”
I am using Win11 , 1.8.10
What is your Obsidian installer version as well?
Are you storing your vault in a cloud sync tool, like OneDrive? If you are, I suggest looking inside your Vault/.obsidian folder and checking if there are any sync conflicts, like duplicated files. Or files that are set to be cloud-only, instead of fully downloaded to your computer.
Hi
This is the app.json
when I save with my setting. To me , it seems like Obsidian reloads the “assets” setting during reopening it then overrides the app.json
file
This is the app.json
after I restart Obsidian
Stored in a cloud tool?
No it is not but the settings files (like app.json) are symlinked from a drive that is on the same system, this necessary for me to keep all my notes same structure across couple systems, I use the same symlink/junctions to reconstruct the same folder structures on other systems.
It seems to me that Obsidian loads this particular setting from some other default and overwrites the app.json in my vault.
symlinks are warned against in the documentation. And I’ve seen a feature request asking for more direct symlink support.
I just set my attachments folder as _assets
, the setting is sticking after a full restart, and reads as:
in the app.json
file.
I wonder where the leading period and slash, ./_assets
, in your app.json
is coming from.
That seems likely to cause problems: Obsidian doesn’t support hidden files or folders (with the exception of .obsidian
).
Ah, was typing on mobile and didn’t scroll the full viewport – maybe from the symlink setup.
Thanks I will give it a try.
After days of troubleshooting, I finally identified the problem. The “workspace-plus” plugin was overriding the file location. I hope this is helpful to others.