Elasticsearch (fulltext search) wrong link in search results of tags

[Denis_Solovev]

Hello. I have assigned tags to some files. The elasticsearch full-text search index was also created. When I search, the full-text search finds these labels and each individual file corresponding to the label opens normally. However, if you select the option to open all files corresponding to the tag, then the tag folder is incorrectly opened.

Here’s what it means: if you open the labels manually in the files section, they look like https://site.com/apps/files/tags/1?dir=/1 and if you open it from the search results, then a folder (naturally empty) of the form is hidden https://site.com/apps/files/tags?dir=1. I suppose this may be related to some kind of rewrite rule, but I can’t figure out which one.

[XueSheng-NC]

@Denis_Solovev Can you provide a screenshot of the search result? Are you sure that fulltextsearch provider is used?
It would also be helpful if you would use the support template. You didn’t provide any information about your system and nextcloud version.

[Denis_Solovev]

Nextcloud Hub 9 (30.0.0)

Linux 6.8.0-45-generic x86_64

PHP 8.3.12

Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, cgi-fcgi, mysqlnd, PDO, xml, apcu, bcmath, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, imagick, imap, intl, ldap, exif, mysqli, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, readline, shmop, SimpleXML, smbclient, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, redis, libsmbclient, Zend OPcache

database
MariaDB 10.11.8

Active apps (not full list):
Full text search (30.0.0)
Full text search - Elasticsearch Platform (29.0.1)
Full text search - Files (30.0.0)
Full text search - Files - Tesseract OCR (27.0.0)

The settings are set in accordance with the recommendations of the documentation and the advice of the forum users. In general, I am satisfied with the installed bundle of the server, applications and its functionality

[XueSheng-NC]

Imho this has nothing to do with fulltextsearch. As your screenshot shows, you are looking at the search result of the tag provider.
I can reproduce the described behaviour.

You can double check whether there is an open issue on github. If not, create one.

[Denis_Solovev]

Yes, it looks like you’re right and the problem is with unified search and not full-text search. I’ll try to find something similar on github.