Closed huachuman closed 10 months ago
Thank you for letting me know! I will look into this right away.
Extra info:
This is what you should see, normally (and this is what I am seeing):
Early tests:
I learned that there is a "debug info" command in Obsidian :-) It displays something like this:
That could be helpful :-) although it provides too much info. Just the first 4 lines (if possible).
@huachuman
Could you try updating / installing version 0.2.8 ?
I improved the code but also disabled the writing to log file by default. Although I was not able to reproduce the error, I had a look at the code and improved a part related to writing to a log file, which miiiight perhaps cause issues (file access on various platforms is prone to exceptions).
I'm on Windows 11. I just updated the plugin and although it didn't seem to work at first, restarting obsidian after updating the plugin worked!!
Awesome, glad it works now. As it worked for me on Win11... it's possible or likely that you didn't have a recent enough version? 🤔
Which means I need to try and test with older versions to be able to indicate the minimum supported version more accurately 🤞👍
On Thu, Oct 12, 2023, 11:29 huachuman @.***> wrote:
I'm on Windows 11. I just updated the plugin and although it didn't seem to work at first, restarting obsidian after updating the plugin worked!!
— Reply to this email directly, view it on GitHub https://github.com/CtrlAltFocus/obsidian-plugin-auto-tag/issues/7#issuecomment-1759260270, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6SAW6NJCGCL3YPLCWCDJ23X66Z7NANCNFSM6AAAAAA52GXEWQ . You are receiving this because you were assigned.Message ID: @.***>
Insider build.
However I have never ever seen this problem and have installed hundreds of community plugins before.
So my fix did fix something, glad 😄 and sorry for that!
I wish I could add my API key but there's no plugin settings for this.