*You can filter the objects based on user. Which means you can include a ForeignKey to User model in your models, and save the logged in user while saving the model. In the views, while displaying, you can filter based on the logged-in user. So no other user get to see your objects * On Tue, Aug 30, 2011 at 11:57 PM, Carsten Jantzen <cars...@jantzens.net>wrote:
> Hej I am new and trying to make a login for mysite. > I have written a basic login which validates against another site and > is working fine atm. > > I would like to make the auth related to the url. > So that user a with permission 1 can access www.test.dk/1/content but > he is not allowed to access www.test.dk/2/content > user 2 with permission 4 can access www.test.dk/4/content but he is > not allowed to access www.test.dk/1/content > > It there a good way to solved this? > > Is it possible extend the or use the @login_required tag to this solution. > > Hope for some input so I can find a solution. > > Regards > Carsten > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- Thanks and Regards, *Praveen Krishna R* -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
