Closed charleshan closed 2 years ago
Same issue here with NLD v0.6.0 and Obsidian v0.12.19
Yes, same issue here with NLD v0.6.0 and Obsidian v0.12.19
Same issue Obsididan v0.12.19
Hello, I created a GitHub account just to comment for this specific issue because that is how much I use this plugin in my day to day. As the people above posted, plugin stopped working on v0.12.19.
Thank you for for the awesome plug in btw. 😁😁
Hello, I created a GitHub account just to comment for this specific issue because that is how much I use this plugin in my day to day. As the people above posted, plugin stopped working on v0.12.19.
Thank you for for the awesome plug in btw. 😁😁
Also use this everyday.
Rolling the plugin back to 0.5.2 let me get back working again.
Release is here https://github.com/argenos/nldates-obsidian/releases/tag/0.5.2
Hey @sethlester , thank you for the reply and the quick solution.
I got the plugin to work again but now every time I hit the "@" to enable the plugin, I get a rectangular menu bar pop up which I never had. Prior to the bug, I had a minimal date suggest pop under what I was typing, think more of a spelling check. Minor inconvenience but very grateful to just have the main functionality be working again.
Thank you!
It's working fine here as well. Thanks!
this is still an issue for me. other than reverting to the previous version, is there a fix planned? it's working on mobile but not on desktop.
It is working again, for me, using the current insider releases. Looks like a regression on Obsidian's end, not the plugin.
Thanks, I will wait for the Obsidian release update
Hi, sorry for the confusion.
This was an issue with the new version (that's only compatible with the Insider Build of Obsidian) from getting released a bit prematurely. We made a fix so that Obsidian will now find the correct version, but if you have the wrong version installed, you'll need to uninstall the plugin and reinstall it from the Community Plugins store. Sorry again about the mix-up!
Trigger not working in 0.12.19
I'm seeing this error in the dev console: