Shopping Cart

[jeffolmstead]

@bleroy I see you have a good start on the back end of the shopping cart (e.g. controller / persistence). Were you planning on implementing the front end via similar scripts to what you had in Orchard (non-Core)? I might have an opening to port them over if that is where you were leaning. Just let me know.

[bleroy]

Yes, that’s the idea. I implemented a scriptless version but if you want to port the script, that’s great. The current behavior should still work as a fallback.

[jeffolmstead]

@bleroy can you add me back on to OrchardCore.Commerce git repository as I was bumped when the root project (e.g. OrchardCMS) made the change to require two factor authentication and mine wasn't set up when they made that change. It is set up now.

[bleroy]

Sure. Done. I invited you back to the org with the rights you had before. LMK if you need me to do something specific on this repo.

[mwpowellhtx]

Chiming in here, I think we have a requirement, potentially, to support perhaps blogs attached to cart and/or order items, in order to capture pre/post-sale discussion, agreement to terms of service, excahnge of assets, and this sort of thing. High level, I am thinking in terms of OC Workflow, would that be possible to support those phase lines in terms of workflow events. And, for our purpose, to associate Commerce Cart/Order content items with blog content items, along these lines.

[bleroy]

Yes. The main reason for modeling the checkout process as a workflow is so it can accommodate for custom business models. As long as your processes are exposed as workflow activities, you should be able to integrate them.

[mwpowellhtx]

Attached is a strong word, perhaps, associated with, along the lines of relationship between blog content item and cart/order content item.