I inserted this code in Custom CSS code under Styles and Colors, and cleared the comment cache, but it didn't seem to take.

#wpdcom .wpd-comment .wpd-comment-wrap {
background-color: #fbbea0 !important;
border: 1px solid #f45d11 !important;
}

Any help would be appreciated.

For reference, here is a page on the site that has a comment with 4 upvotes (about 8 comments in by vulpesvulpes): https://launch-angle.com/2026/04/03/moonshot-astros-at-athletics-4-3-26-840-ct-game-7-thread-and-discussion/

I'm using the Article Inline Feedback feature, and I've run into a logical inconsistency that I hope you can clarify.

In my Default Form settings, the Email field is set to "Required." However, in the Inline Feedback pop-up, guests can still post comments without providing an email address. The system then generates a random temporary email (like xxxx@example.com) for them.

My concern is this: > Right below the comment box, there is a "Notify me via email when a new reply is posted" checkbox. If the email field isn't mandatory, how is this feature supposed to work for guests? It seems like a broken user experience if they opt-in for notifications but the system never collected their real address.

Is there a specific setting to force Email as Required specifically for the Inline Feedback module? I've checked General Settings and User Authorization, but the "optional" behavior persists.

Thanks for the great plugin otherwise!

We noticed that after visiting a translated version of the site such as en.example.com, wpDiscuz comment behavior on the original site can break because of nonce cookie conflicts.

After investigating, we found the following:

• wpDiscuz itself appears to generate its nonce cookies correctly as host-only cookies

• in wpDiscuz code, the cookies are created with an empty domain

• however, on translated subdomains using GTranslate, the AJAX response from wp-admin/admin-ajax.php is returned with rewritten Set-Cookie headers

• GTranslate changes the wpDiscuz nonce cookies to use domain=example.com, which makes them shared across the original and translated subdomains

In our case, the response headers on the translated subdomain looked like this:

• server: gtranslate

• set-cookie: wpdiscuz_nonce_...; domain=example.com; HttpOnly; SameSite=Strict

• set-cookie: wpdiscuz_nonce_exp_...; domain=example.com; SameSite=Strict

This creates a conflict because a nonce cookie generated on a translated subdomain can then interfere with the original site version.

From what we observed, wpDiscuz is not the component introducing the shared cookie domain. The issue seems to come from GTranslate rewriting the Set-Cookie headers at proxy level. Still, I wanted to report this to you in case it is useful for compatibility tracking or future documentation.

It may be helpful for other users if wpDiscuz documentation mentions that translation proxy solutions which rewrite cookie domains can cause nonce conflicts, especially with subdomain-based translated versions.

If you have any recommendation for this kind of setup, I would be glad to hear it.

Thank you.

And this applies to everyone (Admin, moderator, or member).
I've looked in the WpDiscuz settings, without success.
I've also cleared the site cache using "WP Fattest Cache" and the Firefox cache.
I'm a complete newbie.
Can anyone help me?
Thank you.

Rolling back to 7.6.47 fixed the problem for all registered users.  We had previously noticed that guests were unable to like comments after a major WordPress update, possibly in 2025 - this was despite the setting allowing guests to rate comments being turned on.  We chose not to submit a report on this feature breakage for guests until now, since it was more of a WP core issue at that time.

Please note that we do not have JetPack installed, but we did add your suggested code snippet to disregard nonces for guests, since some users and especially guests seemed to experience the red nonce warnings.  With 7.6.48, the red message dialog was the same for both registered users and guests, that they were not allowed to vote.

Thank you in advance for looking at this.

)
(See attached image).

And this applies to everyone (Admin, moderator, or member).
I've looked in the WpDiscuz settings, without success.
I've also cleared the site cache using "WP Fattest Cache" and the Firefox cache.
I'm a complete newbie.
Can anyone help me?
Thank you.

Sir, is it possible for me to use the old comment form and the new comment section together?
See Attachment...

I would like to report a possible bug in wpDiscuz. When a visitor tries to rate a post as a guest (not logged in), the system shows the message “You cannot vote for your own comment.” However, the user is not voting on their own comment; they are simply trying to rate the post while not being logged in.

Guest ratings used to work correctly on our site, but recently this behavior changed and guests can no longer vote. The message therefore appears to be incorrect. I will also attach a screenshot of the general settings in case it helps identify the issue.

For context: the site is running behind Cloudflare.

Expected behavior: guests should be able to rate posts without being logged in, as this worked before.

Could you please check whether this is a known issue or something introduced in a recent update?

Thank you.