Closed Ryuuramaru closed 3 months ago
Just tested (probably should have done this beforehand), this does NOT happen inside a new vault with only Longform installed. The console also does not log any errors:
Disabling all plugins from my actual vault and restarting Obsidian does NOT fix the issue. It does however only generate 1 error instead of 2.
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'length')
at ignoredPatternToRegex (plugin:longform:36596:41)
at eval (plugin:longform:36543:64)
at Array.map (<anonymous>)
at StoreVaultSync.eval (plugin:longform:36543:53)
at Generator.next (<anonymous>)
at fulfilled (plugin:longform:28:58)
I managed to fix it:
This will cause the Index file to be created in the place of the old one, and all scenes will be picked up by the auto-adder. I have no idea why this works however, but I'm leaving it here just in case anyone else has issues.
This fix also removes all errors in the console, in case this info proves useful.
Closing this as I managed to fix it on my own, and it could just be due to an Obsidian update. If it reoccurs, I will reopen it.
Versions Longform version: 2.0.7 Obsidian version: 1.6.7 (happened on 1.6.5 also, but did NOT happen before that) OS [e.g. macOS, Windows, iOS, Android]: Linux (Flatpak), Android Theme: default Other plugins that you think might be relevant here:
Describe the bug
These are two separate behaviors, but I feel like they're part of the same bug.
To Reproduce Steps to reproduce the behavior:
OR
Expected behavior Longform should properly update and read its index file to keep track of a user's project.
Screenshots
First Behaviour: Upon opening Obsidian: Upon manually editing the Index file:
Second Behaviour: Pre-change: Post-change (notice the Index file is unchanged):
Additional context
Console errors: