-
Notifications
You must be signed in to change notification settings - Fork 804
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
Fix full-text search results not being opened in browser #5279
Conversation
Great! |
done 🙂 |
c9d7247
to
74fbfd8
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5279 +/- ##
=======================================
Coverage 57.58% 57.58%
=======================================
Files 139 139
Lines 17631 17631
=======================================
Hits 10153 10153
Misses 7478 7478
|
74fbfd8
to
04783b5
Compare
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
04783b5
to
4812989
Compare
AppImage file: nextcloud-PR-5279-481298997c276f858871c499bb5eed085474e7bf-x86_64.AppImage |
Kudos, SonarCloud Quality Gate passed! |
Sorry - but the fix does not work with Nextcloud Client 3.7.4. The format of the URL is wrong. What ever is called by the client, it will end up in a URL like this: However, this won't work: the directory is not |
The full-text search app provides incomplete resource URLs unlike all other search result apps, meaning our default behaviour for opening search results in the browser does not work
This PR adds a procedure to compensate for this
Closes #5113 and nextcloud/fulltextsearch#728