Django项目点击Techpost提示"No Techpost matches the given query"求助

Hey there! Let's dig into why you're hitting that frustrating error when clicking on a Techpost, even though you haven't changed anything. We'll break down the most likely causes and walk through fixes step by step.

First, Let's Understand the Error #

This error means Django's get_object_or_404 in your techpost_details view can't find a Techpost record that matches all the criteria you've specified:

• Matching slug from the URL
• Status set to published
• Publish date matching the year/month/day in the URL

Since flushing the database worked before but doesn't now, the issue is likely tied to your existing data or subtle mismatches between your URL parameters and database records.

Common Causes & Fixes #

1. Slug or Date Mismatch Between URL and Database #

The most frequent culprit is a mismatch between the values in your URL and what's stored in the database. Let's verify this first:

How to Check:

Fire up your Django shell with python manage.py shell and run this (replace the values with the ones from your problematic URL):

from rincon.models import Techpost
# Replace with your URL's parameters
year = 2024
month = 1
day = 5
slug = "your-techpost-slug"

# Run the exact query your view uses
matching_posts = Techpost.objects.filter(
    slug=slug,
    status='published',
    publish__year=year,
    publish__month=month,
    publish__day=day
)

print("Does a matching post exist?", matching_posts.exists())
print("Post details (if any):", matching_posts.values('title', 'publish', 'status', 'slug'))

If No Matches Are Found:

• Slug Issues: Slugs are case-sensitive by default. If your URL uses my-post but the database has My-Post, they won't match. Fix this by either:
  • Updating the slug in the database to match the URL, or
  • Modifying your view's query to use case-insensitive matching: slug__iexact=techpost instead of slug=techpost
• Timezone Date Mismatch: If USE_TZ = True in your settings.py, your publish field is stored as UTC time. The URL uses the local timezone's date (from get_absolute_url), which might not align with UTC. For example, a post published at 10 PM UTC might be the next day in your local timezone.
  • Fix: Generate the URL using UTC dates instead of local time:

    def get_absolute_url(self):
        publish_utc = self.publish.astimezone(timezone.utc)
        return reverse('rincon:techpost_details', args=[
            publish_utc.year,
            publish_utc.strftime('%m'),
            publish_utc.strftime('%d'),
            self.slug
        ])
    

• Status is Draft: Double-check that the post's status is set to published (not draft). You can verify this in the Django admin or via the shell query above.

2. URL Pattern or View Variable Confusion #

Looking at your code, the URL parameter for the slug is named techpost, and your view uses slug=techpost in the query. This is technically correct, but it's easy to mix up variable names.

Fix:

Make the code clearer to avoid confusion:

1. Update your urls.py to rename the slug parameter:

   path('<int:year>/<int:month>/<int:day>/<slug:slug>/', views.techpost_details, name='techpost_details'),
   

2. Update the view's parameters and query:

   @login_required
   def techpost_details(request, year, month, day, slug):
       techpost = get_object_or_404(Techpost, slug=slug, status='published', publish__year=year, publish__month=month, publish__day=day)
       # Rest of your view code stays the same
   

3. Corrupted Database Data #

Since flushing worked before, it's possible you have a corrupted or inconsistent record in your database.

Fix:

• Delete the problematic Techpost record (via admin or shell) and create a new one with a valid slug, published status, and correct publish date.
• If multiple posts are affected, consider running migrations again (though this is less likely to help if no model changes were made):

  python manage.py makemigrations
  python manage.py migrate
  

Preventive Measures #

To avoid this issue in the future:

• Auto-Generate Slugs: Set up pre-populated slugs in the Django admin to ensure consistency:

  # admin.py
  from django.contrib import admin
  from .models import Techpost
  
  class TechpostAdmin(admin.ModelAdmin):
      prepopulated_fields = {'slug': ('title',)}
      list_filter = ('status', 'publish')
  
  admin.site.register(Techpost, TechpostAdmin)
  

• Validate Slugs on Save: Add a pre-save signal to auto-generate slugs if they're missing:

  # models.py
  from django.db.models.signals import pre_save
  from django.utils.text import slugify
  
  def pre_save_techpost(sender, instance, *args, **kwargs):
      if not instance.slug:
          instance.slug = slugify(instance.title)
  
  pre_save.connect(pre_save_techpost, sender=Techpost)
  

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