Binarylogic Searchlogic

Comments and changes to this ticket

• 

  Ben Johnson February 8th, 2009 @ 02:38 PM

  • State changed from “new” to “open”

  That is really strange. I have to say, lately most of the errors and problems I have been getting have to deal with the rails caching. They have changed that so much, which is good, but its been causing a lot of problems. Did you run rake rails:update when you updated rails, if you ever did. It really sounds like a classic caching issue.

• You flagged this item as spam.
  

  Lucas Efe February 8th, 2009 @ 02:53 PM

  In a moment I was trying to make it work work with rails 2.3. I runed rake rails:update and then I removed vendor/rails and stayed with rails2.2.2, but maybe some of the app structure remain updated. How can I know that? Which files do I have to check to know that?

• 

  Ben Johnson February 8th, 2009 @ 02:56 PM

  Honestly, the rails caching is such a mess and changes so much I am not current with how it works. But I believe your environment/* files contains all of the caching settings. Try running rake rails:update again, I bet 2.2.2 will kick in and change things back.

• You flagged this item as spam.
  

  Lucas Efe February 8th, 2009 @ 06:35 PM

  Well, I did that, and now I have a new problem (the old one is still present).

  NoMethodError in Ingresos#index

  Showing app/views/ingresos/_search.html.haml where line #1 raised:

  undefined method searchlogic_base64_value' for #<ActionView::Base:0x26e25b0>

  lucas@driven:~/programming/cmg$ script/about About your application's environment Ruby version 1.8.6 (i686-darwin9.6.0) RubyGems version 1.3.1 Rails version 2.2.2 Active Record version 2.2.2 Action Pack version 2.2.2 Active Resource version 2.2.2 Action Mailer version 2.2.2 Active Support version 2.2.2 Application root /Users/lucas/programming/cmg Environment development Database schema version 20090124135009

  Any clue? Now I am for sure in 2.2.2.

• You flagged this item as spam.
  

  Lucas Efe February 9th, 2009 @ 08:51 AM

  Ben, today I tried to understand what was going on. I created a new project, based on rails 2.2.2, added the searchlogic gem and resource controller. Then 'script/generate scaffold Product title:string' (just to generate something). Went to the browser, entered '/products' and the same thing happened.

  First request:

  ActionView::TemplateError (undefined method order_by_link' for #<ActionView::Base:0x2830e44>) on line [#5](/projects/16601/tickets/5 "Ticket #5") of app/views/products/index.html.erb: 2: 3: <table> 4: <tr> 5: <th><%= order_by_link :name %></th> 6: <th>Price</th> 7: </tr> 8:

  Second request: Everything's fine.

  After that I removed resource controller from the plugin directory, and the magic happened. No more problems.

  Well, there's clearly a problem with resource controller. The funny thing is that with an older version of RC there's no problem. It works ok, but with the latest its when it fails.

  I think I'll stick with the old r_c's version. I should probably report this to Jamis Buck, right?

  Thanks for everything.

• You flagged this item as spam.
  

  Lucas Efe February 9th, 2009 @ 09:01 AM

  Update! I removed only one line from on file in the ResourceController plugin and it worked ok too.

  The file is lib/resource_controller.rb and the line is the first one

  require_dependency 'application'

  The thing is I dont't know the implications. I'll figure it out soon.

  Best regards. Love Searchlogic.

• 

  Ben Johnson February 9th, 2009 @ 01:23 PM

  • State changed from “open” to “resolved”

  Yes, I would definitely let him know about it. Thanks for the update.

• You flagged this item as spam.
  

  schof February 23rd, 2009 @ 08:35 PM

  I experienced a similar problem with the helpers not being available. In my case I had no problem in development at all (not even the first time.) In production I was getting this problem intermittently. The intermittent nature seemed to be caused by a Passenger timeout. So we could reproduce 100% of the time when setting the timeout to 10 sec. in production.

  Like Lucas, I am using resource_controller and an unpacked (vendor) version of the gem (1.6.3.) Fortunately I can report that the problem went away entirely when I removed from vendor/gems. Same gem, just stopped unpacking.
  

  Another interesting finding is that I could not reproduce the problem locally by switching to production mode. I suspect that the OS may be a factor.

  Development (No problems)

  OS X Mongrel

  Production - Local (No Problems)

  OS X Mongrel

  Production (Problem on first and periodic subsequent requests)

  Cent OS Passenger

• You flagged this item as spam.
  

  schof March 25th, 2009 @ 03:38 PM

  Problem appears to be solved in Rails 2.3