‘Price’ is also a collection with a reference to the specific product it relates to. I know I cannot currently nest dynamic collections within each other but does anyone know of a work around?
If you can put all the variant description in a single richtext field, then you could potentially do this if you have a few variants:
Otherwise, you will need to have a “default” or “primary” price field in the product itself (to display in a collection list of products). Then in the Product template page, you can have a collection list to display variants.
Actually, since you only have a few products, you can do away with the CMS and just design the products directly onto a single page like what you are doing now.
A good use for CMS is if you/your client is going to be regularly adding/removing products, and requiring a template page to display a lot of details about a single product (specifications, extra images (slider/lightbox), related products). Otherwise a CMS is overkill here.
As I understand it this is related to a similar problem I posted a while back. There is no good way to do this in the CMS today. A list or table field in the CMS system would be very handy. I have requested it on the wishlist here
I completely agree. The example link I gave is just designed on the page, the reason for converting it to CMS is because the client now wants to have control over what products show and what the price variants of those products are.
I could keep it as is and just make the changes for them (adding/removing products/prices) but that’s not ideal for me.
I think I will just move the variants into the products collection like you suggested and then use conditions to show/hide when they’re being used.
I’m facing this issue right now. I need to create a course curriculum collection which requires sections and modules. The sections have multiple modules and I need to iterate through the sections and the modules to show under a specific course. This isn’t ideal right now… can’t actually do it.