And, BTW, I don't mind coding something in this direction (for example, subclasses of Product) if it is a common pain-point for other users in Cartridge, but first, I want to see that I understand the current implementation, and how people are using it.
On Wednesday, 26 February 2014 13:37:00 UTC+2, Paul Walsh wrote: > > Hi, > > I posted something similar a while back: > > https://groups.google.com/forum/#!topic/mezzanine-users/-ltMQLoS8Jo > > But now it is getting to the stage where I'm actually going to rebuild a > store and move off Satchmo, starting next week. > > I've reassessed the options in Python land, and I'm mostly happy with > Cartridge, except for the issue of different product types. > > I want to check I'm not missing anything here, and hopefully hear from > others who have similar stores on Cartridge. > > I have at least 4 product types, let's say they all share 7-8 attributes > common to all products, and each have another 5-10 attributes that are > unique to each Product type. > > The implementation of product variations/options is a way to go about it, > I suppose, but it really seems most suited for variations of one product > type, and not for a range of different product types. > > Ultimately, what I'd like to get to is a set of distinct models: Book, > Accessory, Poster, TShirt - etc - for the content editor, and also for the > visitor - I'm not sure how to achieve that with what I see in Cartridge. > > > > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
