[MGNLUI-3171] Sorting in content apps does not wipe the item cache Created: 24/Sep/14  Updated: 05/Dec/14  Resolved: 24/Sep/14

Status: Closed
Project: Magnolia UI
Component/s: content app
Affects Version/s: 5.2.2, 5.3.3
Fix Version/s: 5.2.10, 5.3.4

Type: Bug Priority: Critical
Reporter: Raju Subramaniam Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Scenario: list content records for page 2 is rendered from cache
Steps to reproduce:
1. Go to a content app list view (which has records > 60 atleast 120 would be fine)
2. Sort some column by ascending
3. Scroll the list beyond record count 60 (which is the default cache per page)
4. Now come back to the top of list
5. Sort the list again by the same column (now would move descending)
6. Scroll the list crossing item 60
7. The descending sort would appear fine until 60, beyond which there wont be a sort done.

Reason:
Enabled the DEBUG logs of AbstractJcrContainer and we do not see any request being triggered for page 2 meaning the content we see is actually from cache and not from the backend.



 Comments   
Comment by Daniel Lipp [ 24/Sep/14 ]

Effectively it's not only that the order is broken then - some items (the ones from the cache) might be listed twice then. Once from the cache and some pages later where the actually belong according to the new sorting.

Generated at Mon Feb 12 09:03:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.