Skip to content
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

Can't Use Slash Command: Create Inline Literature Note #53

Closed
li-chena opened this issue Dec 31, 2022 · 16 comments
Closed

Can't Use Slash Command: Create Inline Literature Note #53

li-chena opened this issue Dec 31, 2022 · 16 comments

Comments

@li-chena
Copy link

Error log from the console:Uncaught (in promise) TypeError: Cannot read properties of null (reading '0')

@Logseq Citations Plugin_software 2022-12-31 22-00-34_new

@kmk93posteo
Copy link

kmk93posteo commented Jan 4, 2023

For me, "insert inline" and "link to reference" both do not work. All three shortcuts lead me to the selection menu, but after selecting these two options, nothing (useful) happens - I am a layperson, sorry for the bad description. "go to reference" works perfectly fine so I just use it as a workaround.

@kerim
Copy link

kerim commented Jan 6, 2023

I'm having this problem as well. Nothing is happening. I am using 0.8.15

@sawhney17
Copy link
Owner

sawhney17 commented Jan 7, 2023 via email

@kerim
Copy link

kerim commented Jan 7, 2023

I never had such problems before, but I'm also not sure how frequently the versions have updated and whether or not I used it during each version or not. It has probably been about a month since I used it last.

@kerim
Copy link

kerim commented Jan 15, 2023

This seems to be working again for me now. Perhaps fixed in the last Logseq update?

@gandalf34
Copy link

I have the same issue.

@gandalf34
Copy link

@kerim
Copy link

kerim commented Feb 8, 2023

Yeah, this seems broken again with the latest update.

@sawhney17
Copy link
Owner

sawhney17 commented Feb 8, 2023 via email

@sawhney17
Copy link
Owner

sawhney17 commented Feb 8, 2023 via email

github-actions bot pushed a commit that referenced this issue Feb 8, 2023
## [3.0.1](v3.0.0...v3.0.1) (2023-02-08)

### Bug Fixes

* **error handling:** Add fallback database [#53](#53) ([631192c](631192c))
@sawhney17
Copy link
Owner

sawhney17 commented Feb 8, 2023 via email

@gandalf34
Copy link

gandalf34 commented Feb 8, 2023 via email

@kerim
Copy link

kerim commented Feb 8, 2023

Yes, I moved the database to the new location. Search works, but it won't create anything.

@sawhney17
Copy link
Owner

Try the new update.

sawhney17 added a commit that referenced this issue Feb 8, 2023
github-actions bot pushed a commit that referenced this issue Feb 8, 2023
## [3.0.4](v3.0.3...v3.0.4) (2023-02-08)

### Bug Fixes

* **bug:** the stupidest error ever [#53](#53) ([856662f](856662f))
@kerim
Copy link

kerim commented Feb 8, 2023

Seems fixed. Thanks!

@sawhney17
Copy link
Owner

sawhney17 commented Feb 8, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants