Rails 4 + ActiveAdmin compatibility (Migration error) about acts_as_relation HOT 12 CLOSED

Replace ActiveAdmin.routes(self) with below line in routes.rb

ActiveAdmin.routes(self) rescue ActiveAdmin::DatabaseHitDuringLoad

This fixes the issue.

from acts_as_relation.

I ended up converting the scope to a class method as suggested in #71 (comment), but only after trying to figure out what using a proc means for custom filters. @estelleqiu and @zpieslak are you referring to setting the collection option as in the following (see docs):

filter :author, collection: proc { Author.all }

from acts_as_relation.

I am getting the same error... and I although I have added the acts-as but it still cannot resolve the problem

from acts_as_relation.

@BattleBrisket comment on #59 is complete

from acts_as_relation.

I had the same issue on the newest master branch (activeadmin/activeadmin/commit/930d34cd224272687613dcf1db4cf5b1347f1098) of active_admin. The thing that caused it, was custom 'filter' options which were not wrapped in proc objects.

from acts_as_relation.

Filter part can be changed like this to avoid getting this kind of errors.

ActiveAdmin.register Table do

begin
filter: id
filter: name
rescue
p "msg"
end

end

from acts_as_relation.

I was also getting same error on rake db:migrate. I just commented that line and rake db:migrate runs perfectly and comment it after

from acts_as_relation.

Got the same error.
helped moving in models form scope :foo -> {bar} to def self.foo bar;end for table loading for avoid error

from acts_as_relation.

@r-a-o It works for me also. Thanks

from acts_as_relation.

I find proc{} is work for me.

from acts_as_relation.

rescue ActiveAdmin::DatabaseHitDuringLoad

It worked for me too!

from acts_as_relation.

#71 (comment)

Thank you!

from acts_as_relation.