omnivore-app / logseq-omnivore

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

The articles aren't fetched #80

Closed yfhuang7 closed 1 year ago

yfhuang7 commented 1 year ago

Hi,

I currently changes the laptop and therefore the system from Windows to iOS. I used omnivore plugin with logseq under Windows without issue. However, when I use it with logseq under iOS, it didn't fetch any articles without any error message - The page was created with the title "## đź”– Articles" with zero articles included below. Any suggestion of what might go wrong and how to solve this?

Thank you!

jacksonh commented 1 year ago

Hi @yfhuang7 do you mind attaching a screenshot of your Logseq Omnivore plugin settings? (Just scroll the API key out of the way. That will help us debug.

yfhuang7 commented 1 year ago

Hi,

Thanks for helping. Here are the screenshot. Note that for the filter, I also tried the basic - “import just highlight’, and “import all my articles”. But I got the same results (see the attached screen record). Thanks for helping.





I also attache the screen record here for what’s going on when I tried to fetch: 

On Mar 16, 2023, at 1:50 PM, Jackson Harper @.***> wrote:

Hi @yfhuang7 https://github.com/yfhuang7 do you mind attaching a screenshot of your Logseq Omnivore plugin settings? (Just scroll the API key out of the way. That will help us debug.

— Reply to this email directly, view it on GitHub https://github.com/omnivore-app/logseq-omnivore/issues/80#issuecomment-1472907431, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBDGXRNU4R63NHE4RLQ473W4ORMJANCNFSM6AAAAAAV53UBA4. You are receiving this because you were mentioned.

emacsbliss commented 1 year ago

I'm seeing the same issue on MacOS as well.

sywhb commented 1 year ago

Hey @yfhuang7, sorry for the delay in reply.

I could not view your screenshot here. Could you upload them again? Thanks!

sywhb commented 1 year ago

Hey @emacsbliss, do you mind also showing me the screenshot of your plugin settings?

yfhuang7 commented 1 year ago

repost the screenshots again here, let me know if you still can't see it.

image image

https://user-images.githubusercontent.com/21115742/229197913-351c3416-b61c-41ac-a03f-c8e83775e68c.mov

sywhb commented 1 year ago

Hey @yfhuang7, thanks for providing the screenshot! The settings look correct to me.

May I know if this is the latest value of syncAt in your settings after you clicking on the "sync" button on the ribbon?

Screenshot 2023-04-01 at 10 12 49 AM

So if the articles are "synced" correctly, this value should be set to the current time.

Also, could you try to clear the syncAt value in the settings and try to sync again so I can trace from the logs?

yfhuang7 commented 1 year ago

I’ve tried clear the syncAt value and sync again. It’s still the same. After clicking “sync” button, the syncAt was updated to the time when I clicked the sync.

On Mar 31, 2023, at 4:14 PM, Hongbo Wu @.***> wrote:

Hey @yfhuang7 https://github.com/yfhuang7, thanks for providing the screenshot! The settings look correct to me.

May I know if this is the latest value of syncAt in your settings after you clicking on the "sync" button on the ribbon? https://user-images.githubusercontent.com/12963965/229261065-0d663442-2f69-48e3-ba75-62b418000a7a.png Also, could you try to clear the syncAt value in the settings and try to sync again so I can trace from the logs?

— Reply to this email directly, view it on GitHub https://github.com/omnivore-app/logseq-omnivore/issues/80#issuecomment-1492794892, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBDGXSC6JUUXHYDF3C5MWDW66FP7ANCNFSM6AAAAAAV53UBA4. You are receiving this because you were mentioned.

sywhb commented 1 year ago

Thanks for trying @yfhuang7

I finally was able to reproduce this issue. It is actually with the new version of Logseq App (not the system) and it will escape the characters in the plugin settings now.

So, we don't need the slash \ in the customQuery in the plugin settings to escape quotes ". I have verified it on my local machine and it works just fine.

To solve it, could you try to remove the slash in here?

Screenshot 2023-04-03 at 4 08 20 PM

And the new customQuery looks like this:

Screenshot 2023-04-03 at 4 10 31 PM

After updating the settings, you will need to resync the articles. You could either clear syncAt and sync. Or there is a command to resync everything in Omnivore by pressing Command + Shift + P on the keyboard to show the command palette and search for "Resync all Omnivore Articles" and click on it.

Screenshot 2023-04-03 at 4 14 23 PM
yfhuang7 commented 1 year ago

Yeah! It works now. Thanks for helping out!

On Apr 2, 2023, at 10:16 PM, Hongbo Wu @.***> wrote:

Thanks for trying @yfhuang7 https://github.com/yfhuang7 I finally was able to reproduce this issue. It is actually with the new version of Logseq App (not the system) and it will escape the characters in the plugin settings now.

So, we don't need the slash \ in the customQuery in the plugin settings to escape quotes ". I have verified it on my local machine and it works just fine.

To solve it, could you try to remove the slash in here? https://user-images.githubusercontent.com/12963965/229449699-3f6a583e-bf14-4724-b408-6b7b1bfd8e94.png And the new customQuery looks like this: https://user-images.githubusercontent.com/12963965/229450177-89cdf7aa-2a91-44fd-b742-9c7ab6d3cb45.png After updating the settings, you will need to resync the articles. You could either clear syncAt and sync. Or there is a command to resync everything in Omnivore by pressing Command + Shift + P on the keyboard to show the command palette and search for "Resync all Omnivore Articles" and click on it.

https://user-images.githubusercontent.com/12963965/229451384-47703819-c7d6-432b-be3f-a092f1bfbd56.png — Reply to this email directly, view it on GitHub https://github.com/omnivore-app/logseq-omnivore/issues/80#issuecomment-1493881002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBDGXRXR6T7IYUOM7WLCCLW7KBMBANCNFSM6AAAAAAV53UBA4. You are receiving this because you were mentioned.