> [!NOTE] Title
> [[File]]
[](New%20File.md)
> [!NOTE] Title
> [[File]]
Environment
SYSTEM INFO:
Obsidian version: v1.6.3
Installer version: v1.4.13
Operating system: Darwin Kernel Version 23.5.0: Wed May 1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 23.5.0
Login status: logged in
Catalyst license: supporter
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 0
Plugins enabled: 0
RECOMMENDATIONS:
none
Additional information
The error does not occur for internal links within untitled callouts.
Thanks for this bug report! This bug mangled up many notes of mine. I thought it was caused by core plugin Backlinks. I wasn’t aware that it is the renaming itself that causes trouble.
Here’s a GIF of your wonderfully simple test with a titled callout:
And for comparison with an untitled callout:
In my opinion this is a major bug, because this is an Obsidian core feature destroying data.
SYSTEM INFO:
Obsidian version: v1.6.3
Installer version: v1.4.13
Operating system: Darwin Kernel Version 23.5.0: Wed May 1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 23.5.0
Login status: logged in
Catalyst license: supporter
Insider build toggle: on
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none
Would someone mind explaining why rebuilding the vault cache should address this problem if it persists? I do not totally follow. I am on 1.6.5 with plugins/css snippets disabled and still encounter the issue in some instances, although I am still working on pinning down exactly when/why. Trying out the sandboxed example that started this thread works fine — indeed, it is only on my old notes that the issue persists. So in some sense I would not be surprised if rebuilding the metadata cache will resolve the problem once and for all, but some assurance would be great before I continue the vault-refactoring that caused me to encounter this issue in the first place.
I think we are dealing with two overlapping problems. One is an incorrect cache. This can be fixed by updating the cache. The other problem are previous erroneous changes in Markdown files, that were the consequence of previous caching errors. They need to be fixed manually.