Stand-alone user registration ^ account management

Create issue
Issue #59 resolved
Former user created an issue

I have integrated django-registration (http://code.google.com/p/django-registration/)into the satchmo framework. The tarball is attached. If you untar it in the satchmo directory of today's (rev. 374) trunk checkout, and edit two lines in settings.py, and perform "syncdb" it should work.

This is mainly what I did: I put almost all the user interaction stuff in a folder called registration. I also modified shop/view as well as some template files.

If you look at registration/urls.py you will get a very good idea of everything that is happening.

Note that you need to perform a "syncdb" (this adds a new table, and will affect nothing else)

settings.py needs two new lines, as shown in the settings-customize.py on lines 101 and 105, and a modification on line 109.

The folder shop/views can replace the old shop/views. (The only things happening here is that accounts.py and contact.py are deleted. Their functionality is in registration)

shop/urls.py is modified as shown.

email-auth.py is moved from shop/ to registration/

The folder templates/ can replace the old templates/. base.html has small changes to add "About Us" and "Terms of Service" to "rightnav" A checkbox asking the user to agree to the TOS is part of the registration form. The "templates/email" folder has been deleted. The templates related to contact/login/logout/password are moved (some with small changes) to templates/registration

Note that registration/models.py has no dependency on Satchmo... registration/models.py and parts of registration/views.py are "borrowed" from django-project, but I don't know who to thank or acknowledge because I didn't see a name (except the username "ubernostrum").

I tried hard to minimize any disruption to satchmo... but in the end there was more changes than I would have liked. Please critique.

Reported by jalanoly@yahoo.com

Comments (6)

  1. Former user Account Deleted

    [413]: Created registration branch.

    I've added the setting REQUIRE_EMAIL_VERIFICATION.

    Do we want to have the Terms of Service by default? If not, I'll probably remove it entirely since it's very easy to add.

  2. Former user Account Deleted

    I agree with Chris' comment.... I have made the changes necessary to accomplish what he wants. In settings.py if you set ACCOUNT_ACTIVATION_DAYS to zero, a new account is immediately active without email verification.

    I have attached a new tarball and a README.txt file, and verified that the instructions work well with the latest revision (407) of satchmo trunk.

  3. Former user Account Deleted

    That didn't work out. The diff doesn't show which files were moved or any of that useful stuff.

  4. Chris Moffitt repo owner

    I don't think Terms of Service should be on by default. If someone wants to add it, we need to make it easy to do but not the default.

  5. Chris Moffitt repo owner

    I'm supportive of the improved functionality, however I think it needs to be easy (possibly configurable via settings.py) to automatically create and activate the account without going through the email process. Philosophically, I want to registration/checkout process to be as smooth as possible. I don't want people to have to wait to activate an account. However, some people may want this so havign the functionality is good, as long as it's not burdensome.

  6. Log in to comment