if you use better_nested_set on a class that uses single table inheritance, then things don't work very well. this is because there are several instances of self.class in the better_nested_set code that can isolate those commands to only work with objects that are a subclass of the current object being used.
For example, let's say C < B < A < !ActiveRecord::Base
and A does "acts_as_nested_set"
then when you manipulate any object of B, self.class evaluates to B and rails adds type_conditions to every sql query, limiting the affected rows to only those objects which are of type B or C
To get around this, we need to save the class in which acts_as_nested_set is declared. I will be attaching a patch to do this
