This is caused by a security-related change in Django 1.3.1. You can disable this behavior by adding the following to your settings_local.py file:
Modified on: Wed, 16 Sep, 2015 at 4:42 AM
This is caused by a security-related change in Django 1.3.1. You can disable this behavior by adding the following to your settings_local.py file:
Did you find it helpful? Yes No
Send feedback