求助：Django 1.8 + Python3.5开发的表单无法显示姓名、邮箱字段

Hey there! Let’s walk through the most likely reasons your name and email form fields aren’t showing up in Django 1.8 (with Python 3.5). I’ll break down checks for each of your key files:

1. Verify Your Form Definition in login/forms.py #

First, make sure your form class is correctly set up to include the name and email fields.

If you’re using a ModelForm (tied to your model), double-check:

• You’ve imported your model
• The Meta class specifies the correct model and fields
• Your model actually has name and email fields (more on that in the models section)

Example of a valid ModelForm:

from django import forms
from .models import UserProfile  # Replace with your actual model name

class LoginForm(forms.ModelForm):
    class Meta:
        model = UserProfile
        fields = ['name', 'email']  # Explicitly list the fields to display

If you’re using a regular Form (not tied to a model), ensure you’ve defined the fields directly:

from django import forms

class LoginForm(forms.Form):
    name = forms.CharField(max_length=100, label="Your Name")
    email = forms.EmailField(label="Your Email")

2. Check Your View in login/views.py #

Your view needs to instantiate the form and pass it to the template context. A common mistake is forgetting to include the form in the context dictionary, or only handling POST requests without accounting for GET.

Correct view example:

from django.shortcuts import render
from .forms import LoginForm

def login_view(request):
    # Instantiate the form for GET requests
    form = LoginForm()
    
    # Handle POST submissions if needed
    if request.method == 'POST':
        form = LoginForm(request.POST)
        if form.is_valid():
            # Process the form data here
            pass
    
    # Always pass the form to the template
    return render(request, 'login.html', {'form': form})

Make sure the context key ('form') matches what you’re using in your template—if you use 'login_form' in the view, your template needs to reference {{ login_form }} instead.

3. Validate Your login.html Template #

Your template must correctly render the form object. The simplest way is to use Django’s built-in form renderers, but you can also render fields manually.

Using Built-in Renderers: #

<form method="POST">
    {% csrf_token %}  <!-- Don’t forget this for POST requests! -->
    {{ form.as_p }}  <!-- Renders fields in paragraph tags -->
    <!-- Or use {{ form.as_table }} for table layout, {{ form.as_ul }} for list layout -->
    <button type="submit">Submit</button>
</form>

Manual Field Rendering: #

If you’re rendering fields one by one, ensure you reference them correctly:

<form method="POST">
    {% csrf_token %}
    <div>
        {{ form.name.label_tag }}
        {{ form.name }}
        {{ form.name.errors }}
    </div>
    <div>
        {{ form.email.label_tag }}
        {{ form.email }}
        {{ form.email.errors }}
    </div>
    <button type="submit">Submit</button>
</form>

Double-check that you’re using the correct field names (name and email) that match your form definition.

4. Confirm Your Model in login/models.py (If Using ModelForm) #

If you’re using a ModelForm, your model must have the name and email fields defined. Example:

from django.db import models

class UserProfile(models.Model):
    name = models.CharField(max_length=100)
    email = models.EmailField(unique=True)
    # Add other fields as needed

If these fields are missing from the model, the ModelForm won’t generate the corresponding input fields.

5. Quick Additional Checks #

• URL Configuration: Make sure your URL pattern is pointing to the correct login_view—if the request is hitting a different view, your form won’t be passed to the template.
• Template Caching: Django 1.8 might cache templates. Try restarting your development server or clearing any template cache if you’ve made recent changes.
• Variable Name Typos: A simple typo (like {{ frm }} instead of {{ form }} in the template) can cause the form to not render.

Start with these checks—most form display issues are small oversights like missing fields in the form definition, not passing the form to the template, or incorrect template syntax. If you share snippets of your actual code, I can help pinpoint the exact issue!

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