I’ve just packaged up version 0.2 of django-registration; there are two big changes since the initial release which are worth mentioning (and which are, of course, covered in the documentation supplied with the download):
key_generated field was removed from the RegistrationProfile model, so you’ll want to drop the corresponding column in your database if you upgrade.
Also, a few bug fixes and minor enhancements went in; there’s a changelog in the download which lists them.
Comments for this entry are closed. If you'd like to share your thoughts on this entry with me, please contact me directly.
I was totally going to upgrade until I heard a few bugs went in! I much prefer bug fixes! :)
Well, as it turns out there was a bug in the packaged tarball, but it’s been fixed. And the typo in this entry has been fixed as well.
I’m including this app in the site I’m working on. I had a custom registration code before where I needed to include a country and first language in the sign-up form. So, I’m modifying your application a little bit to include these as well.
There’s one question I had about profile_callback. Shouldn’t it be used when a new user activates as opposed to just registering an account. Activating suggests an intent to use the site, so it’s probably better to create a site-specific user profile, when she/he decides that they want their account.
Is there a feature that allows to re-send a confirmation? In case it expires and someone wants to generate a new one without signing up again (as different user and/or email).