<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									wpDiscuz Support Forum - Recent Topics				            </title>
            <link>https://wpdiscuz.com/community/</link>
            <description>wpDiscuz WordPress Comment Plugin Community. Support and Resources.</description>
            <language>en-US</language>
            <lastBuildDate>Mon, 14 Sep 2026 00:37:24 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Live-update notification (bubble) never notifies two guest commenters when both leave the comment author email field blank</title>
                        <link>https://wpdiscuz.com/community/bug-reports/live-update-notification-bubble-never-notifies-two-guest-commenters-when-both-leave-the-comment-author-email-field-blank/</link>
                        <pubDate>Sat, 12 Sep 2026 04:49:10 +0000</pubDate>
                        <description><![CDATA[wpDiscuz version: 7.6.69Environment: WordPress (ClassicPress-based), PHP, LiteSpeed server, no caching plugin activeSummary:The bubble/live-update REST endpoint (wp-json/wpdiscuz/v1/update) ...]]></description>
                        <content:encoded><![CDATA[<p>wpDiscuz version: 7.6.69<br />Environment: WordPress (ClassicPress-based), PHP, LiteSpeed server, no caching plugin active<br /><br />Summary:<br />The bubble/live-update REST endpoint (wp-json/wpdiscuz/v1/update) never returns<br />newly posted comments in its "ids" field when two different guest visitors post<br />comments without filling in an email address. The overall "all_comments_count"<br />does update correctly, but the "ids" array (which drives the notification<br />bubble/toast) stays empty forever for these visitors, even though the new<br />comments are approved and clearly exist with a higher comment_ID than the<br />client's lastId.<br /><br />Root cause (found by reading includes/class.WpdiscuzDBManager.php):<br />getNewCommentIds() builds its query with:<br /><br />... AND `comment_ID` &gt; %d AND `comment_author_email` != %s ...<br /><br />where %s is the requesting visitor's own email (from $_COOKIE<br />"comment_author_email_" . COOKIEHASH, or the logged-in user's email).<br />This is meant to exclude a visitor's own comments from their own<br />notification feed. However, when a guest commenter does not enter an<br />email address, comment_author_email is stored as an empty string (‘’).<br />If a SECOND, completely different guest visitor also leaves the email<br />field blank, their request also sends email = ''. The exclusion filter<br />then matches "comment_author_email != ''" as FALSE for the other<br />visitor's new comment (because it also equals ''), so that comment is<br />incorrectly treated as "my own" and excluded from `ids` — even though<br />it was posted by a different person in a different browser.<br /><br />Steps to reproduce:<br />1. Open the same post in two different browsers/profiles as two<br />different anonymous guests (not logged in).<br />2. In both, submit a comment WITHOUT filling in an email address<br />(only a display name).<br />3. Wait for the bubble's live-update poll (wp-json/wpdiscuz/v1/update)<br />to fire in either browser.<br />4. Observe: `all_comments_count` increases correctly, but `ids` and<br />the notification bubble/toast never show the other guest's new<br />comment — because both share the same blank email identity.<br />5. For comparison, if one of the two commenters is logged in (so their<br />email is a real, distinct value), notifications work correctly in<br />both directions.<br /><br />Expected behavior:<br />Two different guest visitors who both leave the email field blank<br />should still be notified of each other's new comments — an empty<br />email should not be treated as a shared "identity" for the<br />self-exclusion filter. Suggested fix: only apply the<br />`comment_author_email != %s` exclusion when the requester's email is<br />non-empty, or use a more reliable per-visitor identifier (e.g. a<br />random per-session cookie/nonce) instead of email for this<br />self-exclusion check.<br /><br />Impact:<br />On a public site where many visitors comment as anonymous guests<br />without an email address, this silently breaks the live comment<br />notification feature for a large share of real visitors, not just in<br />a synthetic multi-browser test.<br /><br />Happy to share captured network requests/responses (from Chrome<br />DevTools/Firefox DevTools) and the exact wp_comments rows (comment_ID,<br />comment_author, comment_author_email) that reproduce this if useful.</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>wpdiscuzuser2258</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/bug-reports/live-update-notification-bubble-never-notifies-two-guest-commenters-when-both-leave-the-comment-author-email-field-blank/</guid>
                    </item>
				                    <item>
                        <title>Whitelisting commenters</title>
                        <link>https://wpdiscuz.com/community/troubleshooting/whitelisting-commenters/</link>
                        <pubDate>Fri, 11 Sep 2026 00:01:52 +0000</pubDate>
                        <description><![CDATA[Following up on this thread from 3 years ago:
I&#039;m interested in a way for my comment moderators to whitelist users either automatically after a certain number of approved posts, or manually ...]]></description>
                        <content:encoded><![CDATA[<p>Following up on this thread from 3 years ago: https://wpdiscuz.com/community/troubleshooting/whitelisting/#post-21326</p>
<p>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 &gt; Discussion.) Is there an option for this?</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>daniellerch</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/troubleshooting/whitelisting-commenters/</guid>
                    </item>
				                    <item>
                        <title>Nonce invalid when marking comment as sticky</title>
                        <link>https://wpdiscuz.com/community/bug-reports/nonce-invalid-when-marking-comment-as-sticky/</link>
                        <pubDate>Mon, 07 Sep 2026 14:38:35 +0000</pubDate>
                        <description><![CDATA[When I go to /wp-admin/edit-comments.php and set a comment as &quot;sticky&quot;, the loader icon appears and does not stop and the JS console shows &quot;Nonce is invalid.&quot; See screenshot. 
I was able to...]]></description>
                        <content:encoded><![CDATA[<p>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. </p>
<p>I was able to reproduce this behavior on a productive Wordpress Site with wpdiscuz <span>Version 7.6.68 as well as a locally run Wordpress Site where I deactivated all other plugins.</span></p>
<p>I already did:</p>
<ul>
<li>As mentioned: deactivate all other plugins.</li>
<li>As mentioned: updated to most recent <span>Version 7.6.68</span></li>
<li>Check if "<span>Use WordPress native AJAX functions" is activated -&gt; Is activated.</span></li>
<li>Reset Cache with "<span>Purge Comment and User Caches" -&gt; Resetted.</span></li>
</ul>
<p>Please let me know if you need more information to solve this.</p>
<p>Thanks</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>SkoposConnect</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/bug-reports/nonce-invalid-when-marking-comment-as-sticky/</guid>
                    </item>
				                    <item>
                        <title>How to get latest Google icon to show in social login</title>
                        <link>https://wpdiscuz.com/community/troubleshooting/how-to-get-latest-google-icon-to-show-in-social-login/</link>
                        <pubDate>Sun, 06 Sep 2026 17:09:12 +0000</pubDate>
                        <description><![CDATA[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 &quot;Load Font Awesome css lib&quot; op...]]></description>
                        <content:encoded><![CDATA[<p>Hi.</p>
<p>The social login function displays the old (red) Google icon even though the wpDiscuz Social Login settings page has the updated (color) icon.</p>
<p>I have the "Load Font Awesome css lib" option selected under Styles and Colors. Unselecting and/or reselecting it doesn't help.</p>
<p>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):</p>
<p>/* Hide old Google icon and replace */<br />.wpd-social-login-google svg, <br />.wpd-login-provider-google i {<br />display: none; /* Hide old icon */<br />}<br /><br />.wpd-social-login-google:before {<br />content: "";<br />display: inline-block;<br />width: 18px;<br />height: 18px;<br />background: url("https://mydomain.com/.../Google-New-Logo.png") no-repeat center center;<br />background-size: contain;<br />}</p>
<p>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.</p>
<p>Thanks.</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>cdsingalong</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/troubleshooting/how-to-get-latest-google-icon-to-show-in-social-login/</guid>
                    </item>
				                    <item>
                        <title> Same-IP voting restriction in recent versions blocks logged-in users and breaks legitimate scenarios</title>
                        <link>https://wpdiscuz.com/community/troubleshooting/bug-feature-request-same-ip-voting-restriction-in-recent-versions-blocks-logged-in-users-and-breaks-legitimate-scenarios/</link>
                        <pubDate>Thu, 27 Aug 2026 22:11:08 +0000</pubDate>
                        <description><![CDATA[Description:

Hi wpDiscuz team,

I&#039;ve identified a significant behavioral change introduced in newest wpDiscuz versions in the `voteOnComment()` method of `class.WpdiscuzHelperAjax.php` ...]]></description>
                        <content:encoded><![CDATA[<div>
<div><strong>Description:</strong></div>
<br />
<div><span>Hi wpDiscuz team,</span></div>
<br />
<div><span>I've identified a significant behavioral change introduced in newest wpDiscuz versions in the </span><span>`voteOnComment()`</span><span> method of </span><span>`class.WpdiscuzHelperAjax.php`</span><span> that causes the error </span><span>"You are not allowed to vote for this comment (Voting from same IP)" </span><span>to fire in cases where it shouldn't.</span></div>
<br />
<div><strong>What changed:</strong></div>
<br />
<div><span>In earlier versions the same-IP check in </span><span>`voteOnComment()`</span><span> was </span>gated behind <span>`!$isUserLoggedIn`</span><span>: <br /></span></div>
<div> </div>
<div><span>```php</span></div>
<div><span>// Only guests are checked by IP</span></div>
<div><span>if</span><span> (!$isUserLoggedIn &amp;&amp; </span><span>md5</span><span>($comment-&gt;comment_author_IP) == $userIdOrIp) {</span></div>
<div><span>    wp_send_json_error(</span><span>"wc_deny_voting_from_same_ip"</span><span>);</span></div>
<div><span>}</span></div>
<div><span>```</span></div>
<div> </div>
<br />
<div><span>In </span><span>v7.6.66</span><span>, this condition was removed, and the check now applies to </span><span><strong>all users unconditionally</strong></span><span>, including logged-in administrators:</span></div>
<div> </div>
<br />
<div><span>```php</span></div>
<div><span>// v7.6.66 — Everyone is checked by IP, regardless of login status</span></div>
<div><span>if</span><span> ($comment-&gt;comment_author_IP == $userIP) {</span></div>
<div><span>    wp_send_json_error(</span><span>"wc_deny_voting_from_same_ip"</span><span>);</span></div>
<div><span>} </span><span>elseif</span><span> ($userID &amp;&amp; $userID == $comment-&gt;user_id) {</span></div>
<div><span>    wp_send_json_error(</span><span>"wc_self_vote"</span><span>);</span></div>
<div><span>}</span></div>
<div><span>```</span></div>
<div> </div>
<br />
<div><span><strong>Two issues arise from this change:</strong></span></div>
<br />
<div><span>1.</span><span><strong>Logged-in users should not be subject to IP-based restrictions. </strong></span><span>They are already uniquely identifiable by their </span><span>`user_id`</span><span>. 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.</span></div>
<br />
<div><span>2.</span><strong>The `elseif`</strong><span><strong> structure prevents the correct error message from being displayed. </strong></span><span>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 </span><span>`user_id`</span><span> self-vote check can run.</span></div>
<br />
<div><span><strong>Real-world production scenarios affected:</strong></span></div>
<br />
<ul>
<li><span><strong>CGNAT (Carrier-Grade NAT): </strong></span><span>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. </span></li>
<li><span><span><strong>Corporate/University networks: </strong><span>Employees or students behind a shared gateway IP cannot vote on each other's comments. </span></span></span></li>
<li><span><span><strong>Misconfigured CDN/Proxy: </strong><span>If Cloudflare or another reverse proxy doesn't properly forward the visitor's real IP (e.g., missing <span>`X-Forwarded-For`<span> header), all visitors appear to have the proxy's IP.</span></span></span></span></span></li>
<li><span><span><strong>Localhost development: </strong><span>All traffic originates from <span>`127.0.0.1`<span> or <span>`::1`<span>, making it impossible to test voting features locally.</span></span></span></span></span></span></span></li>
</ul>
<br />
<div><span><strong>Suggested fix: </strong></span></div>
<br />
<div><span>Restore the </span><span>`!$isUserLoggedIn`</span><span> guard that existed in earlier versions, so that the IP-based restriction only applies to </span><span><strong>guests</strong></span><span>, and change the </span><span>`elseif`</span><span> back to a separate </span><span>`if`</span><span> so that the self-vote check is always evaluated independently:</span></div>
<div> </div>
<br />
<div><span>```php</span></div>
<div><span>$userIP = WpdiscuzHelper::getRealIPAddr();</span></div>
<div><span>$userID = get_current_user_id();</span></div>
<br />
<div><span>// IP-based restriction should only apply to guests</span></div>
<div><span>if</span><span> (!$userID &amp;&amp; $comment-&gt;comment_author_IP == $userIP) {</span></div>
<div><span>    wp_send_json_error(</span><span>"wc_deny_voting_from_same_ip"</span><span>);</span></div>
<div><span>}</span></div>
<br />
<div><span>// Self-vote check should always run independently for logged-in users</span></div>
<div><span>if</span><span> ($userID &amp;&amp; $userID == $comment-&gt;user_id) {</span></div>
<div><span>    wp_send_json_error(</span><span>"wc_self_vote"</span><span>);</span></div>
<div><span>}</span></div>
<div><span>```</span></div>
<div> </div>
<br />
<div><span>This preserves the anti-abuse intent for guests while correctly relying on </span><span>`user_id`</span><span> for authenticated users.</span></div>
<div> </div>
<br />
<div><strong>Environment:</strong></div>
<div><span>-</span><span> wpDiscuz version: 7.6.66 (free)</span></div>
<div><span>-</span><span> WordPress version: 7.0.4</span></div>
<div><span>-</span><span> PHP version: 8.3.30</span></div>
<div> </div>
<br />
<div> </div>
<div><hr /></div>
<div> </div>
<div><span><strong>Disclosure: </strong></span><span>This bug report was drafted with the assistance of an AI coding </span><span>assistant (Antigravity/Claude) based on my manual comparison of the wpDiscuz source </span><span>code between versions. The analysis, code excerpts, and suggested </span><span>fix were reviewed and approved by me before posting. All described behaviors were </span><span>observed and reproduced in my local development environment </span><span>(WampServer64 / WordPress 7.0.4 / PHP 8.3.30). </span></div>
<div> </div>
</div>
<div><hr /></div>
<div><br />
<div> </div>
<div><span>Thank you for your time and for maintaining such a great plugin.</span></div>
<div> </div>
<div> </div>
</div>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>DoctorBR</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/troubleshooting/bug-feature-request-same-ip-voting-restriction-in-recent-versions-blocks-logged-in-users-and-breaks-legitimate-scenarios/</guid>
                    </item>
				                    <item>
                        <title>wpDiscuz and SiteGround</title>
                        <link>https://wpdiscuz.com/community/troubleshooting/wpdiscuz-and-siteground/</link>
                        <pubDate>Wed, 26 Aug 2026 20:13:44 +0000</pubDate>
                        <description><![CDATA[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 di...]]></description>
                        <content:encoded><![CDATA[<p class="" data-start="265" data-end="350">Just a heads-up for people who use <strong data-start="300" data-end="312">wpDiscuz</strong> and <strong data-start="317" data-end="331">SiteGround</strong> as their web host.</p>
<p data-start="352" data-end="497">If you use the <strong data-start="367" data-end="391">SiteGround Optimizer</strong> plugin, there is a setting that can cause the wpDiscuz comment fields to disappear for logged-out guests.</p>
<p data-start="499" data-end="523">The setting is found at:</p>
<p data-start="525" data-end="595"><strong data-start="525" data-end="595">Speed Optimizer → Frontend → JavaScript → Combine JavaScript Files</strong></p>
<p class="" data-start="597" data-end="735">If <strong data-start="600" data-end="628">Combine JavaScript Files</strong> is enabled, the wpDiscuz comment fields disappear for guests. The fields still appear for logged-in users.</p>
<p data-start="737" data-end="971">I confirmed that this is specifically a conflict between wpDiscuz and the <strong data-start="811" data-end="839">Combine JavaScript Files</strong> setting. If I deactivate wpDiscuz while leaving <strong data-start="888" data-end="916">Combine JavaScript Files</strong> enabled, the normal WordPress comment fields reappear.</p>
<p data-start="973" data-end="1007">So the problematic combination is:</p>
<ul data-start="1009" data-end="1101">
<li data-section-id="igbwkg" data-start="1009" data-end="1029">wpDiscuz activated</li>
<li data-section-id="1tgsryo" data-start="1030" data-end="1062">SiteGround Optimizer activated</li>
<li data-section-id="14iqn3e" data-start="1063" data-end="1101"><strong data-start="1065" data-end="1093">Combine JavaScript Files</strong> enabled</li>
</ul>
<p data-start="1103" data-end="1220">I tested the other JavaScript optimization settings and they do <strong data-start="1167" data-end="1174">not</strong> cause this problem. These can remain enabled:</p>
<ul data-start="1222" data-end="1290">
<li data-section-id="10j7iq" data-start="1222" data-end="1251"><strong data-start="1224" data-end="1251">Minify JavaScript Files</strong></li>
<li data-section-id="197v0yt" data-start="1252" data-end="1290"><strong data-start="1254" data-end="1290">Defer Render-blocking JavaScript</strong></li>
</ul>
<p data-start="1292" data-end="1408">So, if you're using wpDiscuz with SiteGround Optimizer and your comment fields suddenly disappear for guests, check:</p>
<p data-start="1410" data-end="1480"><strong data-start="1410" data-end="1480">Speed Optimizer → Frontend → JavaScript → Combine JavaScript Files</strong></p>
<p data-start="1482" data-end="1532" data-is-last-node="" data-is-only-node="">and make sure <strong data-start="1496" data-end="1531">Combine JavaScript Files is OFF</strong>.</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>spudart</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/troubleshooting/wpdiscuz-and-siteground/</guid>
                    </item>
				                    <item>
                        <title>Comment typing is erased after clicking</title>
                        <link>https://wpdiscuz.com/community/bug-reports/comment-typing-is-erased-after-clicking/</link>
                        <pubDate>Sun, 09 Aug 2026 13:10:06 +0000</pubDate>
                        <description><![CDATA[Hi guys,I&#039;m writing on behalf of my client (@doctorofcredit).We found out a bug.

Follow a link to any comment that is below the comments that are loaded in by default. For example:
Click ...]]></description>
                        <content:encoded><![CDATA[<p>Hi guys,<br /><br />I'm writing on behalf of my client (@doctorofcredit).<br /><br />We found out a bug.</p>
<ol>
<li>Follow a link to any comment that is below the comments that are loaded in by default. For example: https://stg-doctorofcreditcom-staging.kinsta.cloud/site-updates-requests/#comment-2303788</li>
<li>Click reply on one of the comments that are highlighted and type anything (but don't post the comment).</li>
<li>Scroll to the bottom and click load more comments.</li>
<li>Scroll back up and whatever you typed is gone forever.</li>
</ol>
<p>I was able to reproduce it with the latest version of wpDiscuz.</p>
<p>Let me know if you need any info.</p>
<p>Thanks!</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>accelera</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/bug-reports/comment-typing-is-erased-after-clicking/</guid>
                    </item>
				                    <item>
                        <title>Change &quot;Login&quot; Button to &quot;Login/Register&quot; or similar</title>
                        <link>https://wpdiscuz.com/community/troubleshooting/change-login-button-to-login-register-or-similar/</link>
                        <pubDate>Tue, 04 Aug 2026 19:56:15 +0000</pubDate>
                        <description><![CDATA[Hey Folks
I find the &quot;login&quot; button a bit confusing for new sign-ups. I&#039;d like to add &quot;register&quot; somehow?]]></description>
                        <content:encoded><![CDATA[<p>Hey Folks</p>
<p>I find the "login" button a bit confusing for new sign-ups. I'd like to add "register" somehow?</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>icoholic</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/troubleshooting/change-login-button-to-login-register-or-similar/</guid>
                    </item>
				                    <item>
                        <title>Console error when editing comments in closed threads</title>
                        <link>https://wpdiscuz.com/community/bug-reports/console-error-when-editing-comments-in-closed-threads/</link>
                        <pubDate>Mon, 03 Aug 2026 13:33:57 +0000</pubDate>
                        <description><![CDATA[Hi guys,
I&#039;m writing on behalf of my client (@doctorofcredit)
I found out that when a thread is closed for comments (using the native WordPress setting, see screenshot), editing any alread...]]></description>
                        <content:encoded><![CDATA[<p>Hi guys,</p>
<p>I'm writing on behalf of my client (@doctorofcredit)</p>
<p>I found out that when a thread is closed for comments (using the native WordPress setting, see <a href="https://i.imgur.com/WuRasOK.png" target="_blank" rel="noopener">screenshot</a>), editing any already published comment doesn't work. This is what happens:</p>
<ol>
<li>Close the comments section</li>
<li>Edit a comment from the frontend: <img src="https://i.imgur.com/IWqt6L1.png" /></li>
<li>The console shows this error: <img src="https://i.imgur.com/lLObOrL.png" /></li>
<li>And there's no way to edit the comment. Stays loading and shows a white box<img src="https://i.imgur.com/F4f6upO.png" /></li>
</ol>
<p>We've tried disabling all plugins and it looks like it doesn't make a difference. Any idea what's happening? Let us know if you need any further info.</p>
<p>&nbsp;</p>
<p>Thanks!</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>accelera</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/bug-reports/console-error-when-editing-comments-in-closed-threads/</guid>
                    </item>
				                    <item>
                        <title>Comment Error</title>
                        <link>https://wpdiscuz.com/community/bug-reports/comment-error-2/</link>
                        <pubDate>Fri, 31 Jul 2026 12:39:00 +0000</pubDate>
                        <description><![CDATA[Here is URLare using wpDiscuz - Emoticons and wpDiscuz - User &amp; Comment Mentioning also.There is issue when calling below function during post comment. I attached response which I am get...]]></description>
                        <content:encoded><![CDATA[<p>Here is URL https://inthegroove.eandi.org/2026/07/13/i-can-do-hard-things/<br /><br />We are using wpDiscuz - Emoticons and wpDiscuz - User &amp; Comment Mentioning also.<br /><br />There is issue when calling below function during post comment. I attached response which I am getting.<br /><br />action: wpdAddComment<br />wc_comment : &lt;span style="color: rgb(119, 119, 119);"&gt;test&lt;/span&gt;<br />submit: Post Comment<br />wpdiscuz_unique_id: 0_0<br />_wp_unfiltered_html_comment: ab2f83e9b7<br />wpd_comment_depth: 1<br />postId: 2216<br />wpdiscuz_nonce: 68c78bb9af<br />Here is error<br /><br />Unexpected Error! The query returned with an error.Unexpected Error! The query returned with an error.{"success":true,"data":{"redirect":0,"new_comment_id":268,"comment_author":"Riken Prajapati","comment_author_email":"rprajapati@eandi.org","comment_author_url":"","is_main":1,"held_moderate":0,"is_in_same_container":"1","wc_all_comments_count_new":"1","wc_all_comments_count_before_threads_html"<br /><br />Here is screen record https://www.awesomescreenshot.com/video/55011569?key=12e96cea9aa569e8e1a4ae1c11f8ea9e<br /><br />Here is website URL https://inthegroove.eandi.org/2026/07/13/i-can-do-hard-things/</p>]]></content:encoded>
						                            <category domain="https://wpdiscuz.com/community/"></category>                        <dc:creator>rikenp</dc:creator>
                        <guid isPermaLink="true">https://wpdiscuz.com/community/bug-reports/comment-error-2/</guid>
                    </item>
							        </channel>
        </rss>
		