You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the GridFieldSortableRows::fixSortColumn() method is only called when getManipulatedData() is called, which means only when the grid is displayed.
But if an user creates a new record and gets redirected to the detail view of the created record, the getManipulatedData() method never gets called.
This leaves the sorting in an inconsistent state:
If the site uses caching or things like static publishing, it may happen, that in the time between the creation of a record and the view of its grid representation, the frontend renders the sorted list with the wrong order (because fixSortColumn has not been called until now) and caches this wrong state.
I don't know if there is a clean solution without modifying the SilverStripe core (eg. the GridFieldDetailForm)?
The text was updated successfully, but these errors were encountered:
Currently the
GridFieldSortableRows::fixSortColumn()
method is only called whengetManipulatedData()
is called, which means only when the grid is displayed.But if an user creates a new record and gets redirected to the detail view of the created record, the
getManipulatedData()
method never gets called.This leaves the sorting in an inconsistent state:
If the site uses caching or things like static publishing, it may happen, that in the time between the creation of a record and the view of its grid representation, the frontend renders the sorted list with the wrong order (because
fixSortColumn
has not been called until now) and caches this wrong state.I don't know if there is a clean solution without modifying the SilverStripe core (eg. the
GridFieldDetailForm
)?The text was updated successfully, but these errors were encountered: