Fixed
Details
Priority
MinorAssignee
AlexAlexReporter
AlexAlexDeveloper
Erik S.Erik S.Reviewer
AlexAlexChange Log Group
FixedChange Log Message
The sorting in grids for user wasn't changed, when website default sorting for that grid was changed.Patch Instructions
Patches must be submitted through Phabricator.
To submit patch via Command Line use Patches Workflow (via Arcanist) tutorial.
To submit patch via Web Interface use Patches Workflow (via Web Interface) tutorial.
Commit Revision
16,155Story Points
1Sprint
NoneFix versions
Details
Details
Priority
Assignee
Alex
AlexReporter
Alex
AlexDeveloper
Erik S.
Erik S.Reviewer
Alex
AlexChange Log Group
Fixed
Change Log Message
The sorting in grids for user wasn't changed, when website default sorting for that grid was changed.
Patch Instructions
Patches must be submitted through Phabricator.
To submit patch via Command Line use Patches Workflow (via Arcanist) tutorial.
To submit patch via Web Interface use Patches Workflow (via Web Interface) tutorial.
Commit Revision
16,155
Story Points
1
Sprint
None
Fix versions
Created August 29, 2013 at 1:58 PM
Updated December 29, 2024 at 8:56 PM
Resolved March 21, 2015 at 6:25 PM
Plan:
create
getSortingPrefix($system_setting)
method in ConfigurationEventHandlernew method would inspect
ConfigMapping
setting of each unit configs, which prefix is mentioned inModules
database table (replace "adm" with "c" and skip "In-Portal" module)if system setting name, that is given to the method is matching
DefaultSorting1Field
orDefaultSorting2Field
key values ofConfigMapping
array, then return unit config prefixif no match found then return false
call new method from ConfigurationEventHandler::OnAfterItemUpdate only in case if
VariableValue
field value was changedif new method returns unit config prefix, then remove any stored sorting, that might be associated with it from
PersistentSessionData
table