Closed pond closed 11 years ago
This can be hard to duplicate but the direct setting of list position looks likely to be to blame; current acts_as_list implementations may attempt to shuffle the list when this is done. The documentation says that the "set_list_position" method does not cause the list to be reordered so in the context of setting positions on all rows due to a sort request, this should be the correct call to use.
Believed to be fixed by cef07e72de78052a2f9634f3080ed6d339c4d4c5.
See issue #14. This intentional duplicate tracks the resolution of the "need to sort rows twice" part of that report.