All you need to do is set AUTH_USER_MODEL = "Yourapp.yourmodelname" in your setttings.py, delete your entire database and run makemigrations and migrate again. Django sets the default user model at first migration only.
Hope this helps, you can ask here for your queries. Cheers, Naveen Arora On Wednesday, 26 February 2020 20:11:27 UTC+5:30, Roy Huang wrote: > > thanks Naveen > > wow, how did you even guess that !! yes I did have my own authentication > model on top of the original one > > I will put up more detail first thing tomorrow at work, so glad somebody > can help me out (crying ~~~~~~) > > Roy > > Naveen Arora於 2020年2月26日星期三 UTC+8下午9時46分32秒寫道： >> >> Hi Roy, >> >> Share the exact problem with screenshots and code if possible. Did you >> set default authentication model of user to yours..? >> >> Cheers, >> Naveen Arora >> >> On Wednesday, 26 February 2020 18:00:10 UTC+5:30, Roy Huang wrote: >>> >>> Hi all, >>> >>> any help will be appreciated, i've bee stuck on this for days, couldnt >>> find answers >>> >>> ok, here it is, >>> >>> 1) logged in and retrieved data back to a page, all good (got sessionid >>> and csrftoken) >>> >>> 2) make a request on a view which has got @login_required, then got >>> redirect to login (apparently sessionid got cleared ) >>> >>> any thoughts ? >>> >>> thanks >>> >>> donkey >>> >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7a9b82d6-29ad-4eae-b9ca-608d37226909%40googlegroups.com.
