views:

399

answers:

3

I have a model that has a field named "state":

class Foo(models.Model):
    ...
    state = models.IntegerField(choices = STATES)
    ...

For every state, possible choices are a certain subset of all STATES. For example:

if foo.state == STATES.OPEN:     #if foo is open, possible states are CLOSED, CANCELED
    ...
if foo.state == STATES.PENDING:  #if foo is pending, possible states are OPEN,CANCELED
    ...

As a result, when foo.state changes to a new state, its set of possible choices changes also.

How can I implement this functionality on Admin add/change pages?

A: 

I see what you're trying to do, but why not just display all of them and if the person picks the (already set) current state, just don't change anything?

you could also just build a view with a form to provide this functionality

Jiaaro
that's a possibility, however not a very-elegant and secure one. changing the state triggers some calculations and modifications of the data to be made, therefore I really don't want to trust users, even if they are admins.
shanyu
+3  A: 

You need to use a custom ModelForm in the ModelAdmin class for that model. In the custom ModelForm's __init__ method, you can dynamically set the choices for that field:

class FooForm(forms.ModelForm):
    class Meta:
        model = Foo

    def __init__(self, *args, **kwargs):
        super(FooForm, self).__init__(*args, **kwargs)
        current_state = self.instance.state
        ...construct available_choices based on current state...
        self.fields['state'].choices = available_choices

You'd use it like this:

class FooAdmin(admin.ModelAdmin):
    form = FooForm
Carl Meyer
What happens on the 'add' views for the admin, since there's no self.instance, you can't depend on the instance for filtering, it would be nice to have the request object there
Jj
Yes, this ModelForm would need to handle the absence of self.instance and set the initial available choices appropriately. I don't know why the request object is relevant, but you do have access to it in ModelAdmin.add_view (http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/options.py#L704).
Carl Meyer
A: 

This seems like a job for some javascript. You want the list of items in a select box to change depending on the value of something else, which is presumably a checkbox or radio button. The only way to make that happen dynamically - without getting the user to save the form and reload the page - would be with javascript.

You can load custom javascript in a model's admin page by using the ModelAdmin's Media class, documented here.

Daniel Roseman
No, he's trying to set the choices for the next value of a field based on the current value of that same field - a key difference. So changing the options dynamically client-side is not relevant; in fact it would be very confusing.
Carl Meyer