Django中User与Profile模型表单字段排序问题（附修改后代码）

Hey there! I see you're struggling with getting a dual-model form (for Django's built-in User and your custom Profile) working properly, since your previous approach didn't pan out. Let's start by cleaning up and completing your model setup first, then walk through a reliable way to handle both forms in one submission.

Step 1: Complete Your Model & Signal Setup #

First, let's finish that create_profile signal you started—this ensures a Profile is automatically created whenever a new User is added (though we'll also handle form submissions manually to avoid conflicts):

# models.py
from django.db import models
from django.contrib.auth.models import User
from django.db.models.signals import post_save
from django.dispatch import receiver

class Profile(models.Model):
    user = models.OneToOneField(User, on_delete=models.CASCADE, related_name='profile')
    location = models.CharField(max_length=30, blank=True)
    birth_date = models.DateField(null=True, blank=True)

    def __str__(self):
        return self.user.username

# Signal to auto-create Profile when User is created
@receiver(post_save, sender=User)
def create_profile(sender, instance, created, **kwargs):
    if created:
        Profile.objects.create(user=instance)

@receiver(post_save, sender=User)
def save_profile(sender, instance, **kwargs):
    instance.profile.save()

Step 2: Build the Dual Forms #

Next, we'll create two forms: one for the User model, and one for the Profile. We'll exclude the user field from the Profile form since we'll link it manually to the newly created User:

# forms.py
from django import forms
from django.contrib.auth.models import User
from .models import Profile

class UserForm(forms.ModelForm):
    class Meta:
        model = User
        fields = ('username', 'email', 'first_name', 'last_name')

class ProfileForm(forms.ModelForm):
    class Meta:
        model = Profile
        exclude = ('user',)  # We'll set this in the view

Step 3: Handle Form Submission in the View #

Now, let's write a view that handles both forms at once. We'll check if both forms are valid, save the User first, then link and save the Profile:

# views.py
from django.shortcuts import render, redirect
from .forms import UserForm, ProfileForm

def register(request):
    if request.method == 'POST':
        user_form = UserForm(request.POST)
        profile_form = ProfileForm(request.POST)
        
        if user_form.is_valid() and profile_form.is_valid():
            # Save the User first
            user = user_form.save()
            # Link the Profile to the new User and save
            profile = profile_form.save(commit=False)
            profile.user = user
            profile.save()
            # Redirect to login or dashboard
            return redirect('login')
    else:
        user_form = UserForm()
        profile_form = ProfileForm()
    
    return render(request, 'register.html', {
        'user_form': user_form,
        'profile_form': profile_form
    })

Step 4: Update Your Template #

Finally, create a template that renders both forms inside a single <form> tag (make sure both forms use the same POST method and CSRF token):

<!-- templates/register.html -->
<form method="post">
    {% csrf_token %}
    <h3>User Information</h3>
    {{ user_form.as_p }}
    
    <h3>Profile Information</h3>
    {{ profile_form.as_p }}
    
    <button type="submit">Register</button>
</form>

Common Pitfalls to Avoid #

• Forgetting commit=False: When saving the Profile form, always use commit=False first so you can assign the user field before saving to the database.
• Signal Conflicts: If you're manually creating the Profile in the view, the signal will still trigger—but that's okay, it just ensures a Profile exists even if the form submission fails (no harm done).
• Validation Errors: Make sure to display form errors in your template if either form is invalid. You can add something like this under each form:

  {% if form.errors %}
      <div class="alert alert-danger">
          {% for field in form %}
              {% for error in field.errors %}
                  <p>{{ field.label }}: {{ error }}</p>
              {% endfor %}
          {% endfor %}
      </div>
  {% endif %}
  

This approach should resolve the issues you were having with your dual-model form setup. Let me know if you run into any specific errors or edge cases!

内容的提问来源于stack exchange，提问作者Boidot