Are you saying, instead of saying r^'some_pattern/', include(urls_to_include), basically cut and paste that included url file into my project's url file then decorate the views (in this case, they are all generic)? While I understand you can write any urls you want, I guess I don't understand why you would necessarily want to change them? For examply, I have your book, as it turns out :) and at one point you say let's leave the urls generic so we aren't dictating where a person stores his blog. So let's say I want to plug that blug into my project, which is more than just a blog, but I want the blog to require you to be authenticated. Is there truly no nice way to tell django require the user to be logged in for all views associated w/ those urls?
On Oct 18, 1:28 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Sat, Oct 18, 2008 at 12:25 PM, Heather <[EMAIL PROTECTED]> wrote: > > What do you mean by "set up the urls so you'll have it"? > > Somewhere in your URL configuration, put URL patterns which point to > the views you want at the URLs you want, and wrap the views with > login_required there. > > Remember: URL configuration is configuration. It's not something you > have to treat as unchangeable code, so it's OK if you want something > different than the defaults some application ships, and it's perfectly > acceptable to set up whatever URL patterns you like for it. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
