How-to and Troubleshooting - wpDiscuz Support Forum

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?

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.

Same-IP voting restriction in recent versions blocks logged-in users and breaks legitimate scenarios

DoctorBR — Thu, 27 Aug 2026 22:11:08 +0000

Description:

Hi wpDiscuz team,

I've identified a significant behavioral change introduced in newest wpDiscuz versions in the `voteOnComment()` method of `class.WpdiscuzHelperAjax.php` that causes the error "You are not allowed to vote for this comment (Voting from same IP)" to fire in cases where it shouldn't.

What changed:

In earlier versions the same-IP check in `voteOnComment()` was gated behind `!$isUserLoggedIn`:

```php

// Only guests are checked by IP

if (!$isUserLoggedIn && md5($comment->comment_author_IP) == $userIdOrIp) {

wp_send_json_error("wc_deny_voting_from_same_ip");

}

```

In v7.6.66, this condition was removed, and the check now applies to all users unconditionally, including logged-in administrators:

```php

// v7.6.66 — Everyone is checked by IP, regardless of login status

if ($comment->comment_author_IP == $userIP) {

wp_send_json_error("wc_deny_voting_from_same_ip");

} elseif ($userID && $userID == $comment->user_id) {

wp_send_json_error("wc_self_vote");

}

```

Two issues arise from this change:

1.Logged-in users should not be subject to IP-based restrictions. They are already uniquely identifiable by their `user_id`. The original logic correctly recognized this distinction. Two different registered users who happen to share the same public IP (e.g., coworkers on a corporate network) are two distinct, authenticated identities, blocking one from voting on the other's comment based solely on IP is incorrect.

2.The `elseif` structure prevents the correct error message from being displayed. When a logged-in user tries to vote on their own comment from the same IP, they receive the generic "Voting from same IP" message instead of the correct "You Cannot Vote On Your Comment" message. The IP check intercepts the request before the `user_id` self-vote check can run.

Real-world production scenarios affected:

CGNAT (Carrier-Grade NAT): Mobile carriers (4G/5G) share a single public IP among hundreds of subscribers. Two different registered users browsing via the same carrier could be blocked from voting on each other's comments.
Corporate/University networks: Employees or students behind a shared gateway IP cannot vote on each other's comments.
Misconfigured CDN/Proxy: If Cloudflare or another reverse proxy doesn't properly forward the visitor's real IP (e.g., missing `X-Forwarded-For` header), all visitors appear to have the proxy's IP.
Localhost development: All traffic originates from `127.0.0.1` or `::1`, making it impossible to test voting features locally.

Suggested fix:

Restore the `!$isUserLoggedIn` guard that existed in earlier versions, so that the IP-based restriction only applies to guests, and change the `elseif` back to a separate `if` so that the self-vote check is always evaluated independently:

```php

$userIP = WpdiscuzHelper::getRealIPAddr();

$userID = get_current_user_id();

// IP-based restriction should only apply to guests

if (!$userID && $comment->comment_author_IP == $userIP) {

wp_send_json_error("wc_deny_voting_from_same_ip");

}

// Self-vote check should always run independently for logged-in users

if ($userID && $userID == $comment->user_id) {

wp_send_json_error("wc_self_vote");

}

```

This preserves the anti-abuse intent for guests while correctly relying on `user_id` for authenticated users.

Environment:

- wpDiscuz version: 7.6.66 (free)

- WordPress version: 7.0.4

- PHP version: 8.3.30

Disclosure: This bug report was drafted with the assistance of an AI coding assistant (Antigravity/Claude) based on my manual comparison of the wpDiscuz source code between versions. The analysis, code excerpts, and suggested fix were reviewed and approved by me before posting. All described behaviors were observed and reproduced in my local development environment (WampServer64 / WordPress 7.0.4 / PHP 8.3.30).

Thank you for your time and for maintaining such a great plugin.

wpDiscuz and SiteGround

spudart — Wed, 26 Aug 2026 20:13:44 +0000

Just a heads-up for people who use wpDiscuz and SiteGround as their web host.

If you use the SiteGround Optimizer plugin, there is a setting that can cause the wpDiscuz comment fields to disappear for logged-out guests.

The setting is found at:

Speed Optimizer → Frontend → JavaScript → Combine JavaScript Files

If Combine JavaScript Files is enabled, the wpDiscuz comment fields disappear for guests. The fields still appear for logged-in users.

I confirmed that this is specifically a conflict between wpDiscuz and the Combine JavaScript Files setting. If I deactivate wpDiscuz while leaving Combine JavaScript Files enabled, the normal WordPress comment fields reappear.

So the problematic combination is:

wpDiscuz activated
SiteGround Optimizer activated
Combine JavaScript Files enabled

I tested the other JavaScript optimization settings and they do not cause this problem. These can remain enabled:

Minify JavaScript Files
Defer Render-blocking JavaScript

So, if you're using wpDiscuz with SiteGround Optimizer and your comment fields suddenly disappear for guests, check:

Speed Optimizer → Frontend → JavaScript → Combine JavaScript Files

and make sure Combine JavaScript Files is OFF.

Change "Login" Button to "Login/Register" or similar

icoholic — Tue, 04 Aug 2026 19:56:15 +0000

Hey Folks I find the "login" button a bit confusing for new sign-ups. I'd like to add "register" somehow?

Widget/Shortcode for showing user's most recent comments?

daniellerch — Fri, 24 Jul 2026 22:42:22 +0000

We are building a website that will be running wpDiscuz, wpForo, and LearnDash LMS -- so, we want users to have a single User Dashboard page where we can show them their own most recent activity from all three plugins. Is there a way to do this for wpDiscuz activity show via a shortcode or widget?

Redirect First Comment to (when e-mail field is empty)

doctorofcredit — Tue, 07 Jul 2026 01:52:24 +0000

Is it possible to get Redirect First Comment to option to work when the e-mail field is left empty?

Call to comment out of content area in Blocksy theme

MrZero — Sun, 28 Jun 2026 15:15:16 +0000

Hello, I have a little problem when I add a call to comment in content. The sentence displays out of the content area. See capture.

4560

Screen readers dont read our comments section

AdamTheForumUser — Fri, 26 Jun 2026 12:13:12 +0000

We've been told by a user that on their iPhone the screen reader doesn't read the comments section, and testing this it seems to be true.

Would this be because we have comments set to load via Ajax? Are there any recommendations you have and actions we can take to troubleshoot?

Thanks for your time
Adam

reCAPTCHA verification fails for guest comments — “Please verify that you are a human.” Post:

Adama — Thu, 18 Jun 2026 10:40:40 +0000

Hello wpDiscuz Community,

I’m having an issue with guest comments on my website.

Whenever a guest user tries to submit a comment on this page:

https://www.bachhausen.de/katherina-reiche-muss-zuruecktreten/

the Google reCAPTCHA appears and can be completed successfully. However, after clicking the submit button for the guest comment, the following error message is displayed:

“Please verify that you are a human.”

So it looks like the CAPTCHA is being solved, but wpDiscuz still does not recognize the verification when the comment is submitted.

Could you please help me understand what might cause this?
Is this likely a configuration issue with wpDiscuz, Google reCAPTCHA, caching, JavaScript optimization, or a conflict with another plugin?

I would appreciate any guidance on how to troubleshoot this.

Thank you!