Re: When do we stop using Django admin?

Thanks everyone for your valuable suggestions! On Mar 8, 3:23 am, Michael Radziej wrote: > On Mon, 7 Mar 2011 21:49:45 -0800 (PST), ajaishankar > wrote: > > I do know we can tweak the admin to restrict querysets etc. and also > > override admin templates - but is admin

Re: When do we stop using Django admin?

Thanks KG :) On Mar 8, 12:16 am, ajaishankar wrote: > Thanks Viklap > > We have been doing a lot of ModelAdmin & ModelForm tweaking as > mentioned in those slides. > > But still kind of skeptical we should be opening up the admin to other > companies; and go through the

Re: When do we stop using Django admin?

-the-django-admin>Regards,//Vikalp > > > > On Tue, Mar 8, 2011 at 11:19 AM, ajaishankar wrote: > > Hi > > > We have a app built on Django, and have been using the admin to good > > effect. > > > Right now we want to open up the app to other companies: &g

When do we stop using Django admin?

Hi We have a app built on Django, and have been using the admin to good effect. Right now we want to open up the app to other companies: 1. They can log in, create *their* own users 2. They can only see data that belongs to their company etc. 3. Also in one part of the app, we expect a highly cu

error codes for validation error messages

Hi New to django, and just loving it! Got the basics working - had the following question. What would be the preferred way to associate an error code with an error message (so that say it can be given back to an api call) class MyForm(forms.Form): email = forms.CharField(error_messages={'inv