Problem:

hello i have a django e commerce app that have google social auth when new users create an account we create a some % of dicount code for them i have UserIdentifier class that when users create new account i save either their phoen number or their email address to then when a new users create account i check if we have this users before or not to stop them from abusing the discount code i have this pipeline :

I have an html page, which have dropdown field. I had load dropdown values from DB.
Now selecting dropdown, the required fields related to value may be load, which has been described in 1 DB Table. so how is it possible?

I have an html page, which have dropdown field. I had load dropdown values from DB.
Now selecting dropdown, the required fields related to value may be load, which has been described in 1 DB Table. so how is it possible?

I have an html page, which have dropdown field. I had load dropdown values from DB.
Now selecting dropdown, the required fields related to value may be load, which has been described in 1 DB Table. so how is it possible?

I have an html page, which have dropdown field. I had load dropdown values from DB.
Now selecting dropdown, the required fields related to value may be load, which has been described in 1 DB Table. so how is it possible?

I have an html page, which have dropdown field. I had load dropdown values from DB.
Now selecting dropdown, the required fields related to value may be load, which has been described in 1 DB Table. so how is it possible?

In my Django project, I have both normal registration and Google login. If a user registers normally and provides their email, and then tries to log in with Google using the same email, the classic login screen appears. What I want is this: If a user logs in with Google first and then tries to log in with the same email via normal registration, or if they register normally and later try to log in with Google using the same email, I want both methods to lead to the same account. In other words, regardless of whether they log in with Google or normal registration, the user’s information should be merged and they should access the same account in both cases.

I’m working on implementing an OTP system in my Django project using Twilio. I’ve successfully obtained a Twilio phone number, but the OTP message is not being sent to the user’s mobile number. Below are the details of my setup:

As you can see in the first screenshot, /products/new isn’t showing up as a valid URL although I followed the coding tutorial from YouTube exactly. For some reason there’s a blank character before “new” but no blank space in the current path I’m trying to request. I don’t know if that’s normal or not. I’m using django version 2.1 if that matters