sunspot_solr rake tasks not being loaded properly

[sunspot]

sunspot_solr rake tasks not being loaded properly

[KurtPreston]

On that note, the README does not tell you that you must add any lines to the Rakefile. Without these instructions, the step rake 'sunspot:solr:start will not run.

[alindeman]

Tasks should be loaded automatically. What happens if you remove those require lines from your Rakefile?

[KurtPreston]

If I remove the require lines, no sunspot tasks are listed when I do a rake -T.

[alindeman]

What if you keep the require lines but use rake sunspot:reindex instead of sunspot:solr:reindex?

[KurtPreston]

If I have no require lines:

• No sunspot rake tasks show.

With just require 'sunspot/solr/tasks':

• No reindexing tasks are available

With just require 'sunspot/rails/tasks':

• rake sunspot:solr:start returns "Note: This task has been moved to the sunspot_solr gem"

With both require 'sunspot/solr/tasks' and require 'sunspot/rails/tasks':

• Same. rake sunspot:solr:start returns "Note: This task has been moved to the sunspot_solr gem"

[KurtPreston]

Of note, I can get it working by modifying sunspot_rails-1.3.0/lib/sunspot/rails/tasks.rb:59.

The line says unless defined?(Sunspot::Solr), then proceeds to define stubs for the Sunspot:Solr rake tasks. When I change it to unless false, then the code works fine.

It seems than sunspot_rails is not accurately detecting the presence of the sunspot_solr gem.

[KurtPreston]

Apparently, this problem started with sunspot_rails 1.3.0. It works fine under sunspot_rails 1.2.1.

[nielsjansendk]

+1 I have the samme problem rails 2.3.12, sunspot 1.3.0. Version 1.2.1 works.

[nz]

It seems than sunspot_rails is not accurately detecting the presence of the sunspot_solr gem.

Load order issues here perhaps? Hm.

@KurtPreston @ninajansen — can you show us [the relevant parts of] your app's Gemfile?

[alindeman]

I've been meaning to setup a Rails 2.3.14 application and try out the rake tasks. Might be able to get to it soon.

[KurtPreston]

There's nothing particularly fancy about our Gemfile. For the time, we've downgraded to sunspot_rails 1.2.0. But anyway, when we tried 1.3.0, our Gemfile looked like:

source :rubygems

gem 'rails', '2.3.14'
...
gem 'sunspot_rails', '1.3.0'

group :development do
  ...
  gem "sunspot_solr", "1.3.0"
end

[KurtPreston]

Any update on this issue?

[alindeman]

I can reproduce it, but do not yet know how to fix it. Patches welcomed.

[nathany]

Same issue on a Rails 2.3.14 app using Bundler 1.1.rc.7. Tried rearranging the gems (solr first) but makes no difference.

Search

gem 'sunspot', '> 1.3.0'
gem 'sunspot_rails', '> 1.3.0'
gem 'sunspot_solr', '~> 1.3.0'

As above, commenting out require 'sunspot/rails/tasks' got the start & stop commands working, but lost the reindex command.

[alindeman]

I merged in a fix to both 1-3-stable and master that claims to have fixed this. Can someone here try it out? Thanks.

[xiewenwei]

I resolved this by modifying the Rakefile.

My env is : sunspot_rails 1.3.1 sunspot_solr 1.3.1 Rails 2.3.11.

Add

module Sunspot
module Solr
end
end

above require 'sunspot/solr/tasks' require 'sunspot/rails/tasks' in the Rakefile