similar to: Ruby 1.9 and Searchlogic problem

I am unable to call a polymorphic scope using the searchlogic plugin as it keeps on returning ''undefined method''. I am certain it is only a problem within my project as I created a test project and I was able to call a polymorphic scope using the searchlogic plugin. I am hoping someone can provide a suggestion on how to debug this issue. My project consists of several gems, and

Hi all, Stuck at this problem for several days. Tried to use named_scope, scope_out, and plugin such as searchlogic, but no result. The problem is as follows: I have a pic table and tag table, and a join table called pic_tag (with only pic_id and tag_id) so that I can associate N pics to M tags. This is the tutorial way to set up a many- to-many association. I''m trying to implement a

Hey The guys at the searchlogic google groups seem to be asleep -.- They didnt'' grant me permission to post yet. But anyways, right now, I followed the searchlogic tutorial found here -http://www.binarylogic.com/2008/09/07/tutorial-pagination-ordering- and-searching-with-searchlogic/ however, in that tutorial, the results of the find displays all my items, before i even search for

I am having problem starting my app, here''s the error message, i am running Ubuntu 9.04 with Apache with Passenger: The application has exited during startup (i.e. during the evaluation of config/environment.rb). The error message can be found below. To solve this problem, please follow any instructions in the error message. Error message: Missing these required gems:

Does "is_any" has a bug in searchlogic? "is_any" used to work fine for me. All of a sudden now, for unknown reasons, when I write for example :attribute_is_any => [1] , the sql output is "where attribute != 1" which is the opposite of what I want of course. Curiously, the problem only occurs when running with a web server (mongrel). I see the problem in the

Has anyone been able to use searchlogic with has_many_polymorphs? Are they compatible? -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to

Hi, i have 2 model, Merchant and Items and using acts_as_taggable_on Merchant has_many Items, and i try to find Merchant with search logic including the tags class Merchant < ActiveRecord::Base acts_as_taggable has_many :items end class Item < ActiveRecord::Base acts_as_taggable belongs_to :merchant end This works >> Merchant.tagged_with(''Tag 1'') but

hi there, i try to use searchlogic to find entities by date. its working if i just try to search something. the ordering helper is also working if i just show all results. if i want to order (lets say by zipcode) and find by date it wont work. the order helper messes up the params[:search] in case of using a date if i just search something the params look like (good): Parameters:

hi guys, I need a recommendation for searching with regards to timestamp & foreign key attributes. Sounds a bit too much but here''s an example. Suppose we have a "blog" object. It has many attributes such as - title - content - status_id - created_at - updated_at There are also "status" objects which have the following statuses, "new",

I have many named_scopes chained together in the normal way. So far so good. However in a couple of cases where: 1. The named scope is actually a correlated subquery and I need to pass additional scope into it sometimes. 2. Where the presence of a named scope in the chain should change the behaviour of a named_scope later in the chain Given: Product.price.volume.average_discount

Here are my scopes: default_scope :order => ''posted_on DESC'', :conditions => { :status => ''visible'' } named_scope :positive, :conditions => { :rating => ''positive'', :status => ''visible'' } named_scope :neutral, :conditions => { :rating => ''neutral'', :status =>

I recently upgraded to Rails 3, and this error has come up ubiquitously: DEPRECATION WARNING: Base.named_scope has been deprecated, please use Base.scope instead. Any ideas on how to get rid of it? Or should I just wait for something? There''s actually no place in my application where the code "Base.named_scope" exists, so I assume the problem is inherent in gems that

Hi, this is a general design question and I liked to see how other people handle the following situation: Before named_scope I wrote custom finders for my model classes. Something like # order.rb class Order < ActiveRecord::Base class << self def find_all_marked find(:all, :conditions => {:marked => 1}, :order => ''name ASC'') end end end Now

I just entered this ticket. http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/404-named_scope-bashes-critical-methods It turns out that in an ActiveRecord model like this Model << ActiveRecord::Base named_scope :public private def private_method end public def public_method end end The method public_method will be private because named scope

Hey all, I get error like this: ActionView::TemplateError (`@content_for_details_view_builder__-626960428'' is not allowed as an instance variable name) in app/views/shared/_details_view.haml: searchlogic (2.4.27) lib/searchlogic/rails_helpers.rb:75:in `fields_for'' searchlogic (2.4.27) lib/searchlogic/rails_helpers.rb:64:in `form_for''

I just opened a Rails ticket on a problem with named_scope in Rails 2.1, and cross-posted a message here which I send to rails-core. I''m still a bit mystified, because I''m having a problem caused by this on RSpec 1.1.4, but not on 1.1.3, and I don''t see a difference in code which would explain it. The basic problem, which I encountered upgrading our rails app to RSpec

I am in the process of upgrading my app from Rails2 to Rails3. My Rails2 app uses searchlogic heavily. After googling i''ve come to know that searchlogic is not compatible with Rails3 and need to use meta_search instead. But i havent quite understood the usage of meta_search vis-a-vis searchlogic. If i have a User model with :name and :address fields, i am not able to use the following

class Category has_many :tracks end class Track belongs_to :category, :counter_cache => true named_scope :converted, :conditions => {:converted => true} named_scope :active, :conditions => {:active => true} end I want to make custom counters for scoped associations, e.g: category.converted_tracks_count category.active_tracks_count And when `track` changes its converted,

I have a very annoying problem, when doing rake db:migrate, I get the error message: Missing these required gems: will_paginate ~> 2.3.11 But the gem is not missing, It runs very well in my app. To make the rake pass I have to comment out the gem in my environment.rb file. environment.rb: config.gem "will_paginate", :version => "~> 2.3.11", :source =>

Hi, Rails 2.3.2 class TestD < ActiveRecord::Base default_scope :limit => 12 named_scope :limit, lambda { |num| { :limit => num} } end ruby script/console >> TestD.all TestD Load (0.7ms) SELECT * FROM "test_ds" LIMIT 12 => [] >> TestD.limit(14) TestD Load (0.3ms) SELECT * FROM "test_ds" LIMIT 12 => [] Any ideas why the default limit