DateTime fields don't work in the generic views

[mlambert@…]

fieldname_date and fieldname_time aren't set on the data dictionary, so the form fields come up blank

And similarly, jacobkm said that this also needs the server to recombine these fields back into plain old fieldname on the POST-side.

[mr_little]

Look at admin-pages head, and add to generic templates html head necessary javascripts from admin media

[mlambert@…]

I don't quite know what you mean in the above comment, mr_little. I don't believe it's an issue of javascript. I believe this is because _get_flattened_data is only called for admin views, and the code needs to run for generic views as well., to set up fieldname_date and fieldname_time.

[anonymous]

Please fix soon. Very frustrating that the fields are not updated.

[deltabps]

Yes, please fix this soon. I try to get my view on the appropriate code, perhaps I could help.

This is a show-stopper for my django project :(

[mlambert@…]

So the quick hack-fix for this is:

In views/generic/create_update.py, in the big else statement for the request.POST check, after "new_data = object.dict", add:

from django.views.admin.main import _get_mod_opts, _get_flattened_data
mod, opts = _get_mod_opts(app_label, module_name)
for f in opts.fields:

new_data.update(_get_flattened_data(f, getattr(object, f.column)))

Basically, a c&p of the code from the admin interface to use the functions that we need in the generic views. I'm keeping this simple fix until the django developers get around to implemeting a more proper fix (involving code reorganization and such to avoid generic views' reliance on admin stuff)

[mlambert@…]

diff that fixes #337 and #338

[rjwittams]

This is fixed in new-admin

[rjwittams]

fixed in new-admin merge . People still have to manually include javascript.

[(none)]

Milestone Version 1.0 deleted