Re: Problems with User Auth stuff

I think I mis-read the comment by Mookai. Instead of fighting the existing fraework, I am going to try to use the User from django.models.auth directly (no subclassing) and unset is_staff and is_superuser attributes so that those users can not mess with the admin rights. The Appuser class was only

Re: how about i18n ?

On 8/1/05, Nebojša Đorđević <[EMAIL PROTECTED]> wrote: > > I'll will have this running on current version until the end of > > next week. > > First version is out. I'm attached patch to http:// > code.djangoproject.com/ticket/65. > > btw. Is this thread is more appropriate for django-devel? Yes,

Re: how about i18n ?

On 29-08-2005, at 20:19, Nebojša Đorđević wrote: I'll will have this running on current version until the end of next week. First version is out. I'm attached patch to http:// code.djangoproject.com/ticket/65. btw. Is this thread is more appropriate for django-devel?

DRY strategy for portal site

Hi, I want to use Django for portal-like project. There will be no real "public" and "cms" parts -- everybody with an account can log in in one place, even admin. Sort of site where Plone was made for. Now i was thinking what would be the most effecient, DRY way to use Django here. My first thou