Skip to content

Loading…

Problem in Installing or overriding the extension in spree 0.70 version #588

Closed
railsfactory-dhibika opened this Issue · 3 comments

4 participants

@railsfactory-dhibika

How to install or override an extension in spree version 0.70.

For example -Spree reviews and ratings

In spree-60.0 usually i added the gem "spree_reviews" in the Gemfile which is in sandbox folder.

But in case of spree version 70.0 there is no Gemfile in sandbox.How can i use the extension in this version.I tried to add the gem in Gemfile which is in home folder but it shows error

rake aborted!
Don't know how to build task 'spree_reviews:install'
(See full trace by running task with --trace)

while execute "rake spree_reviews:install".What should i do in this case?

Reply me if anyone knows.

@modology

sandbox now relies on the dummy skeleton which doesn't have Gemfile. Trying out new extension is out of the scope of sandbox. To try out, you can do create new rails app, and append the spree gem into it:

gem 'spree', :git => 'git://github.com/spree/spree.git'

or point it to your local cloned repisitory

gem 'spree', :path => 'spree-path-here'

then bootstrap with:

bundle install
rails g spree:site
bundle exec rake db:migrate
bundle exec rake db:seed
bundle exec rake spree_sample:load

now you are free to add whatever extension you like.

@humancopy

It's because the extension generator creates an install generator module with a singularized version of the the extension's name.

So for example in this case you'll find the file spree_reviews/lib/generators/spree_reviews/install/install_generator.rb
which declares the module SpreeReview instead of SpreeReviews.

@radar
Spree Commerce member

Not an issue to do with Spree core, as far as I can tell. Closing this down. If you still need help, please ask on the Google Group: http://groups.google.com/group/spree-user.

Thanks!

@radar radar closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.