用户没有用户配置文件(User has no userprofile)

 所以我用这样的现场score扩展了我的用户： 
 
 models.py： 
 
class UserProfile(models.Model):
    user = models.OneToOneField(User, on_delete=models.CASCADE)
    score = models.IntegerField(default=0);
 
 这似乎是沿着推荐方式的路线 
 
 然后我尝试在我的视图中访问用户userprofile： 
 
 views.py： 
 
player = request.user.userprofile
 
 这似乎也与推荐的方式一致。 但那是我得到我的错误的地方： 
 
RelatedObjectDoesNotExist
User has no userprofile.
 
 如果我将userprofile更改为其他内容，则会出现另一个错误： 
 
AttributeError
'User' object has no attribute 'flowerpot'
 
 当我尝试下面的代码： 
 
print request.user
print UserProfile.objects.all()
 
 我得到控制台输出： 
 
post_test1
[]
 
 编辑 
 我有两个超级用户， 
 在扩展用户之前创建的七个用户 
 和一个用户（post_test1），我是在扩展用户之后创建的。 
 
 
 EDIT_2 
 
 你好，我们又见面了！ 
 
 所以它清楚地表明我需要的是 
 
 
 
 创建一个post_save处理程序，以便在创建User对象时创建新的配置文件 
 
 
 这看起来很简单，当我读它时，去到链接到的页面是Django发送的所有信号的列表。 我抬头看了一下post_save，它说： 
 
 
 
 像pre_save一样，但在save（）方法结束时发送。 
 
 
 好的，所以我查了一下pre_save，它说： 
 
 
 
 这是在模型的save（）方法开始时发送的。 
 
 
 我这样解释：当我创建我的用户时（在我的views.py中）应该调用一个save（）方法（到目前为止还没有这样），然后post_save应该被发送（？ ）当创建User对象时它将创建一个新的配置文件！ 
 
 所以现在我准备开始看例子，所以我谷歌： 
 django post save example 
 在这里它看起来像我应该添加一些看起来像装饰@receiver(post_save, ... 
 在这里它看起来像我应该改变多个文件并写出一个信号定义？ 
 这一个似乎也暗示了多个文件（包括一个signals.py） 
 
 它看起来还有很多，我首先想到了。 这里的任何一个人是否可以解释我是如何做到这一点，或者向我展示信号如何工作的一些好资源？ 
 
 现在我的create_users视图如下所示： 
 
def create_user(request):
    if request.method == "POST":
        form = UserCreationForm(request.POST)
        if form.is_valid():
            username = form.cleaned_data["username"]
            password = form.cleaned_data["password1"]
            new_user = User.objects.create_user(username=username, password=password)
            return redirect('play')
    else:
        form = UserCreationForm()

    return render(request, 'antonymapp/create_user.html', {'form': form})
 
 我应该在返回之前调用new_user.save（）吗？ 如果是的话，为什么直到现在呢？ 在测试此视图时，我创建了一堆用户。 它也看起来像在这里post_save.connect(create_profile, sender=User)应该被添加？ 我显然很迷茫 

So I've extended my user with the field score like this:
 
models.py:
 
class UserProfile(models.Model):
    user = models.OneToOneField(User, on_delete=models.CASCADE)
    score = models.IntegerField(default=0);
 
which seemed to be along the lines of the recommended way 
 
Then I tried to access the users userprofile in my views:
 
views.py:
 
player = request.user.userprofile
 
which seemed to align with the recommended way as well. But that is where I get my error: 
 
RelatedObjectDoesNotExist
User has no userprofile.
 
If I change userprofile to something else I get another error: 
 
AttributeError
'User' object has no attribute 'flowerpot'
 
When I try the following code:
 
print request.user
print UserProfile.objects.all()
 
I get the console output:
 
post_test1
[]
 
EDIT
 I have two superusers,
 seven users I created before extending the user
 and one user (post_test1) I created after extending the user. 
 
 
EDIT_2 
 
Hi again!
 
So it seams clear that what I need is to 
 
 
 
create a post_save handler that creates a new profile when ever the User object is created
 
 
This seemed simple enough when I read it, went to the page that was linked to which was a list of all the signals Django sends. I looked up post_save and it said:
 
 
 
Like pre_save, but sent at the end of the save() method.
 
 
Alright, so I look up pre_save and it says:
 
 
 
This is sent at the beginning of a model’s save() method.
 
 
I've interpreted it like this: When I create my user (in my views.py) a save() method should be called (which hasn't been the case up till now) and after that a post_save should be sent(?) which will create a new profile when ever the User object is created!
 
So now I'm ready to start looking at examples, so I google:
 django post save example
 Here it looks like I'm supposed to add something that looks like a decorator @receiver(post_save, ...
 Here it looks like I'm supposed to alter multiple files and write a signal definition?
 This one also seem to imply multiple files (including a signals.py)
 
It looks like there's a lot more too it then I first thought. Could any one here either explain how I'm to do this or show me to some good resources on how signals work ?
 
Right now my create_users view look like this:
 
def create_user(request):
    if request.method == "POST":
        form = UserCreationForm(request.POST)
        if form.is_valid():
            username = form.cleaned_data["username"]
            password = form.cleaned_data["password1"]
            new_user = User.objects.create_user(username=username, password=password)
            return redirect('play')
    else:
        form = UserCreationForm()

    return render(request, 'antonymapp/create_user.html', {'form': form})
 
Should I call new_user.save() before returning? If yes, why has it worked up till now? I have a bunch of users that I've created while testing this view. It also looks like somewhere around here post_save.connect(create_profile, sender=User) should be added? I'm obviously quite lost here...

原文：https://stackoverflow.com/questions/36317816