Existing links in frontmatter fields incompatible with new frontmatter rendering

Bug reports
1

Steps to reproduce

Issue with existing files that have links in frontmatter fields
Can be re-created by making a new .md file in notepad with a field and link, eg:

consolename: [[xbox]]

Did you follow the troubleshooting guide? [Y]

Recreated issue in sandbox

Expected result

Functioning link in the frontmatter

Actual result

Link is replaced by orange text, and the frontmatter property can’t be edited

Environment

SYSTEM INFO:
Obsidian version: v1.4.12
Installer version: v1.3.3
Operating system: Windows 10 Pro 10.0.22000
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on

RECOMMENDATIONS:
none

Additional information

The screenshot shows the issue with an existing frontmatter field with link (appearing as orange text that cant be edited), and what it looks like if you make a new field with the new frontmatter renderer

obsidianpropertiesbug
obsidianpropertiesbug961×422 15.5 KB

2 
---
link: "[[Link]]" 
linklist: 
  - "[[Link]]" 
  - "[[Link2]]"
---
1 Like
3

Hi ariehen

Thanks for the response

Has it always been a requirement to enclose links in frontmatter with quotes?

I dion’t ever recall this being a requirement, and wasn’t needed for it to work. I now have hundreds of notes with links in the frontmatter fields, that worked perfectly fine before the update but now break the properties windows so you can’t edit them!

5

Yes, that was always a requirement to have a properly formatted yaml. You probably were living with incorrect YAML.

6

Easy to live with something if it works.

The solution for now then is to set the “Properties in document” setting to source.

image
image755×51 2.89 KB