I’ve had logseq installed on the machine for 4 months with no issues. Suddenly locked up and was giving this error:
Error caught by UI!
NotFoundError: Failed to execute ‘insertBefore’ on “Node”: the node before which the new node is to be inserted is not a child of this node.
I tried all the suggested solutions, I also uninstalled LogSeq, rebooted, then reinstalled from a new download. I’m still getting this error. No issues on the other 3 machines I run logseq and this notebook on.
Can you please share some more context about your setup, like what OS you’re using (including version), what version of Logseq your running, where your graph is stored, and whether you use plugins or a custom theme (and if so, what plugins and theme).
The more info you provide, the better we can help.
(P.S. I’ve moved your post from the feedback to the questions section so it’s easier to find. I’ve also made the title more descriptive so it’s more likely people will click into it. Otherwise this post will likely go ignored if people can’t glance from the title what it’s about.)
Problematic machine is running Windows 11 version 23H2. Logseq version 0.10.9. Notebook is run from OneDrive on multiple machines (three additional machines that are ok - Windows 11, WIndows 10, and MacOS). I did have some plugins and themes installed but they seem to have disappeared? Possibly when I went cleared local storage as suggested in the error popup.
This could be data corruption, which isn’t uncommon when using Logseq in combination with OneDrive. It’s the reason why we’ve created Logseq Sync (DM me for a free extended trial).
I suggest creating a new graph that’s stored locally (so not in any synced folder) to see if that works.
If it does, I suggest to manually move the subfolders (journals, pages, assets, etc.) from you old graph folder to the new graph folder and do a re-index of the new graph.
Just a follow-up. I uninstalled Logseq and manually deleted all the settings files from the c drive folders left after uninstall. Rebooted and reinstalled Logseq then reconnected to the existing OneDrive folders. This solved the issue. Thanks for all the help.