mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
Blank search results sometimes #603
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 @IAreKyleW00t on GitHub (Mar 15, 2018).
BookStack Version: 0.20.0 (Docker)
PHP Version: 7.1.10 (Apache, Docker)
MySQL Version: 10.2 (MariaDB, Docker)
I am running all of this with Docker using the
docker-compose.ymlfile from solidnerd/bookstack, only changing from mysql to mariadb.Expected Behavior
Search results. Either some or zero. Example when searching "ips"
Current Behavior
No results at all; blank search area. Example when searching "ip"
Window will quickly show some results, but then immediately change to being blank and the error is thrown.
Steps to Reproduce
Inconsistent... appears to happen with certain words, but acts differently for another user at my workplace. (eg: Searching "user" fails, but "user to ips" also fails)
Here is the error that gets thrown in the console when I perform a search that fails.
If I search for the word "user" it says this instead.
@alegiovannelli commented on GitHub (Mar 25, 2018):
I have the same issue with docker container, most searches return for half a second the results and then the blank page remains. In fact, research is unusable.
@ssddanbrown commented on GitHub (Mar 25, 2018):
@IAreKyleW00t Looking into this I think it may be a case of the search results clashing if containing vue syntax.
Do you have any text in your pages that matches
{{USER}}or{{NAME}}including the braces?@alegiovannelli commented on GitHub (Mar 25, 2018):
I think not have pages that matches {{USER}} or {{NAME}}.
The change made works correctly now in searches. Thank you for finding and fixing this annoying bug that did not allowed to properly use the search. Thank you, great project!
@ssddanbrown commented on GitHub (Mar 25, 2018):
@alegiovannelli Thanks for confirming.
I'll close this now that v0.20.1 has been released with the likely fix.
@IAreKyleW00t Feel free to request this to be re-opened if you don't find the issue fixed after updating.