search

omnivore-app / logseq-omnivore

Logseq plugin to fetch articles and highlights from Omnivore
MIT License
278 stars 15 forks source link

logseq import issues: multiple problems #123

Closed n9n9n9 closed 10 months ago

n9n9n9 commented 11 months ago

logseq 0.9.11 on macos 13.4.1: fresh os install, fresh logseq install, built my local graph using logseq's sync. omnivore is a fresh install, is the only plugin installed.

what I did: went into omnivore and labelled approximately 80 articles with label "tarot" went to logseq and set things like this:

advanced sync label:tarot do not sync to single page (I want a page each for these articles.)

Here's what happened: when I sync the logseq display jumps around quite a bit, I see it adding blocks to the omnivore page, I do not see it making pages for the articles being imported, and then when it is done I see the omnivore page get erased.

Here's what I tried: I set the templates for import to be as simple as possible, wondering if there was a parsing error on the aricle data or something. when I did this I saw the same behavior as above but my omnivore page was full of the "article" blocks, one per article. I still didn't get my dedicated pages, though.

If you look here: https://discord.com/channels/844965259462311966/1115896629124411504/1135420298301292575 you will see everything you need -- screenshots, narrative, copies of my settings.

jacksonh commented 10 months ago

Hey @n9n9n9 i think we discussed this all on Discord and mostly worked it out. I'll close this based on that convo, i know there's some issues regarding writing content to logseq but those are covered in some other issues, and more-so a Logseq limitation.

let me know if I'm wrong though!

n9n9n9 commented 10 months ago

sounds good!

Robert Monn 646-259-3297 Sent with Spark On Aug 18, 2023 at 3:00 AM -0700, Jackson Harper @.***>, wrote:

Hey @n9n9n9 i think we discussed this all on Discord and mostly worked it out. I'll close this based on that convo, i know there's some issues regarding writing content to logseq but those are covered in some other issues, and more-so a Logseq limitation. let me know if I'm wrong though! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>