updating rails_admin broke config.included_models?

[shawndrost]

Updating from the rails-3.0 branch recently seems to have broken my
list of included models. A random selection of my app's models are
now appearing in the menu. Can't find anything in the docs about
changes to this part of the config. Anyone know of a recent change
that would cause this?

[Gady]

I'm in a similar situation.
I specified
config.included_models = ["Model1", "Model2", "Model3"]
config.excluded_models << "Model4"
but I still get random models missing in development, and constantly
in production (heroku)
In development the missing models appears when refreshing the page.

I tried debugging in development and ispected
RailsAdmin.config(Model1).visible?
In the first request it was false and the second true

Any advice ?

Thanks
Gady

[Gady]

It seems that adding the following code to the models solves the
symptom

rails_admin do
visible { true }
end

[Gady]

But now I get an error when clicking the model

[shawndrost]

Gady (and others) -- I'm pretty sure this is related to the
deprecation of the system to do configuration with
ActiveRecord::Base#rails_admin. Personally, I'm going to see if I
still need that -- iirc, there was a bug preventing me from using the
initializer.

[Gady]

Where can I read more about the deprecation ?
the readme still instructs to use that method.
what is the alternative?

[shawndrost]

Wow. Yeah, you're right... the master branch readme has the below
notice, but not the 3.0 branch, since it's not being maintained any
more. (The 3.0 readme doesn't mention that it's not maintained
either.) Honestly, I'd recommend against using rails_admin unless
you're on master. Even then, you should expect to need to learn the
internals to debug stuff... this is alpha software. (No offense,
maintainers! It's rad, thanks for your work :) )

Anyway, the alternative is a block in an initializer like this:

RailsAdmin.config do |config|
...
end

------

Configuration with ActiveRecord::Base#rails_admin is not recommended
anymore and should be considered as expermimental (development) until
further notice. Unfortunately, implementation of this feature is
thougher than imagined. Any help is welcome, as usual. Please remove
any rails_admin configuration from your ActiveRecord model and put it
inside an initializer (as shown in this documentation now).

[Gady]

Thanks!
it solved my problem

[msp]

Seems to have settled things down for me on the rails-3.0 branch.
Thanks!