I have one instance at work in Docker and another I host from home, also in Docker. I access both of them from the same browser at work. For some reason on the work instance, the Run command search has stopped working. I’ll type e.g. ‘template’ in, but the list doesn’t move or filter.
I get the following errors in the console
I don’t really understand what’s going on as there are no errors in the docker log output, and the instance I host from home works perfectly.
I have cleared my browser cache, run the ‘Clear Local Storage and Log Out’ function, neither which helped.
So it worked before and then stopped all of a sudden? What changed? And as I understand it it is just the command palette that stopped working?
Blindly guessing here: Did you perhaps create a new template of some sort, perhaps defining a command and that has an invalid value? Or no value (eg a snippet with a key but no command).
I’ve been through my templates and double checked plugs etc. today but couldn’t spot any issues.
I decided to delete the .silverbullet.md, .silverbullet.db-shm and .silverbullet.db-wal files, restarted the Docker container and it’s now working properly!
Unfortunately I can’t really tie this into anything that I did. That doesn’t mean to say I got a template wrong at some point, which caused some issue!
I just had this issue as well. I had one page open as a reference and the other i was building a template. All of my action buttons broke. I tried reloading, restarting, and importing libraries again. Craig’s solution worked for me. I think there is a certain workflow combination that breaks it. The last thing i remember before realizing it was broken was a yaml error on my template that i was in the middle of resolving. Silverbullet stopped saving my changes, thats when i tried to reload but couldnt and discovered the issue. I even tried manually deleting the template and the other page i had open and this still did not resolve the issue.
When this happens again, please have a look at your browser’s JavaScript console to see what’s happening as well as your server log. This will be very helpful to fix the issue properly.
Yes sir, ill take note of the server log next time. I did get this screenshot before I tried Craig’s solution. I’m not sure if its related or not though. I believe this error arose when trying to click on the page picker action button.
I found that I was able to reproduce this issue through using the Page Navigation picker after what I believe is an incorrect template formatting. Need to continue debugging.
