A simple database cleanup query can restore missing WooCommerce product reviews caused by orphaned metadata from deleted user accounts. For a permanent solution, implement a function to properly clean up this data upon user deletion.

So, Your Product Reviews Vanished? A DevOps War Story.

I remember the call. It was a Tuesday, just after the big holiday campaign launch. The PagerDuty alert was cryptic: “High Abandoned Cart Rate.” The marketing lead was already on Slack, firing off question marks like they were going out of style. We dug in, and the issue was bizarre: all product reviews, every single star rating, had vanished from the shop. The products looked naked, untrustworthy. It wasn’t a cache issue, not a deployment bug… it was a ghost in the database. A problem that looks terrifying on the surface but, once you’ve seen it, is something you’ll spot from a mile away. This exact scenario popped up on a Reddit thread recently, and I felt that old familiar twitch. Let’s get you sorted.

The “Why”: The Ghost of Users Past

So, what’s actually happening here? This isn’t a random bug; it’s a data integrity problem. In the world of WordPress and WooCommerce, a product review is fundamentally a ‘comment’ with extra data—specifically, a star rating. This rating is stored in a separate table called wp_commentmeta.

The problem starts when an administrator deletes a user account from WordPress. Sometimes, and particularly if a buggy plugin is involved or the process is interrupted, the user’s reviews (comments) are deleted, but the associated star ratings (comment metadata) are left behind. These are called “orphans.”

Now, when WooCommerce tries to fetch the reviews for a product, its database query hits this orphaned rating data. It sees a rating but can’t find the parent comment it belongs to. The query chokes, fails silently, and returns… nothing. Poof. Your reviews are gone, all because the database is trying to make sense of ghosts.

Fixing the Phantom: Three Levels of Engagement

Alright, enough theory. The marketing team doesn’t care about `LEFT JOIN`s; they just want the five-star reviews for the “SuperMegaWidget 3000” back online. We have a few ways to tackle this, from a quick-and-dirty fix to a proper long-term solution.

Solution 1: The “Get It Working NOW” Fix (Direct SQL)

This is the battlefield medic approach. It’s fast, effective, and a little bit dirty. We’re going to dive directly into the database on prod-db-01 and surgically remove the orphaned metadata. It’s the most common way to solve this fast.

WARNING: You are about to directly manipulate a production database. TAKE A DATABASE BACKUP. NOW. I am not kidding. Run a `mysqldump` or use your cloud provider’s snapshot feature. Do not skip this step.

SSH into your server, get a MySQL prompt, and run this query. This command finds all entries in wp_commentmeta that don’t have a matching entry in the wp_comments table and deletes them.

DELETE FROM wp_commentmeta WHERE comment_id NOT IN (SELECT comment_ID FROM wp_comments);

In 99% of cases, after running this and clearing your site’s cache, your reviews will magically reappear. You just exorcised the ghosts. Grab a coffee; you’ve earned it. But remember, this is a patch, not a cure. The problem can come back.

Solution 2: The “Let’s Do This Right” Permanent Fix

A senior engineer doesn’t just fix the problem; they prevent it from happening again. The root cause is an incomplete data cleanup process. We can enforce that cleanup by hooking into WordPress’s user deletion process.

You can add a function to your theme’s functions.php file or, better yet, a custom site plugin. This code ensures that when a user is deleted, we run our cleanup query for that specific user’s comments first, preventing orphans from ever being created.

// Add this to your functions.php or a custom plugin
add_action( 'delete_user', 'techresolve_cascade_delete_comment_meta' );

function techresolve_cascade_delete_comment_meta( $user_id ) {
    global $wpdb;

    // Get all comment IDs for the user being deleted
    $comment_ids = $wpdb->get_col( $wpdb->prepare(
        "SELECT comment_ID FROM {$wpdb->comments} WHERE user_id = %d",
        $user_id
    ) );

    if ( ! empty( $comment_ids ) ) {
        // Prepare the comment IDs for the IN clause
        $comment_ids_in = implode( ',', array_map( 'absint', $comment_ids ) );
        
        // Delete from commentmeta table where comment_id is one of the user's comments
        $wpdb->query( "DELETE FROM {$wpdb->commentmeta} WHERE comment_id IN ( {$comment_ids_in} )" );
    }
}

This is the professional’s choice. It respects the application’s flow, it’s targeted, and it inoculates you against future incidents of the same type. This is the kind of code you can commit to the repo with confidence.

Solution 3: The “Scorched Earth” Nuclear Option

Let’s say things are really, really bad. Maybe you’ve had multiple plugins messing with the database, and the data is a complete mess. The quick fix didn’t work, and you suspect deeper corruption. It’s time to consider the nuclear option: a full review wipe and re-import.

Pro Tip: This is a last resort. It involves potential data loss and downtime. You should only attempt this if you have a clean, verifiable export of all your legitimate product reviews. Your standard database backup counts, but a clean CSV export is even better.

The process looks something like this:

1. Export: Use a plugin like “Product Reviews Import Export for WooCommerce” to export all existing (and hopefully valid) reviews to a CSV file. Manually inspect this file for sanity.
2. Truncate: Take a deep breath. Back up your database again. Then, run these SQL commands to wipe the slate clean.

   
   TRUNCATE TABLE wp_comments;
   TRUNCATE TABLE wp_commentmeta;
   

3. Re-sync Counts: WooCommerce caches the review counts on the product itself. You need to tell it to recount.

   
   DELETE FROM wp_postmeta WHERE meta_key = '_wc_review_count';
   DELETE FROM wp_postmeta WHERE meta_key = '_wc_rating_count';
   

4. Import: Use the same plugin to re-import the reviews from your clean CSV file.
5. Verify: Clear all caches and check the front end. WooCommerce will recount the reviews upon visiting the product pages.

This is messy and high-risk, but sometimes it’s the only way to be sure you’ve cleared out years of accumulated database cruft.

Comparing The Approaches

Here’s a quick breakdown to help you decide which path to take.

In the end, that 2 AM incident was solved with the quick SQL fix. But you can bet that the permanent code fix was in the very next sprint plan. You don’t get woken up by the same ghost twice. Not on my watch.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions