mirror of
				https://github.com/django/django.git
				synced 2025-10-31 09:41:08 +00:00 
			
		
		
		
	Refs #32720 -- Used :commit: and :source: role in old release notes.
This commit is contained in:
		
				
					committed by
					
						 Mariusz Felisiak
						Mariusz Felisiak
					
				
			
			
				
	
			
			
			
						parent
						
							1557778121
						
					
				
				
					commit
					8c4caee76a
				
			| @@ -250,6 +250,4 @@ all their hard work: | ||||
| * Everyone who submitted a bug report, patch or ticket comment. We can't | ||||
|   possibly thank everyone by name -- over 200 developers submitted patches | ||||
|   that went into 0.96 -- but everyone who's contributed to Django is listed | ||||
|   in AUTHORS_. | ||||
|  | ||||
| .. _AUTHORS: https://code.djangoproject.com/browser/django/trunk/AUTHORS | ||||
|   in :source:`AUTHORS`. | ||||
|   | ||||
| @@ -7,13 +7,11 @@ released two days after 1.2.2. | ||||
|  | ||||
| This release corrects the following problems: | ||||
|  | ||||
| * The patch_ applied for the security issue covered in Django 1.2.2 caused | ||||
|   issues with non-ASCII responses using CSRF tokens. | ||||
| * The :commit:`patch <7f84657b6b2243cc787bdb9f296710c8d13ad0bd>` applied for | ||||
|   the security issue covered in Django 1.2.2 caused issues with non-ASCII | ||||
|   responses using CSRF tokens. | ||||
|  | ||||
| * The patch also caused issues with some forms, most notably the user-editing | ||||
|   forms in the Django administrative interface. | ||||
|  | ||||
| * The packaging manifest did not contain the full list of required files. | ||||
|  | ||||
| .. _patch: https://code.djangoproject.com/changeset/13699 | ||||
|  | ||||
|   | ||||
| @@ -115,9 +115,9 @@ ModelAdmin.lookup_allowed signature changed | ||||
| ------------------------------------------- | ||||
|  | ||||
| Django 1.2.4 introduced a method ``lookup_allowed`` on ``ModelAdmin``, to cope | ||||
| with a security issue (changeset `[15033] | ||||
| <https://code.djangoproject.com/changeset/15033>`_). Although this method was | ||||
| never documented, it seems some people have overridden ``lookup_allowed``, | ||||
| especially to cope with regressions introduced by that changeset. While the | ||||
| method is still undocumented and not marked as stable, it may be helpful to know | ||||
| that the signature of this function has changed. | ||||
| with a security issue (changeset :commit:`[15033] | ||||
| <85207a245bf09fdebe486b4c7bbcb65300f2a693>`). Although this method was never | ||||
| documented, it seems some people have overridden ``lookup_allowed``, especially | ||||
| to cope with regressions introduced by that changeset. While the method is | ||||
| still undocumented and not marked as stable, it may be helpful to know that the | ||||
| signature of this function has changed. | ||||
|   | ||||
| @@ -439,14 +439,13 @@ prohibited words an empty list. | ||||
|  | ||||
| If you want to restore the old behavior, simply put a | ||||
| ``PROFANITIES_LIST`` setting in your settings file that includes the | ||||
| words that you want to prohibit (see the `commit that implemented this | ||||
| change`_ if you want to see the list of words that was historically | ||||
| prohibited). However, if avoiding profanities is important to you, you | ||||
| would be well advised to seek out a better, less naive approach to the | ||||
| problem. | ||||
| words that you want to prohibit (see the :commit:`commit that implemented this | ||||
| change <edd767d2612d891a906268cf590571f541dd164f>` if you want to see the list | ||||
| of words that was historically prohibited). However, if avoiding profanities is | ||||
| important to you, you would be well advised to seek out a better, less naive | ||||
| approach to the problem. | ||||
|  | ||||
| .. _Scunthorpe problem: https://en.wikipedia.org/wiki/Scunthorpe_problem | ||||
| .. _commit that implemented this change: https://code.djangoproject.com/changeset/13996 | ||||
|  | ||||
| Localflavor changes | ||||
| ------------------- | ||||
| @@ -763,7 +762,8 @@ Changes to the login methods of the admin | ||||
| In previous version the admin app defined login methods in multiple locations | ||||
| and ignored the almost identical implementation in the already used auth app. | ||||
| A side effect of this duplication was the missing adoption of the changes made | ||||
| in r12634_ to support a broader set of characters for usernames. | ||||
| in :commit:`r12634 <c8015052d935a99a5c8f96434b2d0cd16d8a4e14>` to support a | ||||
| broader set of characters for usernames. | ||||
|  | ||||
| This release refactors the admin's login mechanism to use a subclass of the | ||||
| :class:`~django.contrib.auth.forms.AuthenticationForm` instead of a manual | ||||
| @@ -772,8 +772,6 @@ form validation. The previously undocumented method | ||||
| in favor of a new :attr:`~django.contrib.admin.AdminSite.login_form` | ||||
| attribute. | ||||
|  | ||||
| .. _r12634: https://code.djangoproject.com/changeset/12634 | ||||
|  | ||||
| ``reset`` and ``sqlreset`` management commands | ||||
| ---------------------------------------------- | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user