This extension provides customer an interface to track their 'Return History' and also allows them to create return authorizations.
Try Spree Item Returns for Spree master with direct deployment on Heroku:
Try Spree Item Returns for Spree 3-4 with direct deployment on Heroku:
- Adds a tab for a user to keep track of all his/her return authorizations.
- Provides user an ability to create a return authorization against an order.
- Add this extension to your Gemfile with this line:
gem 'spree_item_returns' , github: 'vinsol-spree-contrib/spree_item_returns'
gem 'spree_item_returns', github: 'vinsol-spree-contrib/spree_item_returns', branch: 'X-X-stable'
The branch
option is important: it must match the version of Spree you're using.
For example, use 3-0-stable
if you're using Spree 3-0-stable
or any 3.0.x
version.
- Install the gem using Bundler:
bundle install
- Copy & run migrations
bundle exec rails g spree_item_returns:install
- Run migrations
bundle exec rake db:migrate
- Restart your server
- Go to Account -> 'Return History' Button. A list of all return made by users will be shown.
- User can select individual return and see it's details.
- Go to Account
- Open order which has return item.
- Click on 'Return Product' button.
- Select the product which need to be returned, and fill fields with appropriate data. And click on 'Create'
Here is a detailed article with screenshots on how does it work: http://vinsol.com/spreecommerce-items-return
For Building Dependencies:
appraisal install
The dummy app can be regenerated by using:
appraisal spree-3-1 rake test_app
This will run rake test_app using the dependencies configured for Spree 3.1. Similarly you can use spree-3-2 and spree-master for generating dummy applications using dependencies for Spree 3.2 and latest version of Spree
appraisal spree-3-1 rspec
This will run rspec using the dependencies configured for Spree 3.1. Similarly you can use spree-3-2 and spree-master to run rspec using dependencies for Spree 3.2 and latest version of Spree
First bundle your dependencies, then run rake
. rake
will default to building the dummy app if it does not exist, then it will run specs. The dummy app can be regenerated by using rake test_app
.
bundle
bundle exec rspec spec
- Fork the project
- Make one or more well commented and clean commits to the repository. You can make a new branch here if you are modifying more than one part or feature.
- Add tests for it. This is important so I don’t break it in a future version unintentionally.
- Perform a pull request in github's web interface.
Copyright (c) 2017 vinsol.com, released under the New MIT License