Fantastic investigation, thanks for the fix Bryan, just updated the docs: http://freelancing-god.github.com/ts/en/common_issues.html#no-fields
-- Pat On 01/05/2012, at 5:55 AM, Evgeniy Solovyov wrote: > Thank you! > > Realy strange solution but works. > To sum up, to solve this issue just place: > gem 'blankslate' > somewhere at the top of your Gemfile > > понедельник, 30 апреля 2012 г., 20:02:55 UTC+3 пользователь mrpunkin написал: > Mine didn't either, it was actually packaged in as a class of another Gem I > was using, not a dependency for that gem. I'd try manually installing > BlankSlate higher up your Gemfile just to see if it can help. If not, I won't > be much help, sorry. > > > On Apr 30, 2012, at 10:01 AM, Evgeniy Solovyov wrote: > >> unfortunately my Gemfile.lock doesn't mention BlankSlate :( >> >> понедельник, 30 апреля 2012 г., 18:53:02 UTC+3 пользователь mrpunkin написал: >> I was able to figure out my problem actually. I had another gem / dependency >> that was requiring the use of BlankSlate and actually packaged it into their >> own Gem, but a VERY old version of it. By requiring BlankSlate in my Gemfile >> before this other gem I was able to get TS working as expected. >> >> >> >> On Monday, April 30, 2012 8:31:47 AM UTC-7, Evgeniy Solovyov wrote: >> Have just found that while i have define_index block but in >> .../gems/thinking-sphinx-2.0.11/lib/thinking_sphinx/index/builder.rb:32 >> where you may see self.instance_eval &block it returns >> #<ThinkingSphinx::Index::FauxColumn:0x007ffcb6063aa0> >> @name = instance_eval >> stack =[] >> >> понедельник, 30 апреля 2012 г., 16:10:26 UTC+3 пользователь Evgeniy Solovyov >> написал: >> In fact i have the same problem after mingration from ruby 1.8.7 to 1.9.3. >> May be i missed something but may be somebody can give me i hint. Rails >> 3.1.4, ts 2.0.11 >> >> четверг, 1 марта 2012 г., 1:50:06 UTC+2 пользователь pat написал: >> >> Sorry, short of having access to the code and reproducing it locally, I've >> no idea what the cause is. >> -- >> Pat >> >> On 29/02/2012, at 5:48 AM, mrpunkin wrote: >> >> > Any ideas what could be causing this? This is currently stopping us from >> > finishing our upgrade to Rails 3, due to our dependency on TS for search. >> > >> > On Monday, February 27, 2012 8:43:22 AM UTC-8, mrpunkin wrote: >> > TS has builder (>= 2.1.2) but the rest of the lock file has builder (~> >> > 3.0.0). No blankslate gem at all. >> > >> > On Saturday, February 25, 2012 3:21:47 AM UTC-8, pat wrote: >> > >> > Hi Bryan >> > I'm at a bit of a loss why this is happening... I've seen this in the >> > past, but it's with pre Rails 3.1. Can you just confirm which version of >> > builder is in your Gemfile.lock file? Also, is the blankslate gem in your >> > Gemfile.lock file? >> > >> > -- >> > Pat >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > On Monday, February 27, 2012 8:43:22 AM UTC-8, mrpunkin wrote: >> > TS has builder (>= 2.1.2) but the rest of the lock file has builder (~> >> > 3.0.0). No blankslate gem at all. >> > >> > On Saturday, February 25, 2012 3:21:47 AM UTC-8, pat wrote: >> > >> > Hi Bryan >> > I'm at a bit of a loss why this is happening... I've seen this in the >> > past, but it's with pre Rails 3.1. Can you just confirm which version of >> > builder is in your Gemfile.lock file? Also, is the blankslate gem in your >> > Gemfile.lock file? >> > >> > -- >> > Pat >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > On Monday, February 27, 2012 8:43:22 AM UTC-8, mrpunkin wrote: >> > TS has builder (>= 2.1.2) but the rest of the lock file has builder (~> >> > 3.0.0). No blankslate gem at all. >> > >> > On Saturday, February 25, 2012 3:21:47 AM UTC-8, pat wrote: >> > >> > Hi Bryan >> > I'm at a bit of a loss why this is happening... I've seen this in the >> > past, but it's with pre Rails 3.1. Can you just confirm which version of >> > builder is in your Gemfile.lock file? Also, is the blankslate gem in your >> > Gemfile.lock file? >> > >> > -- >> > Pat >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Thinking Sphinx" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/thinking-sphinx/-/Pxi2ZpkjhtsJ. >> > 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 view this discussion on the web visit >> https://groups.google.com/d/msg/thinking-sphinx/-/53mXSnYZkm8J. >> 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 view this discussion on the web visit > https://groups.google.com/d/msg/thinking-sphinx/-/pWkiZjJbYZkJ. > 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.
