Changelog do wpDiscuz – WordPress Comment Plugin

Correção

• Security. A commenter whose name contained a placeholder such as {TEXT} could make their comment run JavaScript for moderators viewing it while pending, and for every visitor once it was approved. Names with braces are now shown as plain text. Reported by Patchstack.

Correção

• The Facebook login button signed a visitor in through a client-side flow that trusted a Facebook user ID sent with the request, which was not tied to the access token it arrived with. Because an account's Facebook ID doubles as its user name and the account's email address was derived from that ID when Facebook returned none, this could sign a request in as another visitor's account. Facebook login now always uses the server-side OAuth2 flow, which reads the account from the token's own owner…

Correção

• A comment whose image was refused for its width or height was saved anyway, and the error message was empty. The wpdiscuz_mu_preupload action now fires before the comment is saved, so a file it refuses stops the comment.
• The on/off switches on the settings page showed their state by color alone and could not be used from the keyboard. They now show a cross when off and a check mark when on, and can be reached with Tab and toggled with Space. Switches in addon settings tabs get the same fix.

Correção

• The comment bubble and the live comment update never showed comments posted without an email address to visitors who have no email address themselves, visitors who have not commented yet and guests who comment anonymously. A visitor's own new comments are left out of these updates by their email address, and an empty address matched every comment posted without one, so anonymous commenters were hidden from each other and from everyone who has not commented. The email address is now only used…
• The new comment message of the comment bubble described the newest comment of the post, even when the bubble was not notifying about that comment, the visitor's own comment or one already on their screen. It now describes the newest comment the visitor is being notified about, and is left out of the response when that comment cannot be read, a private comment an addon keeps from the visitor for instance, where it used to be built from nothing.
• The Cookies Consent and Agreement checkbox labels were printed on the comment form, and on the comment edit form, without being escaped. The labels are cleaned when the form is saved, but that only applies to what is saved from then on, so a label stored before v7.6.13 kept whatever markup it was given and was still printed as markup to every visitor. The labels are now filtered where they are printed, the agreement label by the same rules its own save path allows and the cookies consent label…
• The minimal theme carried none of the styles for the "powered by wpDiscuz" line. That stylesheet loads instead of the default theme one rather than alongside it, so the wpDiscuz link was shown permanently and unstyled, and the info icon beside it toggled nothing a reader would notice.
• The HTML field printed its markup on the comment form without being filtered. The markup is cleaned when the form is saved, but that only applies to what is saved from then on, so an HTML field stored before v7.6.13 kept whatever markup it was given and was still printed as markup to every visitor, and cloning a form or importing one copies such a value across untouched. It is now filtered where it is printed, by the same rules its own save path allows, so a field that still holds script no…
• The titles of the comment editor toolbar buttons were passed through the translation function a second time where they are printed, against wpDiscuz's own text domain. The titles are already translated by that point, so the title of a button added by an addon was looked up in a text domain it does not belong to, and a title the addon had already escaped was escaped a second time, which shows the escape sequence itself to the reader in any title holding an apostrophe or an ampersand. The titles…
• The icon height and the tab title of each card on the settings dashboard, and the icon class of the file attachment button on the comment form, were printed without being escaped. All three are supplied through settings arrays and filters an addon can extend, so a value holding a quote or a tag was printed as markup rather than as the value it was meant to be. They are now escaped where they are printed, as the values beside them already were.
• Replies from guests were rejected as spam on sites where an anti-spam plugin fills in its own hidden fields with JavaScript once the page loads, La Sentinelle for instance, while the first comment posted through the main form went through. A reply form is built by copying the markup of a hidden form on the page, and markup carries the values the page was served with rather than the ones those scripts set, so every reply went out with an untouched honeypot and timer. A second comment from the…
• Every comment a guest posted was rejected while "Detect spambots posting comments" is enabled in All In One Security, stored as spam or discarded depending on its settings. That option rejects a guest comment that arrives without its hidden antibot keys, and it adds those keys only to the comment form WordPress prints itself. wpDiscuz now prints them in its comment, reply and inline feedback forms whenever the option is on. As with the WordPress comment form, a page served from a full-page…
• Inline feedback comments were sent without the fields anti-spam plugins add to comment forms. The feedback form is loaded after the page, and those plugins only add their fields to the comment form, so a plugin that treats a missing field as spam, La Sentinelle for instance, rejected every feedback comment from a guest. A feedback comment is now sent with the Akismet and La Sentinelle fields of the comment form on the same page. The new wpdiscuz_antispam_field_prefixes filter adds the input…
• Sending a comment again after it was stored as spam showed WordPress's "Duplicate comment detected" error instead of wpDiscuz's message for a rejected comment. WordPress refuses a comment identical to one it has already stored, spam included, and that refusal was passed on to the commenter as it was. The retry now gets the rejected comment message, "Your comment was not published." by default, and nothing new is stored. The wpdiscuz_comment_rejected_response filter runs for the retry as well…

Correção

• Vote buttons showed guests the wrong state and tooltip when "Allow Guests to Vote for Comments" is disabled (buttons looked active, or blamed the visitor's IP address, then clicking answered "You Must Be Logged In To Vote").
• Guests whose IP address is removed by a privacy plugin or a pre_comment_user_ip filter all shared a single post-rating identity. The first such guest locked the rating for every other one, or overwrote it when "Enable rate editing" is enabled, and they were all counted as one rating in the post average and rating count. Guest rating now requires a usable IP address, the same way comment voting has since 7.6.67.
• The "Enable rate editing" form setting never reached the front-end script, so the confirmation before changing an existing rating was never asked. The form settings were read one line before they were loaded.
• Pages displaying more than one Article Rating repeated the wpd-post-rating id and sent every rating click to the post of the page. Each rating is now a .wpd-post-rating element carrying its own post ID, so any eligible post can be rated wherever the wpDiscuz script is loaded. The legacy id remains on the page's own rating at the first checked built-in position, or on a manual placement when no position is checked.
• The Article Rating schema was repeated whenever the page's own rating appeared more than once. It now follows the rating that owns the legacy id. The template tag's third argument and the shortcode's page_rating attribute can explicitly give or deny a manual placement that ownership when the settings cannot determine it.
• "Display ratings on non-singular pages" loaded a stylesheet that did not style the Article Rating block. The standalone rating styles now cover it and use the configured star colours, allowing template-tag and shortcode ratings to display read-only on archives, listings, and other pages where the wpDiscuz script is not loaded when that option is enabled.
• Selecting comment attachments more than once replaced the files already selected. New selections now accumulate up to the configured limit, and duplicate files are ignored.

Correção

• Logging in with X (Twitter) ended on a blank page showing "0" instead of signing the visitor in. The callback URL and the requested scopes were placed in the authorization request without being URL-encoded.
• The Stick and Close actions under a comment on the WordPress Comments page never completed. The requests carried no wpDiscuz nonce, so they were rejected with "Nonce is invalid." and the button spinner kept turning. Both buttons also restore their icon now when a request fails, instead of spinning forever.

Correção

• Main and inline comment forms now show a moderation plugin's rejection explanation while keeping the standard wpDiscuz spam or trash phrase when no plugin provides one.
• Inline comments stored as spam or trash no longer create subscription records or send mention notifications.
• Comment insertion failures, including duplicate-comment and flood checks, now return a valid AJAX error instead of terminating the request with an unusable response.
• Plus signs and encoded data are preserved in inline commenter names and email addresses, the comment-author email cookie, and submitted website URLs.

Correção

• Registered users can vote independently when they share an IP address, while registered authors are still blocked from voting on their own comments with the correct message.
• Guests no longer fall into one shared voting identity when privacy software removes visitor IP addresses. Affected guests must log in to vote even when guest voting is enabled.
• Vote totals remain visible when voting buttons are hidden by self-vote restrictions, and wpdiscuz_show_vote can now reliably hide other eligible voting components.
• Disabling comment voting now blocks the vote action through both native WordPress AJAX and the custom wpDiscuz AJAX endpoint.

Correção

• A settings search result for an option inside a collapsed accordion scrolled to the top of the page instead of to the option, because the scroll measured the option row while it was still hidden and a hidden row reports a position of zero.
• Clicking a second settings search result belonging to an accordion that was already open closed it, because the accordion was toggled rather than opened.
• The Reviews add-on teaser said the WooCommerce ratings import skips guest reviews. The import includes them.
• The Reviews add-on teaser described the review gate as limiting who may submit a review. It sets submitted reviews to pending and does not vet users.
• The comment editing information printed only the edit icon, without the name of the editor and the time of the edit, on websites whose phrases table does not contain the "Last edited %1$s by %2$s" phrase.
• Visitors whose email address contains an apostrophe could not subscribe to comments. The address was checked for validity before the backslash WordPress puts in front of the apostrophe was removed, so the subscription form rejected it and reported nothing.
• Comment subscriptions were looked up by matching the email address as a SQL pattern instead of comparing it exactly. Since the % and _ characters are allowed in an email address, a subscriber using such an address matched the other subscribers of the same post, received their unsubscribe link, and removed their comment thread subscriptions.

Correção

• Searching the settings page for a term containing an apostrophe returned no results.

Correção

• An issue with comment editing( current_user_can('moderate_comments') ) when comments are closed

Correção

• Imported phrase files were not sanitized on upload, unlike phrases saved from the Phrases settings page.
• The comments block editor preview could be triggered on the front-end without an editing capability check.

Correção

• Missing escaping issues
• Internal images were missing in the combined version of the CSS

Correção

• Attachment delete AJAX dereferences a missing comment before validation
• Bubble live-update AJAX renders arbitrary comment IDs without per-comment authorization
• Post-rating AJAX accepts ratings outside the five-star range
• Show-replies AJAX dereferences an invalid comment ID without validation

Correção

• Some addons are deactivated after an update on some sites/hosting providers

Correção

• An issue with wpDiscuz nonce validation
• An issue with WooCommerce integration (The form was not rendered even if the user has bought a product)
• An issue with wpDiscuz Ratings regeneration in the tools page
• The issues with wpDiscuz tools
• An issue with email notifications checking - wc_msg_ip_mismatch
• An issue when a comment was approved after editing

Correção

• An issue with wpDiscuz nonce validation

Correção

• An issue with wpDiscuz nonce validation

Correção

• The images in the comments were displayed twice.

Correção

• Prevent adding unnecessary statistics on comment deletion.
• Guests can't vote on guest comments.
• Issue with adding nonce in cookies that leads to an issue with nonce verification.

Correção

• An issue with inline commenting in Elementor

Correção

• Issues with PHP 8.x versions

Correção

• Email notification issue for comments made by anonymous users.

Correção

• Duplicated Gravatars for anonymous users.

Correção

• An issue during the plugin deactivation
• An issue with 'Enable subscription bar' option
• An issue with caching