Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How stable is the Django trunk?
I am getting this issue today from updating my Django trunk:
403 Forbidden
CSRF verification failed. Request aborted.
More information is available with DEBUG=True.
To answer your specific question on stability of Django trunk, my experience has been generally positive. Though an occasional issue crops up, it’s usually fixed pretty quickly. If you plan on tracking trunk, I’d recommend monitoring the mailing lists, especially for big, potentially de-stabilizing changes (also, see “Is it safe to track trunk in Django?“), and for any potential backwards compatibility issues.
As for your CSRF verification failure, there have been recent changes to the CSRF middleware that you may need to accommodate in your code. See the documentation (Note the “How to use it” section is tagged with “Changed in Django Development version”) which includes information on a template tag that you’ll likely need to include in your template.