Reloading problem in development

I just upgraded from 1.2.3 to 2.1.0 and now I'm seeing a model
reloading
problem in development. If I set config.cache_classes = true, the
problem goes away (which obviously isn't a very good workaround in
development).

Do you require models explicitly (this can confuse the dependencies
stuff). Do you use any plugins that hang on to model classes (or
instances of them) ?

Fred

Do you require models explicitly (this can confuse the dependencies
stuff).

No.

Do you use any plugins that hang on to model classes (or
instances of them) ?

Fred

I'm using several external plugins. How would I find out? Did the
behavior for how this is handled change between 1.x and 2.x?

Regards,
Robbie
http://statsheet.com

Do you require models explicitly (this can confuse the dependencies
stuff).

No.

Do you use any plugins that hang on to model classes (or
instances of them) ?

Fred

I'm using several external plugins. How would I find out? Did the
behavior for how this is handled change between 1.x and 2.x?

Plugins used to be reloaded with each request by default, but they
aren't anymore. I can't remember when this change happened to be
honest. I have a feeling it was in 1.2 but it could have been 2.0
I've got some info on making plugins be reloaded on each request here http://www.spacevatican.org/2008/5/28/reload-me-reload-me-not
, you could try that out to exclude it as a source of problems
(alternatively examine Dependencies.load_once_paths in your 1.2 app:
if it looks the same there as in 2.0 then that's probably not the
problem)

Fred