Question

I have a modified admin form, where I added a field that shall modify the values of the current model’s parent object. Now, depending on the user, I need to

• alter the queryset of that extra field
• set another field as readonly (or better, even hide it completely)

Basically my code below works as I’d expect it. A superuser gets the whole queryset and the other field is not readonly. All other users get a limited queryset and the other field is readonly. However, once I open that site in a different browser and as a non-superuser, even the superuser get the same result as the non-superusers. Seems like django somehow caches the result? If I put some print statements inside the conditional branches though, they get printed correctly. So the method still gets called each time and seems to still perform these steps. Only with a wrong outcome.

Is that a caching problem? Am I doing something entirely wrong? Can it be a bug in the django test server?

def get_form(self, request, obj=None, **kwargs):
    form = super(MultishopProductAdmin, self).get_form(request, obj, **kwargs)
    if obj is not None:
        form.declared_fields['categories'].initial = obj.product.category.all()
    if not request.user.is_superuser:
        user_site = request.user.get_profile().site
        form.declared_fields['categories'].queryset = Category.objects.filter(site__id=user_site.id)
        self.readonly_fields = ('virtual_sites', )
        if obj is not None:
            form.declared_fields['categories'].initial = obj.product.category.filter(site__id=user_site.id)
    return form

Answer 1

So I couldn’t find a really clever way to do what I wanted with django admin’s custom methods. What I ended up doing now is implementing the admin’s change_view, setting up my own form manually and performing all my custom initializations from there.

I then provided a custom template by setting change_form_template, which is simply extending admin/change_form.html but rendering my own form instead of the default one. I also set extra_context['adminform'] = None so the default admin form gets removed.

That way I can now customize my form the way I need it to be but still use all the other admin conveniences. So far it seems to work very nicely. Not the very most elegant solution either I think, but the best I could think of.