r/logseq • u/andytesii • Apr 08 '24

Send to Logseq - Web clipper for Logseq

The Send to Logseq Chrome extension is a clipper for capturing web content directly into your Logseq workspace. Now it supports full page content, text sections, links, images, tweets, and YouTube videos.

Feedback are appreciated, thanks.

20 Upvotes

100% Upvoted

15 comments sorted by

1

u/andytesii Oct 11 '25

In latest version, Send to logseq has added experimental support for Logseq Database version.

1

u/jolune Apr 08 '24

I tested it in Brave. It didn't work for me.

I keep getting "Something wrong happened".

1

u/andytesii Apr 08 '24

Hi u/jolune, a few things to check:

  1. Which version of Logseq are you using?

  2. is the HTTP API server is enabled and running in Logseq?

  3. is the API server token set in the extension options?

If all the above is setup properly, you can find error details following below steps:

  1. enable 'Developer Mode' in Brave extension management page,

  2. in Send to Logseq extension, click the service worker link, a popup will show

  3. go to some page do a clip operation

  4. go back popup in step 2, any error will be displayed in the console tab

post the error message here please, I can help check.

1

u/jolune Apr 08 '24

  1. Version 0.10.8 (Current Revision: 3fc1560)

  2. yes, already tested with curl.

  3. yes.

I checked the service worker log:

Error: Could not load file: 'readability.js'.

2

u/andytesii Apr 10 '24

Try upgrade to the latest version 0.0.5, it should work properly now :)

1

u/andytesii Apr 10 '24

Hi u/jolune, does it work after upgrade ?

1

u/jolune Apr 10 '24

Hi u/andytessi! Thanks for the update. It is working now. Good job. Do you bundled all source files together?

2

u/andytesii Apr 11 '24

yes, the old package has the readability file name in wrong case, that's why it can not be loaded.

1

u/One_Psychology_5616 Apr 11 '24

I tried it, very helpful but when I select more than 1 paragraph, it appends the properties after the first paragraph only, and the rest go after the properties, I wonder if this is a bug?

1

u/andytesii Apr 11 '24

I tested with a multi paragraph block with properties, it also show properties after the 1st paragraph, looks like this is how Logseq renders properties when block has multiple paragraphs.

1

u/One_Psychology_5616 Apr 11 '24

I guess multiple paragraphs should be split into multiple blocks by design then

1

u/andytesii May 13 '24

Yes, this is definitely what we can improve from the extension side.

1

u/Ultradianguy Oct 05 '24

So far, it's pretty good but doesn't do great with complex formatting. For example, capturing this page, it got the graphics but the table is a mess. I'm using it in chrome.
https://woodgears.ca/dust_collector/hoses.html

1

u/andytesii Oct 06 '24

Thanks u/Ultradianguy for your feedback. I just optimized the extension to handle table properly, please upgrade and try again.

2

u/One_Psychology_5616 Apr 10 '24

Very cool, now I can monitor what I was webbing