Accessing node's path in before_save or after_save about ancestry HOT 4 CLOSED

Just discovered the unscoped method and I've worked out a solution to the issue, but please let me know if I am missing something about the functionality of ancestry or if there is a better way of doing it.

Again, thanks for developing this library, it's solid.

• Nick

from ancestry.

Please investigate any incompatibilities with friendly id and describe them in detail. Where possible, please also suggest changes to resolve any issues. I really don't have time to do that myself.

Friendly id is an important gem and I would be glad to make any specific changes to resolve any incompatibilities between it and ancestry.

Additionally, you might approach rolftimmermans. He has commit access and might be willing to investigate the problem.

from ancestry.

@stefankroes I'm running into the same issue with ancestry 2.1.0 , Rails 4.2.4 with a Postgres DB.

Can you please re-open this issue, or comment what might be causing this?

class Node < ActiveRecord::Base
  has_ancestry(:orphan_strategy => :adopt)
  # has a name and a slug string attribute, the slug is supposed the be the path's names concatenated

  after_save :generate_slug

  # 
  def generate_slug
    puts "OBJECT: #{self.name} ; PATH IS: #{self.path.pluck(:name).inspect}"
    self.update_column(:slug , self.path.each_with_object([]) {|x,a| a << x.name}.join('/') )
  end
end

Objects are created in this fashion:

root = Node.create(:name => 'root')
child1 = root.children.create(:name => 'child1')
OBJECT: child1 ; PATH IS: ["child1"]
child1.slug
  => 'child1'    # oops!
child1.save
OBJECT: child1 ; PATH IS: ["root","child1"]
child1.slug
  => 'root/child1'

self.ancestors does not appear to be set/valid during the execution of the after_save hook.

Looks like this might be an issue with multiple callbacks being registered.

from ancestry.

I really didn't like the way the ids were being updated before. Hoping the newer code will work much better for everyone

from ancestry.