logseq-twitter-extractor
logseq-twitter-extractor copied to clipboard
Cannot read properties of undefined
when enabling the plugin got popup with following error
:plugin.logseq-tweet-extractor/ParseTwitter Cannot read properties of undefined (reading 'forEach')
ubuntu 22.10
logseq 0.8.9
Can you share the tweet you are trying to embed? Does it work with other tweets? On 20 Oct 2022 at 6:42 AM +0400, rachmadani haryono @.***>, wrote:
when enabling the plugin got popup with following error :plugin.logseq-tweet-extractor/ParseTwitter Cannot read properties of undefined (reading 'forEach') ubuntu 22.10 logseq 0.8.9 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
it happen when enabling the plugin, but i will try parse a tweet and report back if there is another error
e: no error happen when parsing the tweet
tweet test https://twitter.com/SteamDeckHQ/status/1582849436438261760
Yep in that case try restart the app. On 20 Oct 2022 at 7:18 AM +0400, rachmadani haryono @.***>, wrote:
it happen when enabling the plugin, but i will try parse a tweet and report back if there is another error — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
restarting the app with plugin enabled still have the same popup error
running it from cli show no error
> Logseq.AppImage
11:34:04.585 › Logseq App(0.8.9) Starting...
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!
11:34:09.086 › :electron.handler/watch-dir {:path "/home/r3r/.logseq/config"}
11:34:09.199 › :electron.handler/unwatch-dir {:path "/mnt/ac54dceb-73a5-4f94-b52c-cb7a426c0f29/Documents/private/logseq"}
11:34:09.200 › :electron.handler/watch-dir {:path "/mnt/ac54dceb-73a5-4f94-b52c-cb7a426c0f29/Documents/private/logseq"}
e:
setting i use
InsertionTemplateForBlock1: {TWEET} tweeted on {Date}, [[{Name} @{username}]] {URL}
InsertionTemplateForBlock2: empty
KeyboardShortcut: empty
I had the same issue when I started logseq using Windows 10 and Logseq 0.8.16. Deinstalling and re-installing the app fixed it for now.