Basically what happens is you have a hierarchial content system. Unlimited subcategories, and products under these subcategories. When you create/edit a product you will specify a price, name, and description. (A name and description for each language if you have more than one turned on).
In your product template you can decide how to layout the price, description, and product images. All products have the field template_id, so it is possible to in fact have multiple product templates. Not all sites will require this functionality, but it will definitely be handy for some. On Jul 27, 9:44 am, "Dr. Tarique Sani" <[EMAIL PROTECTED]> wrote: > On 7/27/07, savagekabbage <[EMAIL PROTECTED]> wrote: > > > > > The reason I wanted to go with database storage instead of flat file > > is because of the user who may want to have 20 different product > > templates for a large site. This just seemed easier to handle if the > > templates were stored in the database. > > I think you are mixing product details with templates here... or am i > missing something > > T > > -- > ============================================================= > Cheesecake-Photoblog:http://cheesecake-photoblog.org > PHP for E-Biz:http://sanisoft.com > ============================================================= --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
