Detailed search
added in v3
Jack
To further highlight pages where keywords are found or with sub search results for hits of the keyword searched.
Photo Viewer
View photos in a modal
Nicolas Giard
marked this post as
added in v3
Added in v3.
j
joseph
J'ai trouver une solution de contournement simple pour la recherche Postgres en modifiant la query dans son engine.js
let qry = `
SELECT id, path, locale, title, ts_headline(?, content, to_tsquery(?,?)) AS description
FROM "pagesVector", to_tsquery(?,?) query
WHERE (query @@ "tokens" OR path ILIKE ?)
`
let qryEnd = `ORDER BY ts_rank(tokens, query) DESC`
let qryParams = [this.config.dictLanguage,this.config.dictLanguage,tsquery(q),this.config.dictLanguage, tsquery(q), `%${q.toLowerCase()}%`]
et en inversant path et description dans l'asset ui-extra.js
s("v-list-item-content", [s("v-list-item-title", {
domProps: {
textContent: e._s(t.title)}
}), s("v-list-item-subtitle", {
staticClass: "caption",
domProps: {
textContent: e._s(t.path)}
}), s("div", {
staticClass: "caption grey--text",
domProps: {
innerHTML: e._s(t.description)}
})], 1), s("v-list-item-action", [s("v-chip", {
attrs: {
label: "",
outlined: ""}
Photo Viewer
View photos in a modal
D
David Simmons
I think it should pretty easy to add the search term fragments with highlighted locations function in SqLite using the code I talk about below as a basis.
It took me about 4 hours to amend the Basic Data search to have Full Text searching with SqLite FTS5 engine. That intrinsic SqLite feature also provides term-location hiliting which would give you today what is being asked for. It also has many other rich searching features.
Here is the basic "thank you" code link for the great work on Wiki.JS and its clean-design.
I have built a simple variant of the basic data engine that provides FULL TEXT search using SqLite's intrinsic FTS5 full text engine with bm25 ordering.
THIS WORKS now in V2 as a drop-in on the path:
server/modules/search/edb
Martin
David Simmons: Great job, this adds the basic highlight feature for search results I wanted until v3 is released! As a small addition to your install instruction. I had to place the code for search module into
server/modules/search/EDB
instead of server/modules/search/edb
otherwise I would get a Cannot find module '../modules/search/EDB/engine'
error.D
David Simmons
Martin: Good catch/note 🙇🏻♂️.
I use a slightly different naming than that packaging, and I run it on Win11 ｢ntfs case-insensitive｣ and use Bridge mode WSL2 w/Ubuntu and container services. I tried to share the bare-bones implementation.
Using SqLite has incredible advantages for me in adding tooling, management and other features. I.e., I have additional modifications and plugins I've integrated or created for my personal use bridging it with systems and tools I have. I have NO intention of migrating to V3 if it doesn't support SqLite.
Nicolas Giard
marked this post as
added in v3
Added in v3.
Chomper
Nicolas Giard: neglect V2 long enough and people are going to move to other alternatives. This is an issue
now
, in the only version we have available.Nicolas Giard
Chomper: I'm sorry, are you a dev working for absolutely free, exclusively on his spare time, on an open source project? If you want something "now", because you're somehow entitled to it, then do feel free to use an alternative or paid product / service. This ain't it.
Chomper
Nicolas Giard: I am in fact, my project has both a software and hardware component which I develop solo in my spare time. That's not the point. Nor have I said "I want this now". My point is that V2 is
currently
missing essential functionality, and all suggestions are being implemented in a V3 product that seemingly never sees the light of day. Just look at all the "Awaiting V3" tags. How many years has it been?I've never understood the victim mentality of many open-source developers. When I put my product "out there", I'm fully aware that I'm going to have to continue developing it based on feedback from my users. My users
are
entitled to that, that's the role I've taken on my developing this product. I'm not going to take their feedback and implement it in a different product they don't have access to. That just asking for my users to leave. Especially if I'm asking for donations.You're surely not oblivious to the fact that people are going to get frustrated when basic functionality, voted on by hundreds of people, basically never happens?
Nicolas Giard
Chomper: That's a lot of nonsense. What you consider "essential" is simply not important for other users. Having highlighted text in search results is a nice to have, not an essential feature. It doesn't prevent you from using the app effectively in the slightest. When some people complain that their feature is the most important thing in the world, when it's completely unimportant to most users, it gets irritating.
You seem to imply that v3 is a different product, when it's an update to the exact same app. Some highly requested features (like multi-sites and notifications) are simply not possible with the current v2 architecture, hence the major v3 update to address these core shortcomings. I can't work on adding new features to v2 while also somehow having time to work on v3. It just doesn't make any sense. By putting time on v2, v3 would get delayed even further and more people would complain. Therefore, v2 is being maintained for security / breaking bugs while new features are added to v3 (which is public, accessible to anyone, with instructions on how to run it, unlike what you said which is plain wrong).
I completely disagree with how you think open source development works. Users are not entitled to anything. They can submit feedback and contribute PRs to help but to expect the maintainer to address all your requests and work on what
you
decided was important is simply wrong. I work on what is best for the project as a whole, even if that might frustrate some users waiting on a particular feature. As for donations, they are a way to say thank you, not an expectation of any sort from the maintainer.Is it taking a long time? Yes. But that's how it is, because in the end, it will result in a better product.
Nicolas Giard
Merged in a post:
Add search result extract like mkdocs material
Thomas Pozzo di Borgo
Hello,
Having a seach extract like mkdocs material (run a search for the word "install" here please: https://squidfunk.github.io/mkdocs-material/) would be a big plus for usability to seach information on the wiki.
The user could better choose the page from the result this way. It would be major improvement for the wiki I think, as search is the main used tools to find information and central to the wiki.
Thanks.
Photo Viewer
View photos in a modal
Nicolas Giard
Merged in a post:
Show a context in search window
Ira Milcsevics
For our company it is important that when we search for some i formation we can see in what context it is included to a page. Could you, please, improve your search engine, that in an opened window with results we also could see a some pease of sentence with searched word/ phrase.
Nicolas Giard
marked this post as
in progress
M
Marius
It would be highly appreciated to have highlighted the words found in the pages from search results and when opening the page to still keep highlight the words found
Nicolas Giard
Merged in a post:
Advanced search results
Анастасия Дзюба
Display in the search results not only the title of the article, but also the searched phrases
Nicolas Giard
marked this post as
planned
diankov
This is a basic functionality and extremely needed. Without it, the full text search is pretty much useless and we have to use much more tags. Some people can't work with tags.
Load More
→