pyrochlore / obsidian-tracker Public
generated from obsidianmd/obsidian-sample-pluginNew issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Obsidian update breaks functionality #102
Comments
|
Also experiencing this issue, with tracker pages that worked mere hours ago |
|
Found, at the very least, a temporary solution to this issue. By checking the developer console (CTRL-SHIFT-I), and looking into the error messages, it appears as though this error was popping up a lot "YAMLParseError: Tabs are not allowed as indentation at line 5, column 1:". So I changed my indentation from tabs to spaces, and now everything works as expected. Attached is a screenshot of the error in question. |
|
Wow. I can't believe that was the solution. Is this an Obsidian issue or Tracker issue? |
|
No idea. My guess is an Obsidian issue, since it worked in the previous version of Obsidian just fine, and the only thing that changed was the update. I'm not a developer though, just happened upon the console while trying to mess with CSS the other day, and thought to check it for this issue. |
|
Yeah...it does seem very odd. I guess someone is taking a hard stance on tabs vs spaces :P |
|
Reported bug upstream on the Obsidian forum. |
|
According to the YAML specs, a |
|
Thanks for the additional info! That's useful to know :) |
|
Obsidian tracker version 1.10.9 will replace the tab characters by spaces for you according to the tabSize settings in editor. |
|
Aww. That's such a sweet little quality of life improvement. Cheers! |

I just updated to the newest version of Obsidian (v0.13.14) and all my tracker pages are returning "Error parsing YAML".
Here's some examples of code I'm using that result in this issue:
I'm not very code-savvy, so I'm not really sure where to begin with diagnosing and resolving this issue myself. I don't use many add-ons, but the few I do use are up to date. Thanks in advance!
The text was updated successfully, but these errors were encountered: