求助：Django模板无法渲染Python变量contacts

Let's break down the most common reasons why your template is displaying "null" instead of the contacts value you're passing, along with actionable fixes for each scenario:

1. The contacts variable isn't being added to the template context #

This is the #1 culprit for issues like this. Double-check your view code to ensure you're explicitly passing the contacts variable into the context when rendering the template. For example:

# Correct: Include 'contacts' in the context dictionary
return render(request, 'your_template.html', {
    # ... other context variables ...
    'contacts': contacts  # Don't forget this critical line!
})

If you omit this, Django won't have access to the contacts variable in the template, so the default filter will trigger and show "null".

2. The contacts value is considered "empty" by Django's template logic #

The default filter uses Django's definition of an "empty" value to decide when to show the fallback. Even though you're converting to a string, if the resulting string is empty (e.g., str("")), or if the original contact_count converts to a falsy empty value, the default will kick in.

Add quick debug prints in your view to verify what your contacts value actually is:

print(f"Raw contact_count: {dict_data['contact_count']}")
print(f"Converted contacts string: '{contacts}'")
print(f"Is contacts considered empty? {not contacts}")

If not contacts returns True, that means Django sees the value as empty, so the default filter will display "null".

3. Typos in variable names #

It's easy to miss a small typo between your view and template. Confirm:

• The variable name in your view is exactly contacts (not contact, Contacts, or contact_counts)
• The template uses exactly {{ contacts|default:"null" }} (check for extra spaces, capitalization errors, or misspellings)

4. Unexpected exceptions altering the contacts value #

If your code hits an exception when extracting contact_count (like a KeyError if the key doesn't exist in the JSON), and you have a silent try/except block that fails to set contacts properly, this could lead to an empty or None value. For example:

try:
    dict_data = dict(json.loads(data))
    contacts = str(dict_data["contact_count"])
except:
    # If this runs without setting contacts, it may default to None
    pass

In this case, an exception would leave contacts undefined or set to None, triggering the default filter.

Quick test to isolate the issue #

To rule out context problems entirely, hardcode a value for contacts in your view:

contacts = "5"  # Hardcode a non-empty string
return render(request, 'your_template.html', {'contacts': contacts})

If the template now shows "5 spots left!", the problem lies with how you're extracting or setting the original contacts value. If it still shows "null", there's an issue with how the template receives the context (e.g., template inheritance conflicts, or the wrong view is rendering your template).

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