> http://example.com/reports/<Category_name>/<Subcategory_name>/ > > I don't want to use category and subcategory IDs because that's not "the > Django way", but when using names as URL parts I also get "ugly" URLs like: > > http://example.com/reports/Real%20Availability/...
It sounds like you're reaching for a SlugField, prepopulated from the actual names. This allows you to make prettier URLs. http://www.djangoproject.com/documentation/model-api/#slugfield This allows you to clean up the URL-field in the slug-field, but default to accepting the default "tidied" version of the name-field. -tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
