position: 0 now makes model pushed to top?

[USvER]

After update i got weird issues with sorting.
After investigation i have found that new items got pushed to top, and not to bottom as described...
So model with position: 0 results into position: 1.
Is this new behaviour, or i have some issues in my code? Maybe with scope(i have scope on multiple fields) but how it relates to this?

[USvER]

For now, fixed my issue with move_to_bottom function in the controller.
But this is really no cool!

[USvER]

Any suggestions to set "new items at the bottom of the list" as a default behaviour?
It's so frustrating when i have this sorting issue poping here and there every day...

[swanandp]

Let me look at this. What is your gem version?
On 17-Mar-2014 4:45 am, "USvER" notifications@github.com wrote:

Any suggestions to set "new items at the bottom of the list" as a default
behaviour?
It's so frustrating when i have this sorting issue poping here and there
every day...

Reply to this email directly or view it on GitHubhttps://github.com//issues/110#issuecomment-37774865
.

[USvER]

• acts_as_list (0.4.0)
• rails (4.0.3)
• ruby (2.1.1)

[neutralino1]

Is this related to #109 ?

[nickpearson]

I had this issue as well, and I fixed it (for my use case, at least) with the following mixin:

module ActsAsListFix
  # clear the default position value, because having it present
  # causes acts_as_list to insert the record at that position
  def self.included(base)
    base.after_initialize do
      if new_record? && (pos = send(position_column)) &&
         pos == self.class.column_defaults[position_column]
        send("#{position_column}=", nil)
      end
    end
  end
end

Just place the acts_as_list_fix.rb file in an auto-loaded path (like <Rails.root>/lib) and include it with any acts_as_list declarations, e.g.:

class Floor < ActiveRecord::Base
  acts_as_list scope: :building_id
  include ActsAsListFix
end

This is an update to my solution to this problem from a few years ago. That wasn't working for me anymore after upgrading to Rails 4.1 and Ruby 2.1, but this new one is working for me so far.

Hopefully this behavior of ignoring the default value of the position database field can be worked into the acts_as_list gem itself, and if not, I at least hope it helps someone else who has trouble with this. (Thanks @swanandp for maintaining this gem!)

[brendon]

Is this still a problem? Instead of a monkey patch it'd be good if we could fix it. New items should go at the bottom of the list by default. Have you tried removing the default value from that column?

[USvER]

Sorry, i'm not having access to that project anymore.

[brendon]

Ok, I'll close this. If someone can reproduce this with a failing test then we'll look into it.