On Oct 11, 1:30 pm, Olivier Lance <[email protected]> wrote: > Frederick Cheung wrote: > > Does still happen in production mode? If it doesn't then you've got a > > class reloading issue. > > > Fred > > Oh okay, thanks! > That's actually part of a feature currently in development so I haven't > tried it in production yet. I'll try that and check that. >
Just setting cache_classes = true is enough for the purpose of this. You're probably hitting this because you're bypassing the rails code loading stuff. You might try using the constantize method provide by rails rather than rolling your own or (depending on the nature of the problem) you might want to mark some of the plugins you're using as reloadable (most issues like this occur when a non reloading plugin ends up hanging on to reloadable bits of your app) Fred > I've just found an old topic where you mentioned this too, and it seems > it's the exact same problem (http://www.ruby-forum.com/topic/209224)... > The ticket mentioned in this post by the OP was last updated one week > ago, and it seems nothing's been really settled yet... should I just set > cache_classes=true ? ... > > Olivier > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
