This extension provides a generic way for you to define different types of relationships between your products, by defining a RelationType for each type of relationship you'd like to maintain.
You can manage RelationTypes via the admin configuration menu, and you can maintain product relationships via Related Products tab on the edit product UI or via Related Products section on the edit variant UI.
- Accessories
- Cross Sells
- Up Sells
- Compatible Products
- Replacement Products
- Warranty & Support Products
Add solidus_related_products to your Gemfile:
gem 'solidus_related_products'Bundle your dependencies and run the installation generator:
bin/rails generate solidus_related_products:installYou can create four different RelationTypes:
| Applies From | Applies To | Bi-Directional available |
|---|---|---|
| Spree::Product | Spree::Product | Yes |
| Spree::Product | Spree::Variant | No |
| Spree::Variant | Spree::Product | No |
| Spree::Variant | Spree::Variant | Yes |
Bi-Directional You can optionally set the bi-directional flag (if available) to automatically create the inverse relation, the flag can be set only on the type creation and can't be changed later, this is needed to avoid unpredictable behavior in the case that the flag is changed. Keep in mind that if you remove one side of the relation, also the other hand will be removed, the same way happens for the description. The discounts are disabled for Bi-Directional by setting the discount amount to be only zero, this is needed because it's not clear how this feature should behave in this case.
The following examples use a Spree::Product -> Spree::Product relation type.
When you create a RelationType you can access that set of related products by referencing the relation_type name, see below for an example:
rt = Spree::RelationType.create(name: 'Accessories', applies_from: 'Spree::Product', applies_to: 'Spree::Product')
=> #<Spree::RelationType id: 4, name: "Accessories" ...>
product = Spree::Product.last
=> #<Spree::Product id: 1060500592 ...>
product.accessories
=> []Since respond_to? will not work in this case, you can test whether a relation_type method exists with has_related_products?(method):
product.has_related_products?('accessories')
# => true
if product.has_related_products?('accessories')
# Display an accessories box..
endYou can access all related products regardless of RelationType by:
product.relations
=> []Discounts You can optionally specify a discount amount to be applied if a customer purchases both products.
Note: In order for the coupon to be automatically applied, you must create a promotion leaving the code value empty, and adding an Action of type : RelatedProductDiscount (blank codes are required for coupons to be automatically applied).
First bundle your dependencies, then run bin/rake. bin/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
bin/rake extension:test_app.
bin/rakeTo run Rubocop static code analysis run
bundle exec rubocopWhen testing your application's integration with this extension you may use its factories. Simply add this require statement to your spec_helper:
require 'solidus_related_products/factories'To run this extension in a sandboxed Solidus application, you can run bin/sandbox. The path for
the sandbox app is ./sandbox and bin/rails will forward any Rails commands to
sandbox/bin/rails.
Here's an example:
$ bin/rails server
=> Booting Puma
=> Rails 6.0.2.1 application starting in development
* Listening on tcp://127.0.0.1:3000
Use Ctrl-C to stop
Before and after releases the changelog should be updated to reflect the up-to-date status of the project:
bin/rake changelog
git add CHANGELOG.md
git commit -m "Update the changelog"Please refer to the dedicated page on Solidus wiki.
Copyright (c) 2010-2015 Brian Quinn and contributors, released under the New BSD License