mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-06 09:09:38 +03:00
Search does not find parts of words #5316
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Danke23 on GitHub (Jun 18, 2025).
Describe the Bug
If I search for “onboard”, the search finds the word “onboard” - if I search for ‘board’ or “boarding”, the search no longer finds anything.
Steps to Reproduce
Expected Behaviour
I would like the search to find boarding in the word onboarding.
Screenshots or Additional Context
Browser Details
No response
Exact BookStack Version
v25.05.1
@virtadpt commented on GitHub (Jun 19, 2025):
I've been seeing this problem for a while, so confirmed over here.
@cevinov commented on GitHub (Jun 19, 2025):
Yes please fix this, and also need to add feature where tag doesnt disappear after saving page draft
@ssddanbrown commented on GitHub (Jun 19, 2025):
This is known and intended. Search for standard terms is performed via a prefix match against indexed search terms (to make use of database indexes). A exact search term (
"in quotes") will perform a slower exact match across the whole range of content text.@virtadpt commented on GitHub (Jun 20, 2025):
@ssddanbrown Okay, that makes sense. thank you.
@Danke23 commented on GitHub (Jun 25, 2025):
Okay, thank you very much for your answer. That's how it works.
However, this is somewhat impractical. I think it would make more sense to make this search for “exact search” the default search.
The naming is also confusing: For me, an exact search is the exact word and a normal search is a word snippet too.
@ssddanbrown commented on GitHub (Jun 25, 2025):
The reason we do a prefix-match by default is because then we can actually use database indexes, and therefore search remains fairly performant, otherwise the exact search (or inner partial match) does not use indexes which can be quite intensive since it requires a full scan/search across content, and this scales linearly with content size, so is something I'd want to make default.