Is the initial value of a form field available in the template?
ChrisK
values. Here's a precis:
template has
<form action="/map/fences/newFence/" method="POST">
{{form.url.field.initial}}
{{form.auth_id}} {{form.media_id}} {{form.fence_id}}
<p><label for="id_teaser">Reminder String:</label>
<input id="id_teaser" type="text" name="teaser" maxlength="40" /></
p>
form type looks like
class editFenceForm(forms.Form):
teaser = forms.CharField(max_length=40)
auth_id = forms.CharField(widget=forms.HiddenInput)
media_id = forms.IntegerField(widget=forms.HiddenInput)
fence_id = forms.IntegerField(widget=forms.HiddenInput)
invocation looks like
form = editFenceForm(initial={
'auth_id' : auth_id, 'fence_id': fence_id, 'media_id':
m_id,
'teaser': m.teaser, })
output html looks like
<form action="/map/fences/newFence/" method="POST">
None
<input type="hidden" name="auth_id" value="ckantarj" id="id_auth_id" /
> <input type="hidden" name="media_id" value="13" id="id_media_id" />
<input type="hidden" name="fence_id" value="27" id="id_fence_id" />
<p><label for="id_teaser">Reminder String:</label>
<input id="id_teaser" type="text" name="teaser" maxlength="40" /></
p>
I'm really not expecting "None" there. If I just use {{form.as_p}},
the values are filled in correctly.
What am I missing?
Thanks,
chris
Rajesh Dhawan
do you have a field called url in your form. Your Form class
definition above does not show such a field nor are you trying to set
an initial value for it in the form instantiation. Perhaps you want to
paste your test code again?
-Rajesh D.
ChrisK
template has
<form action="/map/fences/newFence/" method="POST">
{{form.auth_id}} {{form.fence_id}}
<input id="id_teaser" type="text" name="teaser" maxlength="40" /
></
p>
print m.teaser
'auth_id' : auth_id, 'fence_id': fence_id,
and, indeed, the print statement produces a value
resulting HTML looks like
<form action="/map/fences/editFence/" method="POST">
<input type="hidden" name="auth_id" value="ckantarj" id="id_auth_id" /
Malcolm Tredinnick
trying to solve, because you're asking a question that is too specific.
On Wed, 2008-11-26 at 12:19 -0800, ChrisK wrote:
> Sorry, I cut down my example poorly.
>
> template has
>
> <form action="/map/fences/newFence/" method="POST">
> {{form.teaser.field.initial}}
> {{form.auth_id}} {{form.fence_id}}
> <p><label for="id_teaser">Reminder String:</label>
> <input id="id_teaser" type="text" name="teaser" maxlength="40" /
> ></
> p>
The answer to your question as to whether this is correct syntax is
"yes, it is". However, I guess from the fact that you asked the
question, that what you're really asking is how to get the initial value
that the form will assign to the field. Since initial data can come from
either the form or the field, the way you are accessing it above is too
specific (in this case, the field class itself doesn't have initial
data, but the form might well have some initial data for that field).
If you look in django/forms/forms.py in the BoundField.as_widget()
method, you'll see how Django works out the value for a form widget.
It's a combination of the forms "data" value for the field, form initial
data and field initial data. Which also hints that it's almost never
going to be correct to force the use of "initial" data at the template
level, since if there's form-supplied "data" data, that should override
the "initial" data value. At the template level, attemptign to
differentiate between a value that was an initial default and a value
that was supplied by a previous post to the form is not really
appropriate. Even if you could do so, it would be exploiting a leaky
abstraction. At the form display level, you simply shouldn't care about
that difference.
Again, it comes to down to "what is the real problem you are trying to
solve?"
At the templ
Regards,
Malcolm
ChrisK
> I think you really need to explain what the real problem is that you're
> trying to solve, because you're asking a question that is too specific.
remember :-)
I think the basic issue is that there are some fields in the object
that I'd like to display but not have editable, and it's not at all
clear to me how to make that happen in the form processor. The values
are dynamic, so they can't be in the template.
I'm happy not to replicate the logic inside BoundField.as_widget(), if
there's some way that the "correct" value is exposed to the
template...
DavidA
> that I'd like to display but not have editable, and it's not at all
> clear to me how to make that happen in the form processor. The values
> are dynamic, so they can't be in the template.
the readonly attribute on a TextInput widget:
class LabelWidget(forms.TextInput):
def __init__(self, *args, **kwargs):
attrs = kwargs.get('attrs', {})
attrs['readonly'] = True
if 'class' in attrs:
attrs['class'] = attrs['class'] + ' label'
else:
attrs['class'] = 'label'
super(LabelWidget, self).__init__(*args, **kwargs)
Then I use it in forms like this:
class AccountForm(forms.Form):
name = forms.CharField(widget=LabelWidget)
business = forms.CharField(widget=LabelWidget(attrs={'size': 5}))
...
I set/add 'label' to the CSS class so I can style these differently. I
used a custom widget over explicit "form.initial['field']" syntax in
my template so I could let the form lay itself out automatically
treating all fields the same way.
-Dave
ChrisK
> I often have this need so I created a custom widget where I just set
> the readonly attribute on a TextInput widget:
>
> class LabelWidget(forms.TextInput):
display this!
