Installing and using django-registration -

Before that I am using some older version of the degogeno-registration which is now disliked because my server Does not allow installing plugins, so I have to use 'Registration' as a separate app for the Django application. Now my question is that I need to amend the registration to run as a DJENGO-AP? Can I just copy 'Registration' in my own Denggo project list, add it to the settings and it should work? There was no such thing as 'backend' defined, now the function is the backend init with get_backend, which takes 'path' as ​​the argument. I think this path is sent through the URL?

  url (r '^ active / (? P & lt; activation_key & gt; \ w +) / $', active, {'backend': 'Registration Backends.default.DefaultBackend' }, Name = 'registration_activate'),  

Within this list there is also a init file with default default class, activate and register classes

They use both signals. Do I need to bother these signals in any way? (I still do not get enough which they are used for). The last thing After the first registration, it was either redirecting success_aral or the template in such a way:

  returns.http response redirect (success_url or revers ('registration_complete'))  

Now the code responsible for this code is:

  If success_url is none: args, kwargs = backend.post_registration_redirect (request, new_user) return redirect (from, * Args, ** kwargs) Other: Return Redirect (success_url)  

and post_registration_redirect:

  def post_registration_redirect (auto, request, user Please return the name of the URL "" "After the successful user registration, redirect." Return "(registration 'complete', (), {})  

Why was it changed if it is still 'registration_full' and why the quarts are empty, so why are you worried?

The situation you are as simple as being outside Django applications (such as registration) are only normal Python packages and can be imported as such. . This means that the registration anywhere your dragon can already be in the path. The easiest place for this is often in your root project directory.

The logic was added to the backend logic that only takes a Python import path so that people can expand live-registration to use custom backend, if they wish.

If you put a registration directory on your dragon path then the existing string should work properly.