If you want to override the views, create your own, register it to your urlpatterns for the appropriate pattern and, to be on the safe side, give the urlpattern that goes to that view the same `name` property that the Satchmo view your replacing has.
On Fri, Oct 30, 2009 at 3:52 PM, philosophe <[email protected]> wrote: > > Any suggestions on overriding the core product views? > > thanks, > --derek > > > On Oct 29, 9:44 am, philosophe <[email protected]> wrote: > > I need to put a form on a product detail page (for a custom "order" > > product) to allow the customer to upload a file, whose contents will > > be pushed into the product's CustomTextField. This means I will have > > to submit to the detail page in one step, then have the user add the > > product with that uploaded content to the cart in the next step. > > > > So I need a model for the form, and I need the view for that detail > > page; is there some approach that allows me to override the core model > > and view for that page? I want to get a straightforward multiple step > > flow down before I fancy it up with an ajax interaction. has anybody > > built anything similar? > > > > I had intended to use a custom product as the base for the custom > > order product, but the _get_subtype() issue stopped that approach. > > that means I would have been asking the same question, but I'd have a > > models.py in which to stick the form model. > > > > thanks, > > --derek > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
