-
Notifications
You must be signed in to change notification settings - Fork 5
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
Does not work with Homepage plugin #109
Comments
Performance and error messages when errors occurcaught (in promise) TypeError: Cannot read properties of null (reading 'view') plugin:map-of-content:2937 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'view') |
Also conflict with obsidian workspace function. Turn on the obsidian core function 'workspace' and this plugin, obsidian will go wrong with only blank, and unbale to open any file in obsidian. |
Thank you for creating the issue, i will look into it ASAP |
I would also like to chime in and say that I am getting the same issue. Disabling the plugin is necessary for me at the moment since it conflicts with workspaces. |
Sorry for the long wait. It's been incredibly busy at work lately. I'm releasing the fix now. |
Thank you so much for your work. Appreciate it! |
Marveling at the efficiency of the repair, it was amazing !
…------------------ 原始邮件 ------------------
发件人: "Robin-Haupt-1/Obsidian-Map-of-Content" ***@***.***>;
发送时间: 2023年9月2日(星期六) 凌晨3:33
***@***.***>;
***@***.******@***.***>;
主题: Re: [Robin-Haupt-1/Obsidian-Map-of-Content] Does not work with Homepage plugin (Issue #109)
Closed #109 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I enabled the Homepage plugin and this plugin, set up a workspace containing the plugin's leaf view, and specified that this workspace would open automatically when opened. When I reopened the library, the left and right leaves and the editing page in the middle were completely blank. When I closed the homepage or this plugin, the error disappeared
The text was updated successfully, but these errors were encountered: