-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 10.10-HF45, 11.x, 2021.1
-
Fix Version/s: 10.10-HF49, 11.x, 2021.5
-
Component/s: Query & PageProvider
-
Release Notes Summary:Sort infos are taken into account in this order: first parameters, then quick filters, then defaults from page provider.
-
Tags:
-
Backlog priority:700
-
Sprint:nxplatform #36, nxplatform #37
-
Story Points:0
The original issue was reported as a Web UI issue but upon further investigation we suspect that it is caused by an inconsistency in the behaviour of the page provider when handling quick filters and sorting.
For example, using a fresh Nuxeo server:
- Create a Workspace document and inside it a few File documents with unordered file names (ex: "A", "C", "D", "B").
- Executing the default_search gets all the documents in the server.
- Using sortBy=dc:title and sortOrder=asc gets all the documents ordered by title.
- Using quickFilters=noFolder gets a filtered list of documents.
- It would be expected that adding sortBy and sortOrder to the previous search would result in a list of filtered and sorted results, but instead, the search results are exactly the same as the previous ones, completely unordered.
The goal is to be able to get the expected results when setting both quick filters and sorting params on a search.
- causes
-
NXP-31627 Fix error when applying multiple sorts on a JSF UI content view
- Resolved
- is duplicated by
-
NXP-28896 Sort info is ignored when using quickfilter with pageprovider
- Resolved
- is related to
-
NXP-28896 Sort info is ignored when using quickfilter with pageprovider
- Resolved
- Is referenced in