-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Plugin fails to load properly when installing/enabling it the first time #18
Comments
I have installed it manually by pasting the files main.js manifest.json styles.css into the obsidian plugins directory. It would really be wonderful if you could test that in a fresh vault to see if it's just me or the current Obsidian versions. The "field is not present in this state" error occurs on every range:
|
Finally a restart of the whole vault after the plugin installation solved it. |
I'm reopening this issue as I definitely do not intend for users having to restart Obsidian in order to have this plugin to work, besides, it does seem like it is some kind of race condition between the plugin initalisation and the codemirror extensions - which only occurs if the plugin is not initialised with the loading of the app. Many thank for the detailed issue report and checking the sandbox vault. I will try to fix this as soon as I have some time again (which should be a month from now) |
Addendum, potentially related to #16 |
Thank you for the feedback and reopening the topic. Please excuse me for closing it so quickly. Of course, modifying the plugin to make it available to all users without a restart is much better. |
I can't start the plugin either, I get the error message when trying to activate the plugin. SYSTEM INFO: |
When this Plugin is installed with BRAT (sandbox vault without any other plugins than BRAT):
https://github.com/TfTHacker/obsidian42-brat
It's causing many errors and showing me no sidebars and commands:
Do you plan to make this plugin available for BRAT / Community Plugin store inside Obsidian?
The text was updated successfully, but these errors were encountered: