wpDiscuz Support Forum - Recent Topics

wpDiscuz Comment Form Is Not Working: Troubleshooting Guide

Asti — Fri, 02 Oct 2026 09:08:33 +0000

If the wpDiscuz comment form is not working correctly, the issue may be caused by an outdated plugin, caching, JavaScript errors, a plugin/theme conflict, or WordPress/security settings.

Follow the steps below in order.

1. Update wpDiscuz and Clear Cache

Make sure you are using the latest version of wpDiscuz and all installed wpDiscuz addons.

After updating, clear your website, plugin, server, CDN, and browser caches. Then perform a hard refresh (Ctrl + F5) and test the comment form again.

2. Check for JavaScript Errors

JavaScript errors from your theme, another plugin, or an optimization tool can prevent wpDiscuz from working correctly.

To check:

Open the page with the wpDiscuz form.
Right-click and select Inspect.
Open the Console tab.
Reproduce the problem.

If you see errors, take a screenshot or record a short video showing the issue.

3. Check for Plugin Conflicts

Another plugin may interfere with wpDiscuz functionality.

Temporarily deactivate other plugins and test the comment form again.

If the issue disappears, activate the plugins one by one until you identify the plugin causing the conflict.

4. Check for Theme Conflicts

Temporarily switch to a default WordPress theme, such as Twenty Twenty-Six, and test the comment form again.

If the issue disappears, the problem may be related to the theme's JavaScript, CSS, or other custom functionality.

Note: If possible, perform conflict testing on a staging website so that you don't affect your live website.

5. Check Anti-Spam and Security Plugins

If comments are being rejected or cannot be submitted, check your anti-spam and security plugins, such as Akismet.

If the problem affects only certain comments or users, temporarily disable the relevant plugin and test the comment form again.

For more information, please see our guide on wpDiscuz Comment Submission, Rejection, and Moderation.

6. Check Optimization Plugins

If you use a caching or optimization plugin, temporarily disable JavaScript minification, combination, defer, or delay options and test the comment form again.

These settings can sometimes interfere with JavaScript-dependent functionality such as the wpDiscuz comment form.

7. Still Having Problems?

If the issue persists, contact our support team and provide:

The direct URL where the issue occurs
Your WordPress and wpDiscuz versions
Installed wpDiscuz addon versions
A short screen recording of the issue
Any JavaScript/Console errors
Whether the issue affects guests, logged-in users, or both

This information will help us investigate the issue more efficiently.

Comments not appearing in front end

Manager Prinovix — Tue, 29 Sep 2026 16:08:32 +0000

When one comments it correctly takes time and displays comment in comment section. But then in the same instance when same person to the same post posts another comment in the backend it actually gets recived but in front end its not shown. I dont have cache enabled.. should i enable it?

Do heavily commented wpDiscuz threads impact site crawl and authority metrics?

hamzareads — Mon, 28 Sep 2026 16:39:03 +0000

Hi everyone, I have been running wpDiscuz on my WordPress site for a few months now, and while community engagement has improved, I have run into a concerning issue regarding how search engines handle long discussion threads. Our posts have become quite resource-heavy due to extensive user replies, and I am worried that user-submitted links within the threads might be negatively influencing our search visibility.

While auditing our site performance and checking our dapascoreover the past couple of weeks, I noticed an unexpected drop right around the time several comment-heavy posts started ranking for secondary keywords. This got me wondering whether the default nofollow and link handling configurations inside wpDiscuz are sufficient to prevent crawlers from penalizing pages with numerous low-quality external references.

Has anyone else noticed crawl budget issues or metric fluctuations after scaling up active discussions? I would really appreciate any insights on how to balance wpDiscuz pagination, link attributes, and comment loading to protect site authority while keeping active community interactions.

View comment statistics by specified date range

daniellerch — Fri, 25 Sep 2026 18:58:01 +0000

I see the 'Comment Statistic' box, which allows me to select e.g. "Last Week", "Last Month," etc. But we do monthly and quartelry reporting, so I need to be able to view the number of comments (and replies) by e.g. a specific month, or a date range that I specify. Is there a way to do this?

wpDiscuz Comments: Submission, Rejection, and Moderation

Asti — Wed, 16 Sep 2026 10:35:36 +0000

If your comment is not published and you see the “Your comment was not published” message, the comment may have been classified as spam or trash. Below, we explain how wpDiscuz handles these submissions and answer the most common questions.

Why does my comment say "Your comment was not published"?

This message usually means that WordPress or a moderation/anti-spam plugin stored your comment as spam or trash instead of placing it in the pending-approval queue.

If you believe your comment was rejected by mistake, please contact the site owner.

Does "Your comment was not published" mean that my comment is awaiting approval?

No. This message normally means that the comment was stored as spam or trash, not as a comment awaiting approval.

What happens when my comment is awaiting approval?

If your comment is placed in the pending-approval queue, wpDiscuz displays your comment with an "Awaiting for approval" label.

The comment is visible to you, but other visitors cannot see it until it is approved.

Will I lose my comment if it is rejected?

Normally, no. wpDiscuz keeps your comment text and form fields in place so you can review or copy them.

However, we recommend keeping the page open until you have copied your text. Reloading or leaving the page may cause the entered information to be lost.

Why does the same message appear when I submit my comment again?

If WordPress detects that the comment is a duplicate of a comment already stored as spam, wpDiscuz normally displays "Your comment was not published" again without storing another copy.

If a moderation plugin provided a more detailed explanation, that explanation may only be available during the first submission.

Why am I seeing a different error message?

The exact message can depend on WordPress, wpDiscuz, or another moderation/security plugin.

Site owners can also customize wpDiscuz's spam and trash messages.

Does this behavior also apply to replies?

Yes. The same rejection behavior applies to main comments and replies.

If WordPress stores the submission as spam or trash, wpDiscuz displays a rejection response.

Does this apply to inline feedback?

Yes. Inline feedback follows the same rejection behavior when WordPress stores the submission as spam or trash.

When inline feedback is successfully submitted, the wpDiscuz displays the usual "Thank you for your feedback!" message.

What should I check if legitimate comments are being rejected?

If legitimate comments are being rejected, the site owner should check:

WordPress > Comments, including the Spam and Trash folders.
WordPress Discussion and comment moderation settings.
Active anti-spam and moderation plugins.
Any caching that may be serving outdated pages or forms.

wpDiscuz 7.6.71 also improved compatibility with anti-spam fields in main, reply, and inline-feedback forms.

Can I change the "Your comment was not published" message?

Yes. The default rejection wording can be changed in the wpDiscuz > Phrases > Errors admin page.

If the site uses PO/MO translation files, these strings should instead be managed through the translation files.

For more information, see the wpDiscuz translation guide.

Where can I learn more about WordPress comment moderation?

You can review the WordPress comment moderation settings in the wpDiscuz comment moderation documentation.

"This comment is not acceptable" for answers for non members

MrZero — Mon, 14 Sep 2026 10:02:15 +0000

Hello, when a non member try to answer to a comment, the message "This comment is not acceptable." is showing.

The problem does not occur:

when commenting directly;
when answering as admin.

If I try a Crtl+F5 and try to republish, I have a warning saying it’s a double comment. But there is no trace of the comment in admin.

I made some tests deactivating La Sentinelle AntiSpam and NinjaFirewall without effect.

Live-update notification (bubble) never notifies two guest commenters when both leave the comment author email field blank

wpdiscuzuser2258 — Sat, 12 Sep 2026 04:49:10 +0000

wpDiscuz version: 7.6.69
Environment: WordPress (ClassicPress-based), PHP, LiteSpeed server, no caching plugin active

Summary:
The bubble/live-update REST endpoint (wp-json/wpdiscuz/v1/update) never returns
newly posted comments in its "ids" field when two different guest visitors post
comments without filling in an email address. The overall "all_comments_count"
does update correctly, but the "ids" array (which drives the notification
bubble/toast) stays empty forever for these visitors, even though the new
comments are approved and clearly exist with a higher comment_ID than the
client's lastId.

Root cause (found by reading includes/class.WpdiscuzDBManager.php):
getNewCommentIds() builds its query with:

... AND `comment_ID` > %d AND `comment_author_email` != %s ...

where %s is the requesting visitor's own email (from $_COOKIE
"comment_author_email_" . COOKIEHASH, or the logged-in user's email).
This is meant to exclude a visitor's own comments from their own
notification feed. However, when a guest commenter does not enter an
email address, comment_author_email is stored as an empty string (‘’).
If a SECOND, completely different guest visitor also leaves the email
field blank, their request also sends email = ''. The exclusion filter
then matches "comment_author_email != ''" as FALSE for the other
visitor's new comment (because it also equals ''), so that comment is
incorrectly treated as "my own" and excluded from `ids` — even though
it was posted by a different person in a different browser.

Steps to reproduce:
1. Open the same post in two different browsers/profiles as two
different anonymous guests (not logged in).
2. In both, submit a comment WITHOUT filling in an email address
(only a display name).
3. Wait for the bubble's live-update poll (wp-json/wpdiscuz/v1/update)
to fire in either browser.
4. Observe: `all_comments_count` increases correctly, but `ids` and
the notification bubble/toast never show the other guest's new
comment — because both share the same blank email identity.
5. For comparison, if one of the two commenters is logged in (so their
email is a real, distinct value), notifications work correctly in
both directions.

Expected behavior:
Two different guest visitors who both leave the email field blank
should still be notified of each other's new comments — an empty
email should not be treated as a shared "identity" for the
self-exclusion filter. Suggested fix: only apply the
`comment_author_email != %s` exclusion when the requester's email is
non-empty, or use a more reliable per-visitor identifier (e.g. a
random per-session cookie/nonce) instead of email for this
self-exclusion check.

Impact:
On a public site where many visitors comment as anonymous guests
without an email address, this silently breaks the live comment
notification feature for a large share of real visitors, not just in
a synthetic multi-browser test.

Happy to share captured network requests/responses (from Chrome
DevTools/Firefox DevTools) and the exact wp_comments rows (comment_ID,
comment_author, comment_author_email) that reproduce this if useful.

Whitelisting commenters

daniellerch — Fri, 11 Sep 2026 00:01:52 +0000

Following up on this thread from 3 years ago: https://wpdiscuz.com/community/troubleshooting/whitelisting/#post-21326

I'm interested in a way for my comment moderators to whitelist users either automatically after a certain number of approved posts, or manually from either wpDiscuz Settings in the backend or the wpDiscuz Frontend Moderatoin add-on. (We use volunteer moderators on our site, so they don't have access to Settings > Discussion.) Is there an option for this?

Nonce invalid when marking comment as sticky

SkoposConnect — Mon, 07 Sep 2026 14:38:35 +0000

When I go to /wp-admin/edit-comments.php and set a comment as "sticky", the loader icon appears and does not stop and the JS console shows "Nonce is invalid." See screenshot.

I was able to reproduce this behavior on a productive Wordpress Site with wpdiscuz Version 7.6.68 as well as a locally run Wordpress Site where I deactivated all other plugins.

I already did:

As mentioned: deactivate all other plugins.
As mentioned: updated to most recent Version 7.6.68
Check if "Use WordPress native AJAX functions" is activated -> Is activated.
Reset Cache with "Purge Comment and User Caches" -> Resetted.

Please let me know if you need more information to solve this.

Thanks

How to get latest Google icon to show in social login

cdsingalong — Sun, 06 Sep 2026 17:09:12 +0000

Hi.

The social login function displays the old (red) Google icon even though the wpDiscuz Social Login settings page has the updated (color) icon.

I have the "Load Font Awesome css lib" option selected under Styles and Colors. Unselecting and/or reselecting it doesn't help.

An AI agent suggested the following code (where the url points to an uploaded version of the new Google icon) but it doesn't work (still shows old icon):

/* Hide old Google icon and replace */
.wpd-social-login-google svg,
.wpd-login-provider-google i {
display: none; /* Hide old icon */
}

.wpd-social-login-google:before {
content: "";
display: inline-block;
width: 18px;
height: 18px;
background: url("https://mydomain.com/.../Google-New-Logo.png") no-repeat center center;
background-size: contain;
}

How can I get the new Google icon to display for users? People are starting to forget that the old red one even refers to Google, LOL.

Thanks.