2016-07-13 00:50:17 +00:00
|
|
|
===========================
|
|
|
|
|
Django 1.8.14 release notes
|
|
|
|
|
===========================
|
|
|
|
|
|
2016-07-06 19:41:06 +00:00
|
|
|
*July 18, 2016*
|
2016-07-13 00:50:17 +00:00
|
|
|
|
2016-07-06 19:41:06 +00:00
|
|
|
Django 1.8.14 fixes a security issue and a bug in 1.8.13.
|
|
|
|
|
|
|
|
|
|
XSS in admin's add/change related popup
|
|
|
|
|
=======================================
|
|
|
|
|
|
|
|
|
|
Unsafe usage of JavaScript's ``Element.innerHTML`` could result in XSS in the
|
|
|
|
|
admin's add/change related popup. ``Element.textContent`` is now used to
|
|
|
|
|
prevent execution of the data.
|
|
|
|
|
|
|
|
|
|
The debug view also used ``innerHTML``. Although a security issue wasn't
|
|
|
|
|
identified there, out of an abundance of caution it's also updated to use
|
|
|
|
|
``textContent``.
|
2016-07-13 00:50:17 +00:00
|
|
|
|
|
|
|
|
Bugfixes
|
|
|
|
|
========
|
|
|
|
|
|
|
|
|
|
* Fixed missing ``varchar/text_pattern_ops`` index on ``CharField`` and
|
|
|
|
|
``TextField`` respectively when using ``AddField`` on PostgreSQL
|
|
|
|
|
(:ticket:`26889`).
|
