在管理控制台中更新用户页面时，django管理页面不会发布

Question

I'm trying to deploy a django site. It appears to work correctly, however in the admin site, it appears that POST is not working for updating user accounts.

the error response is located here: http://dpaste.com/0CKD2CS

My question here, is if django-admin is running normally, why would a website not find the page in a POST setting?

Thank you.

Answer 1

The FileNotFoundError in this case actually originates with an attempt to read a "format file", which is used by Django for determining locale-specific formats for things like dates, times, and currency display. In this case it's on the DATE_INPUT_FORMATS for the DateField .

Django allows the path for formats to be specified in settings:

https://docs.djangoproject.com/en/1.8/ref/settings/#format-module-path

Otherwise there are a number of these configured in a locale directory in the Django distribution - .../lib/python2.7/site-packages/django/conf/locale . For example:

../lib/python2.7/site-packages/django/conf/locale/en_AU/formats.py
19:DATE_INPUT_FORMATS = (
20-    '%d/%m/%Y', '%d/%m/%y',             # '25/10/2006', '25/10/06'
21-    # '%b %d %Y', '%b %d, %Y',          # 'Oct 25 2006', 'Oct 25, 2006'
22-    # '%d %b %Y', '%d %b, %Y',          # '25 Oct 2006', '25 Oct, 2006'
23-    # '%B %d %Y', '%B %d, %Y',          # 'October 25 2006', 'October 25, 2006'
24-    # '%d %B %Y', '%d %B, %Y',          # '25 October 2006', '25 October, 2006'
25-)

Worth examining the effective locale and associated files. If you can live with disabling the translation machinery, or perhaps at least while troubleshooting, you can set USE_I18N=False in settings .

Possibly worth perusing the Django Internationalization and Localization docs.

Django will use en if there isn't a country-specific format module, so that will be fine. You can try using a Django shell in the project to attempt the equivalent call:

$ ./manage.py shell
>>> import datetime
>>> datetime.datetime.strptime('2015-10-19', '%Y-%m-%d').date()
datetime.date(2015, 10, 19)

The only place there is Django-related file I/O is in the loading of the format module so as long as django/conf/locale/en/formats.py is available then the possibilities for such failure are limited, failing something strange happening with datetime , which seems improbable. There is a fallback for the formats in that Django will retrieve from settings , so you could add this line to your settings :

DATE_INPUT_FORMATS = ( '%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y')