Hi, There is quite a serious problem with Django 1.2's format localization and forms. At first I noticed Djnago ignores L10N date formats when displaying dates in form fields, but calendar widgets in admin don't. So when you try using the calendar, date format goes back and forth between localized and unlocalized versions. I opened a ticket couple of days ago (#13591) calling it an "usability" problem (because it is utterly confusing to have a date format changing, when the only thing you expected to be changed was a date).
It turned out however, that the issue is much more serious (and not contained to Django Admin only). Look at the StackOverflow question: http://stackoverflow.com/questions/2929388/django-1-2-dates-in-admin-forms-dont-work-with-locales-i10ntrue It turnes out date formats for some countries, shipped with Django, doesn't include the "universal" YYYY-MM-DD formats as accepted date format (DATE_INPUT_FORMATS). Which at first seems logical, but in conjunction with the fact that Django always uses the YYYY-MM-DD format to display dates in forms, ignoring localization settings, the result is people are getting form validating errors, when trying to edit their models. In other words Django populates form fields with data in format it doesn't accept itself. Ludwik Trammer -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.