Finally, I found the error. As usual, it was very simple, but I have not seen it.
As I use Joplin in a new laptop with a new Joplin installation even Joplin have a token available, it does not have enable the clipper service for port 41184. After enabling it, the add.on works as was working in other devices. Thanks for assistant and sorry I cannot see this simple issue before.
2 Likes
Sorry, I never really thought about this, I almost always have this option enabled, maybe I should add some more clear error messages or something.
If the joplin webclipper service is not enabled, will such an error message pop up help? @Eduardo
Release 0.6.1, ref: Release joplin-search-integration@0.6.1 · rxliuli/joplin-utils · GitHub
2 Likes
Sure, I believe in the future if I make the same mistake this will be useful to remember us this issue.
The problem was that in general in previous new Joplin installation in new devices, first I updated the web clipper and later the Joplin search integration add-on. In this process you always enable first the port, but In this case, I altered the steps, I wanted to use first this add.on before the web clipper. Thanks a lot for your support.
1 Like
First of all, thank you very much for such a great idea and its realisation.
Unfortunately, I am facing a deal-breaking issue. While my Joplin is running, everything is OK and running perfectly. As soon as I close Joplin, or do not start it at all, every single search engine attempt pops up the error message posted by rxliuli about two posts back.
The plugin thinks that the webclipper service is not enabled, but the real reason it could not connect is that Joplin is (intentionally) not running at all.
I do not know if I am doing something wrong. There are times when I do not want to run Joplin but I still want to use Firefox to "google" things. Is there a way to fix this behaviour? I have not tested with the Chrome browser and plugin combination.
I didn't realize this, maybe this error should be shown in the search results for joplin notes on the right, rather than a blocking prompt popping up?
Oh, I have never seen such a quick response to my report, thank you very much!
The solution you proposed would be definitely way better. If I can also bring two more ideas to your consideration, these would be:
-
Add a checkbox to voluntarily disable the error message completely. If the browser is not running and the warning was disabled in the configuration, the search page should stay completely untouched by the plugin. No "Joplin search notes" block at all.
-
Let us modify or even style the "Joplin search notes" title and the whole block.
I see a big potential in this plugin. Bringing the search into one place is a really great idea. Browsers are our modern information hubs so it perfectly makes sense. And we have got much more here. The possibility to immediately start browsing the notes right from from the browser, oh my... I haven't even dreamed of such a functionality.
Add a checkbox to voluntarily disable the error message completely. If the browser is not running and the warning was disabled in the configuration, the search page should stay completely untouched by the plugin. No "Joplin search notes" block at all.
It sounds like just adding an option should be simple, but maybe later, showing a non-blocking error doesn't feel like it will have much impact.
Let us modify or even style the "Joplin search notes" title and the whole block.
I'm not sure about that, maybe some kind of custom css style is supported.
My reasoning for the ability to disable the error message completely is that in the case of proper setup, it is not an error situation in the first place. In fact, there are probably users, like me, that run a browser almost all the time, but Joplin only like 20% of the time. Looking at an error message whenever I use google is not optimal. On the other hand, it is "non-blocking", just a cosmetic thing.
It can be probably styled by modifying the browser's default stylesheet, etc. I will look into it.
These were just my little ideas. I will welcome whatever you do to stop the popup, of course. Thank you once more.
Release 0.6.2, refactored using preact, added better error handling, ref: Joplin-search-integration release 0.2.0 - #66 by CyberDave
2 Likes
When I was writing the initial post, I thought that it could be improved ... maybe this year? I wasn't really expecting a light-fast solution. 
Thank you very much.
1 Like
Release 0.6.3, fixed the issue where Brave search no longer works. Reference: [Bug]: Search integration with Brave using search.brave.com no longer working · Issue #92 · rxliuli/joplin-utils · GitHub
1 Like
Release 0.7.0.
- feat: Automatic word segmentation search. close https://github.com/rxliuli/joplin-utils/issues/94
- fix: Fix the issue where Baidu search results were not displayed correctly. close https://github.com/rxliuli/joplin-utils/issues/97
ref: Release joplin-search-integration@0.7.0 · rxliuli/joplin-utils · GitHub
1 Like
Hello. Any chance for you to add support to the Kagi search engine? 
I really like this plugin, thank you for it.
(Also, perhaps your description is out of date? It mentions "Google/Bing/Baidu", but it also works on DDG.)
This appears to be a private search engine, so PRs are welcome.
Yes, it does indeed need to update the instructions.
Yeah, there's a 100 queries trial, then paid only.
Okay, thanks for the info, then.
Released 0.8.0
Major Changes
- Refactored the entire plugin using wxt (Web Extension Toolkit)
- This significant architectural change aims to improve the plugin's maintainability, and extensibility
Notes
- Due to the extensive refactoring, users are advised to report any new issues or unexpected behaviors
- No changes to existing functionality are expected, but please verify your workflow after updating
1 Like
Released 0.8.2
- fix: Resolved a CSS conflict between the search box and plugin CSS when using Bing search
- style: Optimize the style of the note viewing page
- fix: Fixed the issue of abnormal text size when searching on Baidu
- fix: Fixed the issue of incorrect webpage theme detection when using Baidu search
Before
After
Released v0.9.0.
- feat: support search joplin notes on search bar
- feat: optimize ui
Demo Video: https://www.youtube.com/watch?v=4M0yNdGQ65c
GitHub release: Release joplin-search-integration@0.9.0 · rxliuli/joplin-utils · GitHub
1 Like
Release v0.10.2, supports mathematical expressions in Joplin, thanks to the PR submitted by @jannikgohr.
For example
$$f'_{3}(x)=4$$
$x^2$
Before
After
1 Like
Released v0.10.3, add GitHub flavored markdown syntax. Thank you @jannikgohr for submitting the PR.
New Syntax supports:
- autolink literals
- footnotes
- strikethrough
- tables
- tasklists
2 Likes