If I were doing something like a testimonial, I would most likely create it as a separate non-Product model. My Testimonial model could then either be linked in via an inline admin, or submitted via a separate form -- perhaps through a custom form linked to via email messages that went to customers after purchasing products.
I don't really follow what you're saying with the "<title" related to the product, instead of standardized on the stie name." Do you mean the page title, as in the HTML <title> tag? Can't you handle this via your templates? Either way, your given use cases don't really strike me as appropriate for custom product models, as the information isn't really related to extending Satchmo's definition of a Product, but providing extra context for users. I'd keep these separate. On Sun, Nov 8, 2009 at 4:39 AM, Nick Terry <[email protected]> wrote: > > Hello Satchmo Group, > > I'm trying to add more fields to enter in information for each product > that I would like to call upon on a store product page. For example, > for each product, I have specific testimonials for that product that I > would like to manage in the admin under the product, right where the > description, price, slug, etc. is. I would also like to add a field > where I can specifically make the <title> related to the product, > instead of standardized on the site name. Along with a few other fields > with specific information according to the products to fit in particular > places in my design template I'm working with. > > Looking at the documentation here: > http://www.satchmoproject.com/docs/svn/custom-product.html > and the tutorial here: > http://thisismedium.com/tech/satchmo-diaries-part-one/ > > It seems like it would be in my interest into creating a custom product > module, but I would like this to be on every product and the information > editable right directly there, without having to add a product subtype. > I haven't actually dived in yet to try and making the custom product > model, as the examples seem a little more complicated or a little > different than exactly what I want to do. It seems like it would be the > easiest for me to modify the main product model and add the fields in > there, but I know I'm not supposed to touch satchmo... especially if I'd > like to upgrade it later. > > It does look like the example on satchmoproject.com is closer to what > I'm looking at doing, but any guidance would sure be appreciated. (I > honestly do not code much and any clarity would help) Thanks. > > -Nick > > > > -- > visual communicator . interactive designer > www.nickterry.com > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
