-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
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. |
I'm having this problem as well. Nothing is happening. I am using 0.8.15 |
Was it working in the previous version?
…On 6 Jan 2023, 10:51 PM +0400, P. Kerim Friedman ***@***.***>, wrote:
I'm having this problem as well. Nothing is happening. I am using 0.8.15
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
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. |
This seems to be working again for me now. Perhaps fixed in the last Logseq update? |
I have the same issue. |
Yeah, this seems broken again with the latest update. |
Investigating this.
Sincerely, Aryan Sawhney Homeroom 7.11
…On 8 Feb 2023, 10:05 AM +0400, P. Kerim Friedman ***@***.***>, wrote:
Yeah, this seems broken again with the latest update.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Have you moved the database to the new location in the assets folder?
Sincerely, Aryan Sawhney Homeroom 7.11
…On 8 Feb 2023, 12:35 PM +0400, Aryan Sawhney ***@***.***>, wrote:
Investigating this.
Sincerely, Aryan Sawhney Homeroom 7.11
On 8 Feb 2023, 10:05 AM +0400, P. Kerim Friedman ***@***.***>, wrote:
> Yeah, this seems broken again with the latest update.
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you commented.Message ID: ***@***.***>
|
## [3.0.1](v3.0.0...v3.0.1) (2023-02-08) ### Bug Fixes * **error handling:** Add fallback database [#53](#53) ([631192c](631192c))
I’ve added a fallback in the latest version, which would prevent the change from breaking workflows.
…On 8 Feb 2023, 12:37 PM +0400, Aryan Sawhney ***@***.***>, wrote:
Have you moved the database to the new location in the assets folder?
Sincerely, Aryan Sawhney Homeroom 7.11
On 8 Feb 2023, 12:35 PM +0400, Aryan Sawhney ***@***.***>, wrote:
> Investigating this.
>
> Sincerely, Aryan Sawhney Homeroom 7.11
> On 8 Feb 2023, 10:05 AM +0400, P. Kerim Friedman ***@***.***>, wrote:
> > Yeah, this seems broken again with the latest update.
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you commented.Message ID: ***@***.***>
|
Yes it was there at the time of the video
…On Wed, Feb 8, 2023, 11:38 Aryan Sawhney ***@***.***> wrote:
Have you moved the database to the new location in the assets folder?
Sincerely, Aryan Sawhney Homeroom 7.11
On 8 Feb 2023, 12:35 PM +0400, Aryan Sawhney ***@***.***>, wrote:
> Investigating this.
>
> Sincerely, Aryan Sawhney Homeroom 7.11
> On 8 Feb 2023, 10:05 AM +0400, P. Kerim Friedman ***@***.***>, wrote:
> > Yeah, this seems broken again with the latest update.
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
</~https://github.com/notifications/unsubscribe-auth/AUTAGGJS7U2YGCO3EXYBHHLWWNLPPANCNFSM6AAAAAATNXFJVA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yes, I moved the database to the new location. Search works, but it won't create anything. |
Try the new update. |
## [3.0.4](v3.0.3...v3.0.4) (2023-02-08) ### Bug Fixes * **bug:** the stupidest error ever [#53](#53) ([856662f](856662f))
Seems fixed. Thanks! |
Very stupid error. Used a single equal instead of double equals. Good to see it's fixed.
…On 8 Feb 2023 at 11:08 PM +0400, P. Kerim Friedman ***@***.***>, wrote:
Seems fixed. Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Error log from the console:Uncaught (in promise) TypeError: Cannot read properties of null (reading '0')
The text was updated successfully, but these errors were encountered: