Re: Eliminating DRY violations in urlpatterns

Hi, El lun, 07-04-2008 a las 09:08 -0700, bobhaugen escribió: > My view that creates a new order ends with this statement: > return HttpResponseRedirect('%s/%s/' >% ('order', new_order.id)) > [...] > The result of all the above is that I needed two different urlpattern

Re: Eliminating DRY violations in urlpatterns

Perfect. Thanks a lot, and sorry if I should have known that in the first place. On Apr 7, 11:32 am, Steve Potter <[EMAIL PROTECTED]> wrote: > On Apr 7, 11:08 am, bobhaugen <[EMAIL PROTECTED]> wrote: > > > My view that creates a new order ends with this statement: > > return HttpRes

Re: Eliminating DRY violations in urlpatterns

On Apr 7, 11:08 am, bobhaugen <[EMAIL PROTECTED]> wrote: > My view that creates a new order ends with this statement: > return HttpResponseRedirect('%s/%s/' >% ('order', new_order.id)) You should be able to just place a slash in front of your redirect statement so it

Eliminating DRY violations in urlpatterns

My view that creates a new order ends with this statement: return HttpResponseRedirect('%s/%s/' % ('order', new_order.id)) The 'order' URL fragment is appended to the orderentry form URL like so: (first url) http://127.0.0.1:8000/orderentry/order/4/ You can get to the