Major bug: Incompatible with Obsidian's latest core plugin "properties"
yshhwy opened this issue · 7 comments
*Environment: latest version of Obsidian and latest version of Anki
Describe the bug
When a file exists with properties (original yaml area), although synchronizing cards creates new cards in Anki, it does not return and add the card ID to the note. After testing, the plugin only works as expected when the yaml area is blank, but after one sync, the yaml area creates the card-deck field, causing the second and subsequent syncs to be abnormal.
To Reproduce
Steps to reproduce the behavior:
- Create a file with properties (original yaml area).
- Write a card
- Run the synchronize command
or:
- Create a blank file
- Write a card
- Run the synchronize command
- Write another card
- Run the synchronize command again
Markdown used
# Question #card
Answer
Additional context
I hope it'll be fixed soon. It's affecting the use of this beloved plugin in the latest version of Obsidian!
Thank you for taking the time to report the issue and help me to make the project better! 🙂
I am a software-architect, but i developed about 20 years, but mostly in C#. So i am no expert in TypeScript. But the problem could be, that the "Properties" are readonly. And this function does not work:
I am to busy at the moment, to invest more time in it. And i also might be wrong. But i hope, it could help.
Oh, i have seen, there seem to be a PR fixing this problem. I didnt see it before. I am getting old... ;)
Can we get the PR approved and merged? So it will fix this issue
Hello, I wonder if you found a solution for this issue? It seems to be working with the new Obsidian version, but it can't handle the tags add in the "properties" of the note.
Hello, I wonder if you found a solution for this issue? It seems to be working with the new Obsidian version, but it can't handle the tags add in the "properties" of the note.
Try this if anyone encounter the same problem. Download and replace. It works well for me, v1.4.12 Obsidian. #197 (comment)
is this of any interest to anyone anymore?
it leaves the plugin completely unusable.