Safari App Extension for Joplin now available

johnny · 2020-06-24T09:16:09.314Z

I am not an Apple user but I can imagine that this problem occurs when the clipper service isn’t enabled in the joplin options. Did you enabled the service (in Joplin Desktop go to: Tools–>Options–>Web clipper and click on “Enable Web Clipper Service”)?

LastStarfighterAJ · 2020-06-24T09:23:25.709Z

The web clipper service is running. I’ve been using it via Firefox extensions for some time without issue.

The extension on Safari also shows the green light that it sees the web clipper service is running

cweirup · 2020-06-24T11:33:08.399Z

Are you seeing this on every page you visit or pages you already have loaded in Safari? One thing to try is to reload the page and try it again.

For some reason, if you try to run the Extension right after it is installed on a page that was previously loaded, it hangs at “Processing”. If you refresh/reload, it should work as designed. I believe it has to do with the content script not being fully injected but I need to investigate further.

LastStarfighterAJ · 2020-06-24T11:40:47.423Z

Thanks Chris,

You seem to have solved the issue here. I couldn’t recall if I’d reloaded the pages I tried it with since installing the app. I tend to keep a lot of tabs open in Safari. Trying it on a new tab loaded up after installing the Webclipper plugin seems to work perfectly.

Thanks again for all your hard work on this.

petty · 2020-06-30T16:55:15.729Z

The extension is awesome!

I don’t think the timing is bad at all. Yes, Web Extensions API will be in macOS Big Sur … but that releases this Fall & will take a year to really permeate. Your extension will be useful & valid for much longer considering those that lag on OS updates (as potentially bad as that might be).

This fills a gap perfectly.

cweirup · 2020-07-01T13:41:31.224Z

Thanks! I appreciate the words of encouragement.

bbchase · 2020-09-07T22:37:35.113Z

This is awesome and might be what lets me switch to Joplin.
I might be missing if you said this, but how do I install this once I’ve cloned the repo?

cweirup · 2020-09-08T01:34:36.700Z

You don’t need to clone the repo to install it. There’s a compiled version of it under Releases.

You can get the latest here: https://github.com/cweirup/JoplinSafariWebClipper/releases/download/v.0.1.3/Joplin.Clipper.zip

Just unzip, move the executable to the Applications folder, and run the app once. You’ll be prompted to enable it in Safari Extensions, then you should be good to go.

bbchase · 2020-09-08T04:16:43.929Z

Ah, ok. I wasn’t seeing the releases link. Thanks!

LastStarfighterAJ · 2020-10-02T10:45:02.756Z

Just a heads up, this web clipper app seems to still work following an upgrade to Safari 14 (which is supposed to enable chrome extensions).

cweirup · 2020-12-14T15:46:15.426Z

Hi everyone! Just wanted to let you all know that I updated the Safari App Extension to support the new APIs introduced in Joplin v1.4.12.

If you are running that version or later of Joplin, you will need to upgrade to this latest version of the Extension (v0.2.0); otherwise, you will no longer be able to select folders or save pages.

Latest Version of Extension: https://github.com/cweirup/JoplinSafariWebClipper/releases/download/v0.2.0/Joplin.Clipper.zip

Thanks!
Chris

Stany · 2020-12-29T12:19:47.364Z

Thank you very much, your extension works perfectly !

pvod · 2021-03-02T15:47:57.508Z

Hey this looks great, thanks for you effort.
Do you have plans on merging this to the original Joplin repository? Can I help in any way?

leclercfl · 2021-07-20T19:34:23.644Z

Where can I get the updated version of the web clipper for safari 14 compatible with the desktop application 2.1.9 ? Thanks.

laurent · 2021-07-20T22:51:55.113Z

@cweirup, if that can help I've documented there how to get the token from the API: joplin/clipper_auth.md at dev · laurent22/joplin · GitHub

cweirup · 2021-07-21T02:02:25.253Z

@leclercfl Still working on it. I have something working but it's pretty rough. I've been pulled into a work project that's limited my free time, but I'm hoping to have an update published in the next week or so. I'll post something here when it's ready.

@laurent Thanks for sharing that info! That's been a big help!

Thanks!
Chris

cweirup · 2021-07-23T12:54:47.598Z

@leclercfl I have a new build that should support the authorization mechanism in Joplin now. Check it out with Joplin v2.1.5 or later. You will most likely encounter bugs if you refuse an auth request, but for the most common cases the Clipper should be functional.

Thanks again, @laurent!

GitHub

Release Support for Clipper Authorization · cweirup/JoplinSafariWebClipper

This release is to support the authentication of the API supporting the Clipper. The Clipper must now request authorization before it is able to access application data. This version should be used...

qykzoo53 · 2021-09-29T22:35:54.152Z

Hi David ...newbie wanting to sunset Evernote...

I am a
macOS Big Sur 11.6
Safari..v15.0

Have installed lates of both Clipper & Base... following this thread I have been confused as to why my clips dont seem to work...

The web services is running on port 41184
web clipper has been authorised and when clicking the J to clip it allows folder and tags to be entered.
goes to the ether and never seems to clip a webpage.
Joplin has all of the xx.md files for notes and tags .... so the macOS version loads folders etc and sync with dropbox...

I would like to help debug this.. please advise what steps you wish me to take etc...

David

qykzoo53 · 2021-09-29T22:51:36.145Z

Hi, This is David....

did some testing on this issue......

it works, but not as expected....

if a webpage is open already before Joplin is started on the device (both iPad and MacBook Pro) and Clipper is clicked then it will not work... ONLY NEW PAGES opened after the JOPLIN Server (device version) is running then the pages will be clipped...

Is there a way we can change this...error message or something?? I am willing to help with debug...

cweirup · 2021-10-14T02:06:25.892Z

David,

Yes, this is an issue with my Clipper. I'm not entirely sure why that happens. I suspect the problem is that extension is not able to access the full DOM in Safari if the page is already loaded, but I haven't confirmed that.

I mostly get around it by refreshing/reloading the page then using the Clipper again. Since it is then basically a "new page" the Clipper seems to work.

I'm somewhat booked at the moment, but if I get a chance to revisit this, I'll reach out for any help.

Chris