> (FYI, the method I was referring to is created by "magic", and has
> probably already been removed from the magic-removal branch. It is
> django.core.meta.manipulator_flatten_data(), but since this is tied so
> closely into the admin code it probably wouldn't do much for you. Sorry
> to send you on a goose chase with that!)
Erm, no.
flatten_data is necessary to make automatic manipulators work full stop.
They aren't tied to the admin in any way, shape or form.
There is absolutely no way to make using the raw __dict__ of an instance
work in anything like a sane way.
The reason why there is no flatten_data for manual manipulators is that
there is no way for the system to know what data you want put in there.
You may not even have a model object behind it. So you need to write it
yourself.
Anyway, in this case, I have no idea what PythonistL is doing. He
appears to be writing out the html that the input fields would adding.
Very odd. Also, he should be using manipulator.flatten_data() as you said.
<h1>Change your profile1</h1>
<form method="post" action="./">
<table border="0" cellpadding="3" cellspacing="5" width="105%">
<tr>
<td width="22%"><big><font color="#0000FF"><label
for="id_Login">Login:</label> </font></big></td>
<td width="3%"><big><strong><font
color="#FF0000">*</font></strong></big></td>
<td width="81%" colspan="2"><font color="#00FF00">{{form.login}}
</font></td>
</tr>
</table>
<p><span class="required"><big><font
color="#FF0000">*</font></big></span> Required
information</p>
<p> </p>
<p><input type="submit" value="Register"/> </p>
</form>
Would be a vaguely reasonable place to start.
