Hello,

A big problem with carts is handling products that have sub or related products. For example, selecting a basic pizza, and then the user could add for extra cash toppings.

I think this could be nicely handled in a cart:
1. if the items could be arranged by the user in a hierarchical fashion. Kind of like how you can move around taxonomy terms.
2. mark nodes as dependent on another, and require an additional product selection in an extra step

Something like this for cart items would be great. So the user selects two pizzas, and 5 toppings and then he can drag and drop the toppings between the pizzas, or presented with an extra step where the user can select dependent nodes (toppings in this case).

Would this be too much for this module? I think it would be killer :)

CommentFileSizeAuthor
#1 bitdefender-product-options.jpg228.75 KBalex dicianu

Comments

giorgio79’s picture

Issue summary: View changes

info

giorgio79’s picture

Issue summary: View changes

more info

alex dicianu’s picture

StatusFileSize
new228.75 KB

Hi,

I think you are talking about product options. See the screenshot attached with the BitDefender product page in the uk. There is the main product, the antivirus and below there are the product options:

  • The backup cd
  • Premium Services – Install & Configure
  • Windows Debugging
  • Virus & Spyware Removal

I think this would be the general feature that everybody could use ...

giorgio79’s picture

Yes, definitely.

Would be great if this could be made flexible so Drupal does all the heavy lifting.

Perhaps if we could select for a node dependent products via taxonomy or some other relationship, and Basic Cart would just do some kind of a validation.

For example:

Have pizza nodes, like Vesuvio and Prosciutto.
Then have topping nodes like eggs, ham, onion. And if toppings node have a reference field for pizza, basic cart would verify that if the user selected a topping it has been assigned to a pizza or sg like this.

Or in the case of Bitdefender, all the Premium Services could be separate nodes with a reference node for the main product.

The point is, Basic Cart should keep this light, and let Drupal do the heavy lifting. I think this is where the other projects like Ubercart and Commerce make a mistake and try to do it all themselves. :P

alex dicianu’s picture

I think we're on the same page here :)
I was actually looking for a D7 module that does this ... Basically it needs to link the 2 content types containing the products and product options.

giorgio79’s picture

This would be a good candidate
http://drupal.org/project/entityreference

It is the successor of http://drupal.org/project/references.

Then there is http://drupal.org/project/relation but that may need some time to mature.

PS: Or perhaps Taxonomy may be good as well, as that represents relationships and hierarchy very well and it is in core.

giorgio79’s picture

Issue summary: View changes

more

norman.lol’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Thank you everyone for taking the time to report and discuss this issue. 🙇🏻‍♂️

As the Drupal 7 versions of this module are no longer supported, I’ll be closing this issue. 🔚

Huge thanks and credit to everyone who contributed in any way. ✨

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.