Hi Tim,
On Tue, Mar 23, 2010 at 1:03 AM, Tim Shaffer wrote:
> Ah, yes I see the problem. Good catch. I hadn't tested that
> functionality. Luckily it is a simple change to admin.py. It's a
> matter of removing line 25:
>
once again, thanks for the good work. Now it works perfectly. You did
a grea
SVN diff is here:
http://code.google.com/p/django-namespace/source/diff?spec=svn3&r=3&format=side&path=/trunk/namespace/admin.py&old_path=/trunk/namespace/admin.py&old=2
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, sen
Ah, yes I see the problem. Good catch. I hadn't tested that
functionality. Luckily it is a simple change to admin.py. It's a
matter of removing line 25:
form.base_fields["namespace"].queryset =
Namespace.objects.user_can_access(request.user)
And replacing it with the following 3 lines. This basic
Hi Tim,
I just tried your app and, wow, this is exactly what i was looking
for. It works instantly, but, as always, there must be a but.
One thing doesnt work. I did all as you said, and, like i wrote, it
worked out of the box, except my ForeignKeys.
In my example i have:
class Task(NamespacedMod
Django doesn't support that out of the box. I searched and couldn't
find anything. Self plug: I created an app that does exactly this.
http://code.google.com/p/django-namespace/
Only difference is I called the model Namespace instead of Domain.
Just download it, then add it to your INSTALLED_APPS
5 matches
Mail list logo
