Logfile? I get permanently "failed to fetch articles" error

[marcfree]

Hey first, thanks for the great plugin. Unfortunatly, since recently I can't sync my articles anymore, and the error I get is failed to fetch articles There was no change in the API key, just a little update to have date-read in my template. But even returning to the previous version of the template, the sync doesn't work. How can I check, what's going on?

[thiswillbeyourgithub]

Hi, I have the same feeling. I feel bad creating issues with no logs nor ideas of what went wrong.

I support the idea of improving the logging situation!

[jacksonh]

Hey first, thanks for the great plugin. Unfortunatly, since recently I can't sync my articles anymore, and the error I get is failed to fetch articles There was no change in the API key, just a little update to have date-read in my template. But even returning to the previous version of the template, the sync doesn't work. How can I check, what's going on?

hi, in logseq you can go "View" -> "Toggle Developer Tools"

[marcfree]

Hi, thanks for the advice with the developer tools. So I've enabled the developer tools and found a log file which says exactly nothing. I've updated to config for Omnivore, and requested the articles - and there is just nothing in the logs. I found the file main.log right here: /Users/xy/Library/Logs/Logseq and here is the content: main2.log Spoiler: not one line for Omnivore :(

[thiswillbeyourgithub]

(For the record I was already aware of the way to toggle the developper tools but, finding nothing useful for the omnivore plugin, I came to the conclusion that adding a few debug prints would be useful)

[jacksonh]

Hi, thanks for the advice with the developer tools. So I've enabled the developer tools and found a log file which says exactly nothing. I've updated to config for Omnivore, and requested the articles - and there is just nothing in the logs. I found the file main.log right here: /Users/xy/Library/Logs/Logseq and here is the content: main2.log Spoiler: not one line for Omnivore :(

Hi, there should be a console that is printed to in the developer tools. Something like this:

[marcfree]

Hi Jackson, thanks again for your help. In Logseg I can't find such a console. There are also no commands in the command list or menus ;( (have looked for DEV, Error, Entwickler (DEV in German :) ), failure etc. Any other idea ? Thanks, Marc

[richd67]

Another Logseq user here with the same problem, no sync for the last 6 days or so? No changes on my side?

[marcfree]

I just played around with Wireshark, to figure out, what's going on. And it seems to me, just absolutely nothing. 1st) I tried using the Omnivore-App on MacOS. It calls up the API like desired and fetches the article I've chosen. 2nd) I start LogSeq, and there is no visible package addressed to the API of Omnivore and as such, no error message. To be sure, I tried yesterday, and had another try today - same result. No outgoing API Call from Logseq-omnivore plugin :(

[marcfree]

So, today I have had again a look into this topic. I guess it's a user error (at least on my side). I've recently added a new field in my template for new articles. I pretty sure, it has worked until a previous version, as I wasn't aware of this behaviour. Here's what happened: First: I found the development console in the Mac Version of Logseq is triggered by Command-Option-I. So, I've acitivated Dev-Mode, and started the Dev-Console. Finally, I pressed the "Omnivore" button in Legseq. The console showed then an error, saying

So, then I had a look here: https://docs.omnivore.app/integrations/logseq.html#controlling-the-layout-of-the-data-imported-to-logseq While it was not the first time, I found, that there is different handling for variables and sections - wasn't aware of this. So, I've removed the sections for date-saved, published and read - and voila - Omnivore is syncing again 👍 Section: {{#labels.length}} labels:: {{#labels}}[[{{{name}}}]] {{/labels}} {{/labels.length}} Fields: date-saved:: {{{dateSaved}}} date-published:: {{{datePublished}}} date-read:: {{{dateRead}}}

[thiswillbeyourgithub]

Sadly this is the not case for me. And I still have the plugin disabled on startup, for no reason that left something in the log.

[richd67]

Still not working for me??

[jacksonh]

Hi Jackson, thanks again for your help. In Logseg I can't find such a console. There are also no commands in the command list or menus ;( (have looked for DEV, Error, Entwickler (DEV in German :) ), failure etc. Any other idea ? Thanks, Marc

Hey here is a video: https://www.loom.com/share/d404390368e6434db572dc2d837bd4cc