Node.js+MongoDB项目EJS中Cannot read property 'name' of null错误排查

Hey there, let's break down why you're hitting this error and how to fix it. The "Cannot read property 'name' of null" message tells us that somewhere in your code, you're trying to access the name property of a value that's null—almost always tied to your associated comment/post data not loading correctly. Here are the most common causes and fixes:

1. Missing or Incorrect Population of Associated Data #

MongoDB doesn't automatically load related documents (like a comment's author or a post's comments) unless you explicitly use populate(). If your template tries to access something like comment.author.name but you haven't populated the author field on comments, you'll either get an ObjectID (which has no name property) or null if the ID is invalid.

Fix Example: #

Make sure your show route populates all nested associated data correctly. For example, if your Post has comments, and each Comment links to an author:

// Correct show route with nested population
router.get('/posts/:id', async (req, res) => {
  try {
    const post = await Post.findById(req.params.id)
      .populate({
        path: 'comments',
        populate: { path: 'author' } // Populate the author inside each comment
      });
    res.render('posts/show', { post });
  } catch (err) {
    console.error(err);
    res.redirect('/');
  }
});

2. Invalid IDs in Your Seed Data #

When seeding your database, if you assign a comment (or post) to an author/post ID that doesn't exist in the corresponding collection, populate() will return null for that association. For example, if your seed script uses a random ObjectID for comment.author that isn't present in the users collection, the populated author will be null.

Fix Example: #

Ensure your seed data uses valid, existing IDs. If you're creating users, posts, and comments together, reference the actual saved documents:

// Example seed script
const user = await User.create({ name: 'Test User', email: 'test@example.com' });
const post = await Post.create({ title: 'Test Post', content: 'Hello', author: user._id });
await Comment.create({ content: 'Great post!', post: post._id, author: user._id }); // Uses valid user ID

3. No Null Checks in Your EJS Template #

Even if your data is correct, edge cases (like a comment without an author due to a bug) can lead to null values. Your EJS template should check if the object exists before accessing its properties.

Fix Example: #

Add conditional checks in your show.ejs template:

<% post.comments.forEach(comment => { %>
  <div class="comment">
    <p><%= comment.content %></p>
    <!-- Check if comment.author exists before accessing name -->
    <small>By <%= comment.author ? comment.author.name : 'Unknown User' %></small>
  </div>
<% }) %>

4. Mismatched ref Values in Your Schemas #

If your Schema's ref property doesn't exactly match the name of your Mongoose model, populate() will fail and return null. For example, if your Comment Schema uses ref: 'user' but your model is defined as mongoose.model('User', userSchema), the population won't work.

Fix Example: #

Double-check your schemas for correct ref values:

// Comment Schema
const commentSchema = new mongoose.Schema({
  content: String,
  post: {
    type: mongoose.Schema.Types.ObjectId,
    ref: 'Post' // Must match the model name (case-sensitive!)
  },
  author: {
    type: mongoose.Schema.Types.ObjectId,
    ref: 'User' // Must match the User model name
  }
});

Quick Troubleshooting Steps #

1. Open your MongoDB database (using Compass or the shell) and verify that the comments collection has valid author and post IDs that exist in the users and posts collections.
2. Log the post object in your show route (using console.log(post)) to see if the populated fields are null or missing.
3. Test your template with a conditional check first to confirm the null value is the root cause.

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