You are the first user reporting an issue with kits. Here are some steps:
- Ensure that
custom.js
is allowed to run. - Ensure that you have copied the whole code inside
custom.js
- Indeed css and other macros are optional.
- You may want to temporarily add these too, to help with investigation.
- Indeed css and other macros are optional.
- But if you don’t get “kits ok” when Logseq starts, nothing is expected to work.
- This is a pop-up at the top-right of the screen.
- Indeed this is triggered by the last command.
- To investigate why it doesn’t get executed:
- open the console with
Ctrl+ Shift + i
- check for any errors there
- preferably right after starting Logseq, to have a clean console
- report back with any findings
- open the console with