Hi Todd,
> > and for a ForeignKey:
> > related_object = OtherObject.objects.get(pk=23)
> > new_data['related_object'] = str(related_object.id)
>
> This, not so much. The related object entry is in the data field of
> the FormWrapper when I look at it, but if I render the SelectField it
> corresponds to, the empty entry is pre-selected, not the entry that
> corresponds to the related_object. Is it not possible to pre-select
> something in a SelectField, or do you have to do it some other way?
I'm sorry, I forgot to mention that there is something odd with the
current default manipulators with regards to foreign keys. As far as I
know, this is going to be changed before Django hits 1.0.
Let me try to explain this with an example. Suppose you have a
Customer model with two fields, a name and a country of origin:
class Customer(models.Model):
name = models.CharField(maxlength=100)
country = models.ForeignKey(Country)
The odd thing is that the FormWrapper, when rendering the select
field, will pre-select the country according to the value in
new_data['country_id'] instead of new_data['country']. But when the
form is POSTed to the view, the selected value will come in
new_data['country'].
In other words, look at this view:
def add_customer(request):
manipulator = Customer.AddManipulator()
new_data = {}
errors = {}
if request.POST:
new_data = request.POST.copy()
errors = manipulator.get_validation_errors(new_data)
# The country selected by the user comes in the field
# new_data['country'], but if there were errors from
# get_validation_errors(), the selection will be lost
# because FormWrapper expects 'country_id',
# so we need to do this:
new_data['country_id'] = new_data['country']
if not errors:
manipulator.do_html2python(new_data)
manipulator.save(new_data)
return HttpResponseRedirect('/some/url/')
else:
# No POST, set up default values
# FormWrapper expects country_id!
mexico = Country.objects.get(name='Mexico')
new_data['country_id'] = str( mexico.id )
form = forms.FormWrapper(manipulator, new_data, errors)
return render_to_response('template.html', {'form': form})
As you can see, the problem is that the FormWrapper uses the value in
'country_id' when rendering the select field in the template, but when
the form is posted the value will be available in new_data['country']
(as expected).
This does not happen when you build a custom manipulator, I don't know
why. Hopefully this discrepancy will disappear before Django hits
version 1.0.
> Also, since I don't really want the user to be able to change this,
> it would be just as nice for me to replace the SelectField that the
> AddManipulator creates with a HiddenField of my own, but I can't see
This is not recommended at all. It is easy for a malicious user to
change the value in a hidden field, thus bypassing your rules and
compromising your application. Never put in a hidden field a value
that must not be altered, just set the value in your view function.
Regards,
Jorge
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
