forked from bread-and-pepper/django-userena
-
Notifications
You must be signed in to change notification settings - Fork 0
/
UPDATES
84 lines (47 loc) · 2.19 KB
/
UPDATES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
# UPDATES
This file contains all the backwards-incompatible (since 1.0.1) and other
significant (since 1.4.1) changes.
## Version 1.4.1
Fixes and improvements:
- Set `html2text==2014.12.29` requirement in order to remove nasty hack
in `userena/mail.py` (#462).
- Updated version in Sphinx docs (#461).
- Added support for Python3.2 (#453).
- Fixed issue causing malformed utf-8 usernames on user profile creation (#456).
- Fixed issue with user creation on Python3.4 (#455).
- Fixed randomly failing tests on travis (#446).
## Version 1.4.0
Fixes and improvements:
- Python3.3 and Python3.4 support added.
## Version 1.3.2
Backwards incompatibile changes:
- Creating new user always creates new empty userena profile (fixes bug from 1.3.1).
## Version 1.3.1
Backwards incompatibile changes:
- When USERENA_ACTIVATION_REQUIRED = False, creating new user does not automatically
create userena profile (bug).
## Version 1.2.2
Backwards incompatibile changes:
- Changed backwards relationships names for Umessages contrib application from
`to_user` to `um_to_user` and `from_user` to `um_from_user`.
## Version 1.2.0
Backwards incompatibile changes:
- This version updates Userena to be able to use the new `User` model found in
Django 1.5. This does require the django-guardion > 1.5-dev. To make this
work, there is a `get_user_model` function in `userena/utils.py` which is used
to get the correct `User` model.
## Version 1.1.2
Backwards incompatibile changes:
- Activation view no longer contains username. If you override
`userena/templates/userena/emails/activation_email_message.txt` and
`userena/templates/userena/emails/confirmation_email_message_new.txt` be sure
to remove username from the URL.
## Version 1.1
Backwards incompatibile changes:
- Userena now requires Django >= 1.3 because of the use of class based views.
## Version 1.0.1
Backwards incompatibile changes:
- Removed the ``user`` relationship outside ``UserenaBaseProfile`` model. This
allows the user to define it's own relationship and fixes a conflict while
running ``manage.py test``. To migrate, place the ``user`` field inside your
profile model, instead of inheriting it from the ``abstract`` class.