Python Signals - Building a web app with Django - Part 11

In this video we will add signals to create user profile pages and we modify the onboarding process.

This is part of a tutorial series where we build a web app from scratch and go live on the internet. Enjoy.

0:00 Intro
1:09 Signals Logic
5:34 Test
6:38 Sync Emails
12:22 User Onboarding

Follow me on:

Support me on:
Thank you.

#django #python #signals #webdevelopment #webapp #stayathomedad

[alexdin]

the best youtube channel that make django easy for every one

[Armin-qp]

Perfect explanation, you helped me a lot Bro, for real

[kazuoy]

Wow, I've never seen an explanation this straightforward before!

[MrValVet]

Thanks for the signals tutorial. Clear and concise explanation.

[CaptainCoder]

Hi Andreas I was implementing the signals in code but due to some weired reason i don't know why but every time i was getting fase in the created variable
Could you just help me out in this and tell me why it is happenning?

What possible i might be doing wrong or any solution?
Assume I have been following you strictly?

Thanks and waiting for you response

[muellexx]

Hi Andy,
Thank you very much for the videos, they are really great and help me a lot as a refresher for django and also for learning new things about django.
I have one question though, which I first had when you created the Profile model, but now even more: why do you need an email field in the profile? With the signal implemented in this lesson, the email in the User model and Profile model will always be identical, right? So in the Profile, couldn't you just always refer to profile.user.email, when you need the email? Then the email field in the Profile model, as well as the signals to keep the 2 emails identical wouldn't be needed.

[davidl.e]

Question with django signals. Why not overwrite the original Model's save() method and let it do other things to other models instead of using signals?

Signals can be hard to debug, easily conflicts if you are making concurrent request to the same db.

[captaintonny]

I'll be waiting on the changes on the signup.html as highlighted in the last tutorial regarding allauth on the changes made as it has its sigup.html

[nahidmubinkhan]

This video need to be updated. "allauth" library has been changed. In your last video's comment you said that no need to copy the "account" folder. But in this video you worked in "account" folder. But I don't have that folder. How can I redirect to profile-onboarding template?

[jonatansnyders]

Great stuff!

I was wondering about get_object_or_404 in the signal handlers, and from what I could find that doesn't seem to be necessary as you're not handling any http requests here but are directly working with your database. So left that out of my own solution.

Loving the course, keep it up Andreas!

[JuanitoOrtega]

Thank you for your videos. How I can set up redirect to profile-onboarding after sign up in the new version of the django-allauth?, signup.html template it is very different. Thank you.

[drkrueger]

Another excellent presentation! Thank you!
It would be great if you could create a video about Django debugging in VS Code. I have the Django Toolbar working but it would be great to step through the code and view the variables. I've tried and failed several times. I think part of the problem is the debugger is using the main python install executable, despite activating the virt env. Any advice greatly appreciated.

[__mostafa__]

Hello Andreas, I have another problem, but this time on the Sign Up page (17:30).
When I enter this page under any circumstances, I am faced with the following messages:

Your password can't be too similar to your other personal information.
Your password must contain at least 8 characters.
Your password can't be a commonly used password.
Your password can't be entirely numeric.


These messages are placed under the Password input.
What should I do so that these messages are not displayed as soon as I enter this page?