.~hddlmZddlmZddlmZddlmZddlm Z ddl m Z ddl m Zdd l mZdd l mZGd d eZGd deZ GddeZy))settings)get_current_site)render)signals)RegistrationProfile) UserModel)ActivationView)RegistrationView)ResendActivationViewc8eZdZdZeeddZdZeZ dZ dZ y)r a\ A registration backend which follows a simple workflow: 1. User signs up, inactive account is created. 2. Email is sent to user with activation link. 3. User clicks activation link, account is now active. Using this backend requires that * ``registration`` be listed in the ``INSTALLED_APPS`` setting (since this backend makes use of models defined in this application). * The setting ``ACCOUNT_ACTIVATION_DAYS`` be supplied, specifying (as an integer) the number of days from registration during which a user may activate their account (after that period expires, activation will be disallowed). * The creation of the templates ``registration/activation_email_subject.txt`` and ``registration/activation_email.txt``, which will be used for the activation email. See the notes for this backends ``register`` method for details regarding these templates. When subclassing this view, you can set the ``SEND_ACTIVATION_EMAIL`` class variable to False to skip sending the new user a confirmation email or set ``SEND_ACTIVATION_EMAIL`` to ``False``. Doing so implies that you will have to activate the user manually from the admin site or send an activation by some other method. For example, by listening for the ``user_registered`` signal. Additionally, registration can be temporarily closed by adding the setting ``REGISTRATION_OPEN`` and setting it to ``False``. Omitting this setting, or setting it to ``True``, will be interpreted as meaning that registration is currently open and permitted. Internally, this is accomplished via storing an activation key in an instance of ``registration.models.RegistrationProfile``. See that model and its custom manager for full documentation of its fields and supported operations. SEND_ACTIVATION_EMAILTregistration_completect|j}t|dr|jd}n.t j j di|j}|jj j|||j|j}tjj|j||j|S)a Given a username, email address and password, register a new user account, which will initially be inactive. Along with the new ``User`` object, a new ``registration.models.RegistrationProfile`` will be created, tied to that ``User``, containing the activation key which will be used for this account. An email will be sent to the supplied email address; this email should contain an activation link. The email will be rendered using two templates. See the documentation for ``RegistrationProfile.send_activation_email()`` for information about these templates and the contexts provided to them. After the ``User`` and ``RegistrationProfile`` are created and the activation email is sent, the signal ``registration.signals.user_registered`` will be sent, with the new ``User`` as the keyword argument ``user`` and the class of this backend as the sender. saveF)commit)new_usersite send_emailrequestsenderuserr)rrhasattrrr objects create_user cleaned_dataregistration_profilecreate_inactive_userrruser_registeredsend __class__)selfformrnew_user_instancers l/var/www/peopleoo.sandbox-dev.co.uk/venv/lib/python3.12/site-packages/registration/backends/default/views.pyregisterzRegistrationView.register@s0  - 4 $  7 ".!4!4"-+"C040A0A"C ,,44II&11LL J  $$DNN*2-1\\ % ;c$ttddS)a Indicate whether account registration is currently permitted, based on the value of the setting ``REGISTRATION_OPEN``. This is determined as follows: * If ``REGISTRATION_OPEN`` is not specified in settings, or is set to ``True``, registration is permitted. * If ``REGISTRATION_OPEN`` is both specified and set to ``False``, registration is not permitted. REGISTRATION_OPENT)getattrr)r$s r'registration_allowedz%RegistrationView.registration_allowedksx!4d;;r)N) __name__ __module__ __qualname____doc__r,rr success_urlrrr(r-rr)r'r r s0,Z$H.EtL)K.)V  r)c ddifS)N registration_activation_completerr)r$rs r'get_success_urlzActivationView.get_success_urls2B;;r)N)r.r/r0rrr=r@rr)r'r r {s.*rRsJ ;#)9=Ek<+k<\<'<:3r)