First, search the help docs and this forum. Maybe your question has been answered! The debugging steps can help, too. Still stuck? Delete this line and proceed.
What I’m trying to do
I am trying to revert back to previous YAML view. The current view (1.4) negates all the tags that I have. They don’t show up at all. I don’t want to have to reenter them all.
Things I have tried
I have attempted to read through documentation, did a search via google, looked at switches under Core Plugins and haven’t been able to find a way to do this. Thanks for the help. Apologies if this is a simple fix that I missed.
I have been using the #Tag (example #Personal) protocol for some time. It is pretty standard with other apps. I can no longer do that in this iteration, even switching to Source Mode. If I enter #Personal, Obsidian indicates that it is not a valid entry for a Tag and will delete it. I have been a big fan of Obsidian and even did the paid version (moving from Evernote). But this has kind of broken it for me. I often use a text editor app and save to .md and then move file into Obsidian vault. This isn’t good.
Well… why not add an option to disable the feature? I don’t see why everyone would want to have it. Plus I don’t want to disable live preview just to not have this feature.
Where exactly do you key in #Personal? In the frontmatter (YAML) section as the value of the tags key or as an inline (Dataview) YAML key, e.g., tags:: #Personal?
We need to know where and when the issue breaks your workflow.
Well, it used to work - and when importing notes from other apps, it was really helpful to not have to edit them. And Tags - Obsidian Help does show hashtags at the bottom of the page being used.
Thanks for the help. Will drop the hashtag going forward. However, Evernote export (using Evernote export, and Obsidian Evernote plugin) uses the hashtag in the YAML section. So apparently it is somewhat standard procedure.
Hashes are allowed in YAML as comment indicators. In the image below, you can see that #hash in the YAML is not recognized as a tag (because it is a comment), so it is not read in queries (see the example q1 hash). The #yesahash tag in the body can be queried.