[Bug]: Fulltext search is not working correctly

[ostasevych]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

While trying to search something via client and pointing to the Full text search output section, clicking by any link I am lead to I am lead to the root folder instead of the document. So, in my case, when I am clicking on the file test.xlsx it it tries to open the file https://bcd.local/apps/files/%3Fdir=/Documents/&scrollto=test.xlsx.

However, If I search it via the webui it opens it correctly:

Steps to reproduce

1. Have installed fulltext plugins
2. Open desktop clients
3. Try to search for the file containing test inside of it
4. Click on the result test.xlsx
5. Observe that the file is not opened, but the root location

Expected behavior

When clicking on the results of the search, it should open the document or location of the document and point to it.

Which files are affected by this bug

fulltext search

Operating system

Windows

Which version of the operating system you are running.

Windows 10 x64

Package

Distro package manager

Nextcloud Server version

25.0.4

Nextcloud Desktop Client version

3.7.4

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

n/a

Additional info

n/a

[ostasevych]

Duplicate #5514

[claucambra]

Hi, we get these URLs from the Full Text Search component on the server side, so this bug originates from the server module. I opened an issue here: nextcloud/fulltextsearch#729

Feel free to add your report here too.

Since this is an upstream issue I will close the issue here