On 4/20/07, DuncanM <[EMAIL PROTECTED]> wrote: > > (r'^team/(?P<team_id>[0-9]+)/results/(?P<object_id>[0-9]+)/$', > 'django.views.generic.list_detail.object_detail', dict(results_dict, > template_name='teams/team_results_reports.html') > > doesn't work for me...
Uh, yeah, it wouldn't would it? Sorry, about that. Capturing and passing in an unexpected parameter to the generic views function is broken, as you discovered. If you still want to use this url form, I think it will work if you avoid capturing/naming the team_id: r'^team/[0-9]+/results/(?P<object_id>[0-9]+)/$' or even: r'/results/(?P<object_id>[0-9]+)/$' (that is, don't check the beginning of the string at all, just require that it end with /results/<object_id>/ ... I'll confess I didn't doulbe-check the regex docs and my regex is rusty so no guarantees either of those is correct....) Then you can still have your breadcrumbs in your url, but I'm not sure it is worth it. Depends on how complex your urls & urls config is going to get, and how valuable you think it will be to users to have breadcrumbs in the urls. Personally for my own app I've gone the 2nd route, and let the browser "back" button answer the question "how did I get here?", but I'll admit to occasionally wishing I could just glance at the url and tell. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
