Until now the column with the handles starting the reorder action always
appeared as the first column at the left of the GridField. As a followup to
the previous change's for extra sort fields, this change allows specifying
a different column index. This way you can eg. move the handles behind a
category column whose sorting will always be enforced, thus giving the user
visual support in understanding the limits of drag-n-drop reordering.
This change allows for the specification of extra sort fields that are to be
applied before the user-defined sort field's order. This is useful in
scenarios where a GridField is used with one or more "fixed" columns which
eg. categorize the entries and whose order is important but the user should
still be allowed to modify the order within a category.
This change affects the PHP code only, therefore the Javascript code will
still let the user drag rows into foreign "categories". However, after
dropping it the GridField will reload and the extra sort order will be
enforced again.
* 'ManyManyRelationOrdering' of git://github.com/dnadesign/silverstripe-gridfieldextensions:
fixed many many ordering so that other many many lists with the same relation aren't affected
If it's a many many relationship, then it should be based on View not edit, as the sort field will be on the relationship using many_many_extraFields. Plus the view permission allows the user to create a many relationship, so it should allow editing of the relationship.
