Plugin Update Issues - wpDiscuz Support Forum

Images duplicated in comments

g86439 — Wed, 25 Mar 2026 11:39:57 +0000

Since the last update (?), all images uploaded by users are shown twice in comments area. I have tried reinstalling WPDiscuz but this behavior didn't change. Is there a setting or another way to prevent images from being duplicated in comments?

Nonce is invalid error

UBweb — Sat, 14 Mar 2026 13:24:34 +0000

Dear wpDiscuz Team,

I was asked by your team to open a new thread on this forums, after the one I started on wordpress plugin support forums was not resolved.

As per the title of this thread, I am reached out by users telling me they are unable to post their comments on my website. I tried it myself as an admin, and I am getting the “Nonce is invalid” error. This is most likely goes back since mid OCTOBER 2025, as since then I was unable to see any new comments from my users.

I was offered by your team to add the below filter:

add_filter(“wpdiscuz_validate_nonce_for_guests”,”__return_false”)

I have used code snippets to add the filter, however, it did not work. Although I am not a code expert, I assume there be some function code included along to use with this filter (see attached image)

4528

Please advise how to resolve this issue, as everything was working perfectly in the past and I am not sure what step to take next ( I also searched for previous similar topics, but they were not helpful in my case).

Thank you and kind regards,

latest version of WPDiscuz . Hier: Errors in php errorlog

Nick776 — Fri, 13 Mar 2026 12:58:14 +0000

Dear Support Team,

Yesterday, we migrated to the latest version of WPDiscuz. Following the update, we found the following error message in our PHP error log:

PHP Fatal error: Uncaught Error: Class "wpdFormAttr\Form" not found in /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-content/plugins/wpdiscuz/forms/wpDiscuzForm.php:22
Stack trace:
#0 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-content/plugins/wpdiscuz/class.WpdiscuzCore.php(102): wpDiscuzForm->__construct()
#1 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-includes/class-wp-hook.php(324): WpdiscuzCore->wpdiscuzInit()
#2 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-settings.php(727): do_action()
#5 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-config.php(86): require_once('/home/w28e2juh6...')
#6 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-load.php(50): require_once('/home/w28e2juh6...')
#7 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-blog-header.php(13): require_once('/home/w28e2juh6...')
#8 /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/index.php(17): require('/home/w28e2juh6...')
#9 {main}
thrown in /home/w28e2juh6h76/webseiten/hello-world.net/wordpress/wp-content/plugins/wpdiscuz/forms/wpDiscuzForm.php on line 22

Please advise on how to proceed.

Thank you in advance,
Nico Marcuz

wpDiscuz is writing rows to WooCommerce causing major database bloat

WebWolf — Thu, 12 Mar 2026 03:58:34 +0000

We need to report a pretty significant bug that's been unknown to us until recently, that has apparently been causing significant database bloat on our site for several years. We've done extensive database testing and have pretty solid evidence of the bug.

---

We're running the latest versions of all of the plugins we use, including version 7.6.47 wpdiscuz. We are also running the latest versions of WooCommerce with Subscriptions, Memberships, and we actually only use wpDiscuz on a single, normal wordpress page for special Q&A events.

---

THE BUG

wpDiscuz is incorrectly writing _wpdiscuz_statistics rows to WooCommerce post types that have absolutely nothing to do with comments. Specifically it is writing to:

- shop_order — 61,271 rows
- wc_user_membership — 9,791 rows
- shop_subscription — 6,731 rows

Total illegitimate rows: 77,806

These post types are WooCommerce orders, memberships, and subscriptions. wpDiscuz has no business writing statistics to these records.

---

WHEN IT HAPPENS

Through database analysis we've confirmed this is NOT triggered by members submitting comments. It is triggered by WooCommerce order completion events. Every time a WooCommerce order is completed — whether a subscription renewal, new membership purchase, or product sale — wpDiscuz writes a _wpdiscuz_statistics row to that order record.

Evidence: The 5 most recent affected orders were all created March 9, 2026 at:
- 11:16 AM
- 11:51 AM
- 13:31 PM
- 14:31 PM
- 15:26 PM

All are wc-completed status orders. This confirms wpDiscuz is hooking into WooCommerce's order completion event, not the comment submission event.

---

HOW LONG THIS HAS BEEN HAPPENING

- Oldest affected record: March 29, 2015
- Most recent affected record: March 9, 2026 (today)
- Duration: over 9 years
- Growth rate: Approximately 1,000 new illegitimate rows per month
- The issue has been consistent and ongoing throughout 2023, 2024, 2025, and 2026

---

DATABASE IMPACT

- Total database size: 1.34 GB
- wp_postmeta table: 543 MB with 3.5 million rows
- _wpdiscuz_statistics is the single largest meta_key by row count in our entire wp_postmeta table
- At current growth rate this adds approximately 12,000 illegitimate rows per year

---

SQL EVIDENCE

Query confirming affected post types:
SELECT p.post_type, COUNT(*) as count FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE pm.meta_key = '_wpdiscuz_statistics' GROUP BY p.post_type ORDER BY count DESC;

Results:
shop_order: 61,271
wc_user_membership: 9,791
shop_subscription: 6,731
page: 4
ajde_events: 4
attachment: 3
post: 2

Query confirming date range:
SELECT MAX(p.post_date) as most_recent, MIN(p.post_date) as oldest FROM wp_postmeta pm JOIN wp_posts p ON pm.post_id = p.ID WHERE pm.meta_key = '_wpdiscuz_statistics';

Results:
most_recent: 2026-03-09 15:26:05
oldest: 2015-03-29 22:47:31

---

1. Is this known behavior or a confirmed bug?
2. Is there a setting to prevent wpDiscuz from writing statistics to non-comment post types?
3. Is it safe to delete all existing _wpdiscuz_statistics rows attached to shop_order, wc_user_membership, and shop_subscription post types?
4. Will a future update fix this so it stops happening?

Obviously this is causing pretty large and ongoing database bloat and should be fixed as soon as possible. You should not need access to our particular site to investigate, since this should be easily replicated if you're running widiscuz alongside WooCommerce.

Please advise!

wpDiscuz plugin stops working

tripwinego — Tue, 24 Feb 2026 01:45:47 +0000

I'm not sure what happened, but all of a sudden, comments are only appearing on the forum and not on the blog posts. I have disabled and re-abled wpDiscuz plugin a few times without luck.

Could you please help me look into this?

we are facing security problem

prabakaran — Thu, 08 Jan 2026 11:04:04 +0000

We are facing vulnerable issues. Could you please help us resolve them? We have shared the screenshots for your reference

4475

Issue with comment threading/nesting after deleting a parent comment

YA — Tue, 02 Dec 2025 01:10:30 +0000

Hello Support Team,

I am experiencing an issue with how the comment hierarchy behaves after deleting a specific comment (e.g., spam or troll).

The Problem: When a comment is deleted, the replies attached to it are being incorrectly re-assigned to the comment immediately above it (the grandparent), rather than remaining as a reply to a "deleted user" or maintaining their context. This confuses the conversation flow.

Example: Original structure:

User A (Root comment) — 2. User B (Troll/Spam) —— 3. User C (Replying to User B)

Action: I delete the comment by User B.

Current (Incorrect) Result:

User A — 3. User C

Why this is bad: User C was arguing with the Troll (User B). After deletion, it looks like User C is arguing with User A, which changes the context completely.

Expected Behavior: Previously, or normally, the reply should stay nested or show that it was a reply to a deleted participant, without shifting the parent ID to the previous commentator.

Could you please advise if there is a setting to disable this "auto-reparenting" of comments, or if this is a bug in the current version?

Thank you.

Image Preview Not Working in wpDiscuz ≥7.6.28 When Used with Elementor

Reit — Mon, 28 Jul 2025 04:38:43 +0000

Hello wpDiscuz Team,

I’m having an issue with the image upload preview feature in the comment form when using wpDiscuz along with Elementor.

What happens:

When I upload an image in the comment box, the preview does not show at all (the preview area remains empty).
However, if I submit the comment, the uploaded image does get posted successfully and appears with the comment.
This issue started happening from version 7.6.28 onwards.
If I roll back to version 7.6.27, the preview works perfectly again.
Also, if I deactivate Elementor, the preview starts working again even with the newer versions.

It seems there’s a conflict or change introduced after 7.6.27 that breaks the image preview display only when Elementor is active.

Could you please help me understand what changed that might cause this conflict, or provide guidance or a fix for compatibility with Elementor?

How to allow user to subscribe to a single thread

justinweb — Fri, 04 Jul 2025 18:38:29 +0000

The plugin description says that it is possible for users to subscribe to the comments. Unfortunately, after installing and configuring the plugin and some paid add-ons, I cannot find a way for a user to subscribe to a single thread. The user can only subscribe to all comments on this post.

Version 7.6.31 Wipes Out wpForo Default Avatars!

WebWolf — Mon, 23 Jun 2025 19:34:46 +0000

We are currently running both wpForo and wpDiscuz for a large community. We have never encountered any issues until today, when we upgraded wpDiscuz from version 7.6.30 to 7.6.31.

Immediately after doing so, all default avatars were instantly removed for users who haven't uploaded a custom one. The missing avatars appear across all wpForo pages, including the profile pages themselves.

We confirmed this issue multiple times by reproducing it. Downgrading and then upgrading again proves with 100% certainty that this avatar conflict is caused by the latest version of wpDiscuz.

We also ensured the issue isn't triggered by any custom code, CSS, themes, or other plugins. We tested it by disabling all plugins except wpForo and wpDiscuz.

In the meantime, we have rolled back to version 7.6.30.

This needs to be fixed. Please advise!