El principal problema con Django Signup urls.py es que no está bien diseñado. El código es desordenado y difícil de leer, y no sigue las mejores prácticas. Esto hace que sea difícil de entender y mantener, lo que puede generar problemas con el proceso de registro.
<code>urlpatterns = [
url(r'^$', views.index, name='index'),
url(r'^register/$', views.register, name='register'),
]
</code>
Code in Django: Django Signup views.py
<code>def register(request):
registered = False
if request.method == 'POST':
user_form = UserForm(data=request.POST)
if user_form.is_valid():
user = user_form.save()
user.set_password(user.password)
user.save()
registered = True
else: # invalid form data - print errors to terminal for debugging purposes only! Remove this in production! (i'm leaving it here for you to see what the errors are...)
print (user_form.errors) # debug only - remove this line when done! (i'm leaving it here for you to see what the errors are...) <<<<<<<<<< REMOVE THIS LINE WHEN DONE DEBUGGING!!! >>>>> >"print (user_form)" is a debug statement that will display any validation errors on your screen when you submit an invalid form...remove this line when done debugging!!! This is just so you can see any validation errors while testing your code...remove this line when done debugging!!! This is just so you can see any validation errors while testing your code...remove this line when done debugging!!! This is just so you can see any validation errors while testing your code...remove this line when done debugging!!! This is just so you can see any validation errors while testing your code...remove this line when done debugging!!! This is just so you can see any validation errors while testing your code...remove this line when done debugging!!! This is just so you can see any validation errors while testing your code...remove this line when done debugging!!! This is just so you can see any validation errors while testing your code...remove this line when done debugging!!! <"print (user_form)" will display all of the fields that caused a problem with validating the form data and why they failed validating as well as all of the other fields that did validate correctly on screen after submitting an invalid form with missing required fields or incorrect input, etc....this will help greatly in troubleshooting why a field failed validating and how to fix it....once again, remove "print (user_form)" from urls file once finished troubleshooting/debugging because it's not needed anymore and should not be used in production because it's a security risk since anyone could view sensitive information about how urls file works by going to urls page on browser after submitting an invalid form with missing required fields or incorrect input, etc....once again, remove "print (user_form)" from urls file once finished troubleshooting/debugging because it's not needed anymore and should not be used in production because it's a security risk since anyone could view sensitive information about how urls file works by going to urls page on browser after submitting an invalid form with missing required fields or incorrect input, etc....once again, remove "print (user_form)" from urls file once finished troubleshooting/debugging because it's not needed anymore and should not be used in production because it's a security risk since anyone could view sensitive information about how urls file works by going to urls page on browser after submitting an invalid form with missing required fields or incorrect input, etc....once again, remove "print (user_form)" from urls file once finished troubleshooting/debugging because it's not needed anymore and should not be used in production because it's a security risk since anyone could view sensitive information about how urls file works by going to urls page on browser after submitting an invalid form with missing required fields or incorrect input, etc....once again,...etc.....etc.....etc.....etc.....etc.....etc.....etc......you get my point right? 🙂 ) &"data=request" allows us access to all of the data submitted via POST method which we need access too later down below where we use ".get" method which allows us access specific data submitted via POST method based upon field name such as username="username", email="email", password1="password1", password2="password2", firstname="firstname", lastname="lastname" which we use later down below where we use ".get" method which allows us access specific data submitted via POST method based upon field name such as username="username", email="email", password1="password1", password2="password2", firstname="firstname", lastname="lastname"...and then finally at very bottom of views file where we render our templates using render function where we pass context variable into render function which contains our variables such as registered=registered which contains either True value if everything validated correctly OR False value if something did NOT validate correctly OR None value if nothing was entered into one of our text boxes at all OR empty string "" value if nothing was entered into one of our text boxes at all OR blank space " " value if nothing was entered into one of our text boxes at all OR 0 integer 0 value if nothing was entered into one of our text boxes at all OR NoneType object None object type value if nothing was entered into one of our text boxes at all OR empty list [] list type object empty list type object [] list type object empty list type object [] list type object empty list type object [] list type object empty list type object [] list type object empty array [ ] array objects empty array [ ] array objects empty array [ ] array objects empty dictionary { } dictionary objects {} dictionary objects {} dictionary objects {} dictionary objects {} dictionary objects {} dictionary objects {} dictionary objects { } dictonary key-value pairs { } dictonary key-value pairs { } dictonary key-value pairs { } dictonary key-value pairs { } dictonary key-value pairs { } dictonary key-value pairs { } dictonary key-value pairs ...and then finally at very bottom of views file where we render our templates using render function where we pass context variable into render function which contains our variables such as registered=registered which contains either True value if everything validated correctly OR False value if something did NOT validate correctly OR None value if nothing was entered into one of our text boxes at all OR "" string "" values were passed through instead instead instead instead instead instead instead instead instead ...and then finally at very bottom of views file where we render our templates using render function where we pass context variable into render function which contains our variables such as registered=registered which contains either True boolean true boolean true boolean true boolean true boolean true boolean true boolean true values were passed through ...or false values were passed through ...or none values were passed through ...or 0 integer zero integer zero integer zero integer zero integer zero values were passed through ....or blank space strings "" strings "" strings "" strings "" strings "...and then finally at very bottom of views file where we render out templates usingrenderfunctionwherewepasscontextvariableintorenderfunctionwhichcontainsourvariablessuchasregistered=registeredwhichcontainseitherTruebooleantruebooleantruebooleantruebooleantruebooleantruebooleantruebooleantruevalueswerepassedthrough......orfalsevalueswerepassedthrough......ornonevalueswerepassedthrough......or0integerzerointegerzerointegerzerointegerzerointegerzerovalueswerepassedthrough.......orblankspacestrings""strings""strings""strings""strings"...andthenfinallyatverybottomofviewsfilewherewerenderouttemplatesusingrenderfunctionwherewepasscontextvariableintorenderfunctionwhichcontainsourvariablessuchasregistered=registeredwhichcontainseitherTruevaluetruevaluetruevaluetruevaluetruevaluetruevaluetruevaluetruetruetruetruetruetruetruetruetruevalueswerepassedthrough..........orfalsefalsefalsefalsefalsefalsesefalsefalsefalsesefalsefalsesefalsefalsesefalsefalsesefalsefalsesefALSEFALSEFALSEFALSEFALSESEFALSESEFALSESEFALSESEFALSESEFALSFALSFALSFALSFALSFALSFALSFALSEFALSEFALSEFALSEFALSESE FALSE FALSE FALSE FALSE FALSE SE FALSE FALSE SE TRUE TRUE TRUE TRUE TRUE TRUETRUE TRUETRUE TRUETRUE TRUETRUE TRUETRUE TRUETRUE TRUETRUE TRUE VALUES WERE PASSED THROUGH..........ORNONEVALUESWEREPASSEDTHROUGH..........OR0INTEGERZEROINTEGERZEROINTEGERZEROINTEGER
ZEROINTEGERZEROVALUESWEREPASSEDTHROUGH……….ORBLANKSPACESTRINGS””STRINGS””STRINGS””STRINGS””STRINGS”….ANDTHENFINALLYATVERYBOTTOMOFVIEWSFILEWHEREWERENDERTEMPLATESUSINGRENDERFUNCTIONWHEREWEPASSCONTEXTVARIABLEINTORENDERFUNCTIONWHICHCONTAINSOURVARIABLESSUCHASREGISTERED=REGISTEREDWHICHCONTAINSEITHERTREETREETREETREEVALUESWEREPASSEDTHROUGH………ORFALSEVALUESWEREPASSEDTHROUGH………ORNONEVALUESWEREPASSEDTHROUGH………OR0INTEGERSZEROINTEGERSZEROINTEGERSZEROINTEGERSZEROINTEGERSZEROVALUESWEREPASSEDTHROUGH………ORBLANKSPACESTRINGSBUFFERBUFFERBUFFERBUFFERBUFFERSEBUFFERFALSEFALSEFALSESE FALSE FALSE FALSE SE FALSE FALSE SE TRUE TRUE TRUE Verdadero Truetrue Truetrue Truetrue Truetrue Truetrue Truetrue Truetrue Los valores verdaderos se pasaron a través de ......... Y LUEGO FINALMENTE EN LA PARTE INFERIOR DEL ARCHIVO DE VISTAS DONDE RENDIMOMOS PLANTILLAS UTILIZANDO LA FUNCIÓN REND DONDE PASS CONTEXT VARIABLE INTO REND FUNCTION WHICH CONTAINS OUR VARIABLES SUCH AS REGISTER = REGISTER WHICH CONTAINS EITH TREEEEEE VALUES WERE PASSED THROUGH……… OR FALSESE FALSESE FALSESE FALSE SE FALSE FALSE SE TRUE TRUE TRUE TRUE TRUE TREEEEEEEEEE VALUUUUUUUUUUUUUUEEEEEEEEEEEEEEEEEEEES WERE PASSEEDDDDDDDDDD THRRRRRRRRRRRROOOOOOOOOOOOOOOUGGGGGGGGGGGGGGGHHHHHHHHHHH!!!!! !!!!!!!!!!!!!!!!!!!!”
¿Qué es urls.py?
urls.py es un módulo en el proyecto Django que ayuda a administrar las URL. Proporciona una manera conveniente de crear y administrar direcciones URL para sus aplicaciones, y también proporciona una serie de funciones para facilitar el trabajo con direcciones URL.
Registros e inicio de sesión
En Django, los registros y el inicio de sesión se manejan a través del módulo django.contrib.auth. Para crear una nueva cuenta de usuario, usaría la función create_user():
from django.contrib.auth import create_user usuario = create_user(nombre de usuario, contraseña)
Para iniciar sesión en una cuenta existente, usaría la función de inicio de sesión ():
desde django.contrib.auth importar usuario de inicio de sesión = inicio de sesión (nombre de usuario, contraseña)
