Jump to:
| Project: | Commerce Kickstart |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
The development of Commerce Kickstart 2.0 began with a store that was filled with demo content. This is helpful to see how products are created and managed, and what they can look like in their final form. Then the option of installing without the demo content was added. Now there are two versions of the site, the "Demo Content" and the "No Demo Content" versions. The "No Demo Content" has a massive number of bugs that aren't present in the other version. This is worrisome and indicates problems in the architecture around demo content. This issue has a number of tasks, and aims at analyzing and solving the demo content issue:
- Explain how demo content is installed, and how the logic differentiates from the point at which the user chooses one option or the other
- Explain how all of the [No Demo Store] bugs got introduced
- Analyze if we have come up with the best solution for getting demo content into the build, and make suggestions
For example, how much of the bugginess is due to having different themes?
For example, should there really be an option "No Demo Store Content" plus a feature list? Or is there a way to make "Demo content" a feature just like Blogs or Search?
Comments
#1
Closing old issue.
We've clarified this internally, but I'll recap here:
The main problem that we had was the fact that the demo store (and commerce_kickstart_theme) were made first (and were the #1 priority).
Then, "no_demo_store" and "omega_kickstart' were made by copying the original code, which meant that we suddenly had the same bugs twice.
We managed to fix this problem by removing most of the duplication over time:
1) commerce_kickstart_theme became a child theme of omega_kickstart.
2) We created commerce_kickstart_search (and from that, commerce_search_api) which removed the duplication of the search code from the features (which was the biggest duplicated part)
3) A lot of the product-specific UI stuff was removed from the duplicated features and moved into Commerce Backoffice.
4) The taxonomy code was moved into commerce_kickstart_taxonomy.
5) We created the "Add to cart confirmation" module.
6) Many parts of Kickstart were made more generic. For example, custom Views filters for taking all product display node types, or all product display categories, which means they didn't need to be hardcoded, which allowed us to remove several duplicated Views.
#2
Automatically closed -- issue fixed for 2 weeks with no activity.