Make sure the "view_config" data used for saved searches/views always includes the "sort" key instead of omitting the key when there is no active sort key or when multisort is enabled. Saving "sort" as {} in these cases makes these saved searches load correctly -- omitting the key was causing a default sort key to be applied, corrupting the view.
Make sure the "view_config" data used for saved searches/views always includes the "sort" key instead of omitting the key when there is no active sort key or when multisort is enabled. Saving "sort" as {} in these cases makes these saved searches load correctly -- omitting the key was causing a default sort key to be applied, corrupting the view.
This fixes issue #186.