-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search from CLI doesn't work #72
Comments
I have the same issue
What can I do to identify the cause of the error? |
i have the same Problem. In Connection.php line 632: {"error":{"root_cause":[{"type":"x_content_parse_exception","reason":"[1:63] [bool] failed to parse field [should]"}],"type":"x_content_parse_exception","reason":"[1:63] [bool] failed to parse field [must]" |
I also get the same error in Nextcloud 20 with all fultext apps on version 2.0. |
This commit fixes issue nextcloud#72
Fix for unhandled exception, when SearchService is being used by occ fulltextsearch:search command. We ensure, that userId member of SearchService is set properly. This commit fixes issue nextcloud#72
Fix for unhandled exception, when SearchService is being used by occ fulltextsearch:search command. We ensure, that userId member of SearchService is set properly. This commit fixes issue nextcloud#72 Signed-off-by: Maciek Barczak <[email protected]>
Fix for #72 - occ fulltextsearch:search throws unhandled exception
Fix for unhandled exception, when SearchService is being used by occ fulltextsearch:search command. We ensure, that userId member of SearchService is set properly. This commit fixes issue #72 Signed-off-by: Maciek Barczak <[email protected]>
[stable21] Fix for #72 - occ fulltextsearch:search throws unhandled exception
Can you please confirm this still hapens with both latest versions of Nexcloud and |
Fixed in #104 |
Example:
App versions:
The text was updated successfully, but these errors were encountered: