I see in the 3.4 road map, there is an item to remove the multi-step checkout (#12058); however, the proposed work items also contain an item for true single page checkout (#10615).
Is the thought to only use the accordion style single page checkout? I feel that the true single page checkout in #10615 provides a much better UX. I have had a few customers ask for this very feature as they did not like the accordion page.
Also, what would be the possibility of replacing the checkout workflow with a plugin in order to give developers more control over the whole process?
nopCommerce 3.40 roadmap and estimated release date. Let's discuss.
MVP
Silver Solution Partner
- 5236
- 49485
- 10/4/2010
- Mexico
It is, as always, a great roadmap.
I suggest to include the following workitems to round the product attributes feature (in priority order):
1) Combinable/non-combinable attributes to differentiate attributes inherent to the product such as color and sizes (combinable) and those (non-combinable) which are add-ons or accesories for the product. This will also match well with the optimization of stock management for attribute combinations
2) "List" attribute control type let build simple product sets and bundles
3) Conditional checkout and product attributes will give a lot of flexibility and power for complex product configuration and attribute sets
I suggest to include the following workitems to round the product attributes feature (in priority order):
1) Combinable/non-combinable attributes to differentiate attributes inherent to the product such as color and sizes (combinable) and those (non-combinable) which are add-ons or accesories for the product. This will also match well with the optimization of stock management for attribute combinations
2) "List" attribute control type let build simple product sets and bundles
3) Conditional checkout and product attributes will give a lot of flexibility and power for complex product configuration and attribute sets
- 16
- 128
- 5/10/2013
- United Kingdom
fibox wrote:
I wholeheartedly agree with this as I require both work items.
Hi Andrei,
Roadmap for 3.4. seems good.
I would just vote for adding 10762 work item, which I mean is quite close to 11111 active work item.
I think, this functionality can be very interesting, there for I didn't found any e-commerce solution which can offer it. This way NopCommerce can become very interersting for a lot of new customers.
Please, think about it.
Thanks
Roadmap for 3.4. seems good.
I would just vote for adding 10762 work item, which I mean is quite close to 11111 active work item.
I think, this functionality can be very interesting, there for I didn't found any e-commerce solution which can offer it. This way NopCommerce can become very interersting for a lot of new customers.
Please, think about it.
Thanks
I wholeheartedly agree with this as I require both work items.
- 95
- 913
- 6/22/2013
- United Kingdom
Although I love the workflow of hg, git would allow me to keep source control for my customers shops in visual studio online, which would be a huge benefit. Also it means there is the functionality built into vs2013 so less environment setup would be needed.
please think about using nuget package restore (http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages) It would make the repo so much smaller so the clone is more likely to succeed.
please think about using nuget package restore (http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages) It would make the repo so much smaller so the clone is more likely to succeed.
