Hi Hayes This was done because that check used to be in a different spot, and was fired as soon as Rails was initialised. For 2.1 with classes cached, Rails wouldn't load classes until you needed them, but then would not forget them. Rails 2.2 and later loads all classes at the very start.
Still, I've realised that method is causing a few issues, so I've removed it, and now add_indexed_models is called every time a new context is created. Give 1.3.14 a spin, that should be better. -- Pat On 20/12/2009, at 2:29 PM, Hayes Davis wrote: > Hi, > > I'm running TS 1.3.13 as a Rails plugin in Rails 2.1.0. When > cache_classes is true in my environment, I get the same "called > local_options on nil" issue as described in this thread: > http://groups.google.com/group/thinking-sphinx/browse_thread/thread/c1e550f332c08dbe/7e425be13397e3a7 > > I've tracked this down to the cached? method in context.rb. It has the > following check: > Rails::VERSION::STRING.to_f > 2.1 > > Is there any reason that should be > instead of >= ? Since I'm on > Rails 2.1, that check is failing and add_indexed_models never gets > called when prepare is called on ThinkingSphinx::Context. I changed it > to be >= and everything seems to work fine. Let me know if there is a > reason Rails 2.1 should be excluded or if there's something else I'm > missing. > > Thanks. > > Hayes > > -- > > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" 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/thinking-sphinx?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" 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/thinking-sphinx?hl=en.
