[Bug]: unified search filtering issues (space at end handling)
Nessuno ha ancora preso questa issue.
- Lingua principale
- PHP
- Stelle
- 36.9k
- Fork
- 5.2k
- Merge medio
- 2g 3h
- PR unite (30g)
- 713
Descrizione
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- Nextcloud Server is running on 64bit capable CPU, PHP and OS.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
- The search result varies depending on whether or not there is a space at the end of the search.
- This behavior is different depending on the app (in:files or in:mail)
- except error before: "date" does not work. or where to find the possible filters and instructions for use.
To clarify these points, the easiest way is to watch the short video here https://drive.google.com/file/d/1iOH51EFZBmparcEGdJga9GePBZLbD9oz/view
Steps to reproduce
- have 2 files named foo1.md and foo2.md
- have emails containing the word "foo"
- make a search with: foo (without space at this end)
- note the result
- add a space at the end of the search ("foo " without quotes) and note the difference in result
- add " in:files" (without spaces at the end) and note the result
- add a space to have " in:files " and note the result
- change "files" to "mail" and note the different behavior with "in:mail" and "in:mail"
- add: "before:2021" (with old mails dating from 2021 and 2020) and note the issue again
Expected behavior
always the same mode of operation. A space at the end of the entry must not influence the search result.
Installation method
Community Docker image
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
No response
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
Enabled:
- accessibility: 1.10.0
- activity: 2.16.0
- calendar: 3.4.2
- circles: 24.0.1
- cloud_federation_api: 1.7.0
- comments: 1.14.0
- contacts: 4.2.0
- contactsinteraction: 1.5.0
- dashboard: 7.4.0
- dav: 1.22.0
- deck: 1.7.1
- federatedfilesharing: 1.14.0
- federation: 1.14.0
- files: 1.19.0
- files_accesscontrol: 1.14.1
- files_pdfviewer: 2.5.0
- files_rightclick: 1.3.0
- files_sharing: 1.16.2
- files_trashbin: 1.14.0
- files_versions: 1.17.0
- files_videoplayer: 1.13.0
- firstrunwizard: 2.13.0
- groupfolders: 12.0.1
- impersonate: 1.11.0
- logreader: 2.9.0
- lookup_server_connector: 1.12.0
- mail: 1.13.8
- nextcloud_announcements: 1.13.0
- notifications: 2.12.0
- oauth2: 1.12.0
- password_policy: 1.14.0
- photos: 1.6.0
- privacy: 1.8.0
- provisioning_api: 1.14.0
- recommendations: 1.3.0
- serverinfo: 1.14.0
- settings: 1.6.0
- sharebymail: 1.14.0
- spreed: 14.0.4
- support: 1.7.0
- survey_client: 1.12.0
- systemtags: 1.14.0
- text: 3.5.1
- theming: 1.15.0
- twofactor_backupcodes: 1.13.0
- updatenotification: 1.14.0
- user_status: 1.4.0
- viewer: 1.8.0
- weather_status: 1.4.0
- workflowengine: 2.6.0
Disabled:
- admin_audit
- encryption
- files_external
- user_ldap
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Non viene indicato alcun file sorgente, test o punto di ingresso. Inizia riproducendo i passaggi con spazi finali, confrontando la ricerca unificata nei file e nella posta e il filtro before:2021. Il lavoro è completato quando gli spazi finali non modificano più i risultati e il comportamento è coerente tra le modalità di ricerca descritte.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- php, postgresql
- Ambito
- backend, search
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100