-
Type: Bug Report
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.3.0-B1
-
Component/s: Data Management
-
Labels:
-
Change Log Group:Fixed
-
Change Log Message:The sorting in grids for user wasn't changed, when website default sorting for that grid was changed.
-
Story Points:1
-
Sprint:In-Portal's First Sprint, In-Portal's 2nd Sprint, In-Portal's 3rd Sprint, In-Portal's 4th Sprint
-
Copy Issue Key:
-
Patch Instructions:
-
Commit Revision:16,155
Plan:
- create getSortingPrefix($system_setting) method in ConfigurationEventHandler
- new method would inspect ConfigMapping setting of each unit configs, which prefix is mentioned in Modules database table (replace "adm" with "c" and skip "In-Portal" module)
- if system setting name, that is given to the method is matching DefaultSorting1Field or DefaultSorting2Field key values of ConfigMapping array, then return unit config prefix
- if no match found then return false
- call new method from ConfigurationEventHandler::OnAfterItemUpdate only in case if VariableValue field value was changed
- if new method returns unit config prefix, then remove any stored sorting, that might be associated with it from PersistentSessionData table
- is backported by
-
INP-1615 Reset cached sorting on sorting configuration change
- Closed
- implemented in
-
[Request, 37 lines] D10 INP-1315 - Reset cached sorting on sorting configuration change
- mentioned in
-
Wiki Page Loading...