djangodocs.org

1305 sections across all versions Narrow to Django 6.0 (current) →

Log out via GET

Release notes Django 4.1 release notes

Use POST requests instead. If you want to retain the user experience of an HTML link, you can use a form that is styled to appear as a link:

dev

django.contrib.auth

Release notes Django 4.2 release notes

UserCreationForm now saves many-to-many form fields for a custom user model. The new BaseUserCreationForm is now the recommended base class for customizing the user creation form.

dev

Forms

Release notes Django 5.0 release notes

In order to improve accessibility, the following changes are made: Form fields now include the aria-describedby HTML attribute to enable screen readers to associate form fields with their help text. Invalid form fields now include the aria-invalid="true" HTML attribute.

dev

Forms

Release notes Django 5.1 release notes

In order to improve accessibility and enable screen readers to associate fieldsets with their help text, the form fieldset now includes the aria-describedby HTML attribute.

dev

django.contrib.admin

Release notes Django 6.0 release notes

The new AdminSite.password_change_form attribute allows customizing the form used in the admin site password change view. Message levels messages.DEBUG and messages.INFO now have distinct icons and CSS styling. Previously, both levels shared the same appearance as messages.SUCCESS.

dev

Bugfixes

Release notes Django 6.0.2 release notes

Fixed a visual regression in Django 6.0 for admin form fields grouped under a <fieldset> aligned horizontally (#36788).

dev

Forms

Release notes Django 6.1 release notes

The new asset object Stylesheet is available for adding custom HTML-attributes to stylesheet links in form media. See paths as objects for more details.

dev

Release notes Django 1.0 release notes What’s new in Django 1.0

… definitions are now completely decoupled from model definitions (no more class Admin declaration in models!), rewritten to use Django’s new form-handling library (introduced in the 0.96 release as django.newforms, and now available as simply django.forms) and redesigned with extensibility and …

4.2 5.0 5.1 5.2 6.0

Release notes Django 1.0 release notes What’s new in Django 1.0

… were scheduled for removal prior to the 1.0 release, are no longer present in Django. These include imports of the form library from django.newforms (now located simply at django.forms), the form_for_model and form_for_instance helper functions (which have been replaced by …

4.2 5.0 5.1 5.2 6.0

Release notes Django 1.1 release notes Backwards-incompatible changes in 1.1

In Django 1.1, BaseModelFormSet now calls ModelForm.save(). This is backwards-incompatible if you were modifying self.initial in a model formset’s __init__, or if you relied on the internal _total_form_count or _initial_form_count attributes of BaseFormSet. Those attributes are now public methods.

4.2 5.0 5.1 5.2 6.0

Bugfixes

Release notes Django 1.10.7 release notes

Made admin’s RelatedFieldWidgetWrapper use the wrapped widget’s value_omitted_from_data() method (#27905). Fixed model form default fallback for SelectMultiple (#27993).

4.2 5.0 5.1 5.2 6.0

Improved CSRF protection

Release notes Django 1.2 release notes What’s new in Django 1.2

… protection against Cross-Site Request Forgery (CSRF) attacks. This type of attack occurs when a malicious website contains a link, a form button or some JavaScript that is intended to perform some action on your website, using the credentials of a …

4.2 5.0 5.1 5.2 6.0

Release notes

Django 1.2.1 was released almost immediately after 1.2.0 to correct two small bugs: one was in the documentation packaging script, the other was a bug that affected datetime form field widgets when localization was enabled.

4.2 5.0 5.1 5.2 6.0