评论- wpDiscuz
| 开发者 | gVectors Team |
|---|---|
| 更新时间 | 2026年9月11日 22:28 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
标签
下载
1.0.0
7.6.46
7.6.66
7.6.68
7.6.69
7.6.70
2.0.2
2.0.3
2.0.4
2.0.8
2.1.0
2.1.1
2.1.2
2.1.4
2.1.5
2.1.6
2.1.7
2.2.0
2.2.10
2.2.2
2.2.3
2.2.5
2.2.6
2.2.7
2.2.9
3.0.0
3.0.1
3.0.2
3.0.3
3.0.6
3.0.7
3.0.8
3.1.0
3.1.3
3.1.4
3.2.0
3.2.3
3.2.6
3.2.7
3.2.8
4.0.0
4.0.10
4.0.11
4.0.12
4.0.13
7.0.5
7.0.6
7.0.9
7.1.0
7.1.1
7.1.2
7.1.4
4.0.2
4.0.7
4.1.0
4.1.1
4.1.3
4.1.4
5.0.0
5.0.1
5.0.2
5.0.3
5.2.2
7.0.2
7.1.3
7.2.0
2.0.0
7.6.67
2.1.8
7.6.30
3.2.5
5.3.1
7.6.5
5.2.1
5.3.4
7.6.53
7.6.54
7.2.2
3.0.9
5.1.2
5.1.4
7.3.17
7.3.19
7.4.1
7.5.1
7.3.6
7.5
7.0.8
7.6.11
7.3.15
7.3.12
7.3.13
7.3.14
7.3.18
7.3.8
7.6.1
7.6.2
7.6.3
5.1.3
2.2.4
7.3.0
7.3.11
7.5.3
7.6.23
7.6.8
3.2.1
4.0.4
4.0.5
5.1.0
5.1.7
5.3.5
7.3.9
7.4
7.6.17
7.6.18
7.6.26
1.0.2
1.0.6
1.0.7
7.0.0
7.6.57
2.0.1
5.1.1
5.1.5
7.3.16
7.3.20
7.5.4
7.6.10
7.6.28
7.6.29
7.6.31
7.6.33
7.6.35
7.6.4
7.6.7
7.6.9
1.0.4
1.0.5
2.0.6
2.0.7
2.0.9
2.2.8
3.0.4
3.1.1
3.1.2
3.2.4
5.0.4
5.0.5
5.0.7
7.2.1
7.3.2
7.5.2
2.0.5
4.0.3
7.0.10
7.6.38
7.6.39
7.6.40
7.6.41
7.6.42
2.2.1
3.2.2
4.0.9
7.3.10
7.3.3
7.6.19
7.6.22
7.6.43
7.6.24
7.6.55
7.6.58
7.6.27
7.6.50
7.6.44
7.6.13
7.6.45
1.0.3
5.3.3
7.6.48
7.6.49
1.0.9
1.0.8
5.0.6
1.0.1
2.1.9
7.6.36
4.0.1
4.0.14
4.0.15
4.0.8
7.0.1
7.0.3
7.3.5
7.4.2
7.6.0
7.6.12
7.6.14
7.6.25
7.6.32
7.6.34
7.6.37
7.6.6
7.6.60
7.6.61
7.6.62
4.0.6
4.1.2
5.3.6
7.3.4
7.6.21
7.6.51
7.6.56
7.6.63
3.0.5
5.2.0
5.3.2
7.0.4
7.6.52
7.6.59
7.6.64
7.6.65
2.1.10
5.1.6
5.3.0
7.0.7
7.1.5
7.3.1
7.3.7
7.6.15
7.6.16
7.6.20
7.6.47
详情介绍:
wpDiscuz transforms the native WordPress comment system into a fast, modern, and interactive discussion experience while keeping your comments and data in your own WordPress database.
Add AJAX comments, live comments, threaded comments, comment voting and rating, inline comments, comment subscriptions, social login, custom comment forms, lazy loading, and modern engagement features without moving your community to an external commenting service.
wpDiscuz is a powerful Disqus alternative for WordPress and is designed for blogs, news websites, magazines, communities, membership sites, and WooCommerce stores.
- wpDiscuz Demo: https://wpdiscuz.com/
- Documentation: https://wpdiscuz.com/docs/
- Support Forum: https://wpdiscuz.com/community/
- GDPR Information: https://wpdiscuz.com/gdpr/
- wpDiscuz Add-ons: https://wpdiscuz.com/addons/
- Three modern WordPress comment layouts
- Comment sorting by newest, oldest, and most voted comments
- Comment editing for logged-in users and guests
- Automatic URL and image embedding in comments
- Long comment collapsing with "Read More" button
- WordPress date format integration
- Quick Tags support for comments
- Highlighting new comments since last visit
- Comment access control by user roles
- 设置在首页加载时加载所有评论
- 内置 Gravatar 缓存
- Sticky comments support
- Closed comment threads support
- User follow functionality
- Built-in comment and author caching system
- Responsive interface for desktop and mobile devices
安装:
Important
If you use a cache plugin or CDN, clear all caches after installing or updating wpDiscuz so the latest plugin assets are loaded.
Installation
- Upload the plugin folder to the
/wp-content/plugins/directory. - Activate the plugin through the Plugins menu in WordPress.
- Open the wpDiscuz menu item in your WordPress admin dashboard to configure your comment system.
屏幕截图:
常见问题:
What is wpDiscuz?
wpDiscuz is a WordPress comments plugin that enhances the native WordPress comment system with a modern, interactive commenting experience while keeping comments in your own database.
What is the best WordPress comments plugin?
wpDiscuz is one of the most popular WordPress comments plugins, combining AJAX comments, live commenting, inline comments, comment voting, subscriptions, custom comment forms, social login, and other engagement tools while keeping comments in the native WordPress database.
How do I enable AJAX comments in WordPress?
Install and activate wpDiscuz to add AJAX-powered comment posting and interactive comment loading without requiring visitors to reload the page after every action.
How do I replace Disqus with WordPress comments?
wpDiscuz is a Disqus alternative that uses the native WordPress comment system, allowing you to keep comments stored in your own WordPress database rather than relying on an external commenting service.
What happens to my existing WordPress comments?
Existing comments remain in the WordPress database and are displayed automatically by wpDiscuz. Uninstalling wpDiscuz does not remove your existing WordPress comments.
Where are wpDiscuz comments stored?
Comments are stored locally in your own WordPress database using the native WordPress comment system.
Does wpDiscuz support threaded comments and nested replies?
Yes. wpDiscuz supports multi-level threaded comments and nested replies to keep long discussions organized and easier to follow.
Can users subscribe to comments and replies?
Yes. wpDiscuz includes comment subscription and notification options so users can follow discussions and receive updates about new activity.
Can I create a custom WordPress comment form?
Yes. wpDiscuz supports custom WordPress comment forms and custom fields for different post types, products, pages, communities, and discussions.
Does wpDiscuz support inline comments?
Yes. wpDiscuz supports inline commenting and inline feedback, allowing visitors to interact directly with content inside a post.
Does wpDiscuz work with WooCommerce?
Yes. wpDiscuz can improve WooCommerce product discussions with AJAX-powered comments, ratings, and engagement features. Advanced WooCommerce review and rating functionality is available through the wpDiscuz - Reviews add-on.
Does wpDiscuz lazy load comments?
Yes. wpDiscuz can lazy load comments on scroll and also provides AJAX-based loading options to reduce the amount of comment content loaded during the initial page request.
Is wpDiscuz GDPR compliant?
wpDiscuz provides GDPR-related tools and guidance for site owners. See the wpDiscuz GDPR documentation for configuration details and information relevant to your site.
What should I do if I use a caching plugin or CDN?
After installing or updating wpDiscuz, clear your WordPress cache and purge your CDN cache so the latest plugin assets are loaded.
How do I protect WordPress comments from spam?
wpDiscuz includes built-in anti-spam features and works with WordPress comment moderation. It can also be used alongside Akismet and compatible CAPTCHA solutions for additional protection.
Does wpDiscuz affect site performance?
wpDiscuz includes AJAX comment loading, lazy-loading options, built-in comment and author caching, Gravatar caching, and other performance-focused features. Actual performance depends on factors such as traffic, comment volume, hosting, caching configuration, and enabled features.
Does wpDiscuz work with Gutenberg and the WordPress block editor?
Yes. wpDiscuz provides a Comments block for the WordPress block editor, so you can add wpDiscuz comments to Gutenberg-based content.
更新日志:
IMPORTANT!
Please remember to delete all caches and purge CDN after the update.
Comments - wpDiscuz v7.6.70 - 11.09.2026
- Fixed: 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").
- Fixed: Guests whose IP address is removed by a privacy plugin or a
pre_comment_user_ipfilter 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. - Fixed: 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.
- Added: The
wpdiscuz_post_rating()template tag prints the standalone Article Rating anywhere in a theme or page builder template, andwpdiscuz_get_post_rating()returns the same HTML. Pass a post ID to display that post's rating with its own form settings, or pass false as the second argument for read-only output. WooCommerce products continue to use WooCommerce's own rating. - Added: The
[wpdiscuz_post_rating]shortcode provides the same output for page builders and content editors, withpost_id,can_rate, andpage_ratingattributes. Disable unneeded built-in Article Rating positions to avoid displaying the rating more than once. - Fixed: Pages displaying more than one Article Rating repeated the
wpd-post-ratingid and sent every rating click to the post of the page. Each rating is now a.wpd-post-ratingelement 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. - Fixed: 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_ratingattribute can explicitly give or deny a manual placement that ownership when the settings cannot determine it. - Fixed: "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.
- Fixed: 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.
- Fixed: 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.
- Fixed: 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.
- Improved: The Google social login button now uses the official multicolor Google "G" logo.
- Added: The
wpdiscuz_comment_rejected_responsefilter lets moderation plugins provide a clear explanation when a new comment is stored as spam or trash. - Fixed: 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.
- Fixed: Inline comments stored as spam or trash no longer create subscription records or send mention notifications.
- Fixed: Comment insertion failures, including duplicate-comment and flood checks, now return a valid AJAX error instead of terminating the request with an unusable response.
- Fixed: Plus signs and encoded data are preserved in inline commenter names and email addresses, the comment-author email cookie, and submitted website URLs.
- Improved: The Phrases screen now identifies the spam and trash rejection fields separately.
- Improved: Voting buttons now stay visible in a disabled state for visitors who cannot vote on a comment, instead of being hidden. Hiding them left visitors unaware that the site has voting at all. The buttons carry a
wpd-vote-disabledclass and a tooltip with the reason, and clicking one still shows the existing message. - Added: The
wpdiscuz_hide_readonly_vote_buttonsfilter hides those buttons again, restoring thewpd-vote-readonlymarkup used before this release. - Security: The Google Client Secret is no longer included in the front-end JavaScript settings.
- Fixed: 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.
- Fixed: 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.
- Added: The
wpdiscuz_deny_vote_from_same_ipfilter lets site owners show voting buttons and allow votes for same-IP guest comments without changing registered-user voting. Guests on that IP still share one voting identity. - Fixed: Vote totals remain visible when voting buttons are hidden by self-vote restrictions, and
wpdiscuz_show_votecan now reliably hide other eligible voting components. - Fixed: Disabling comment voting now blocks the vote action through both native WordPress AJAX and the custom wpDiscuz AJAX endpoint.
- Improved: The voting settings now explain the global request gate and IP-based guest identity, including shared-IP behavior and the login requirement when no visitor IP is available.
- Note: Existing vote records and totals are preserved; this update changes future voting behavior and does not recalculate historical votes.
- Security: Fixed an unauthenticated comment disclosure vulnerability in AJAX comment loading. Reported by Jakub Herman via WPScan.
- Added: The Reviews add-on teaser lists the new "Allow guest reviews" option.
- Improved: The settings search shows which email a result belongs to. Eight options are labelled "Email subject" and eight "Email content", so a search for "email" returned an indistinguishable list; every result now carries its section, such as "Subscription Type: Post new comment".
- Improved: The settings search also matches those section names, so searching for "mentioned" or "follow confirmation" finds the email templates belonging to them.
- Improved: A settings search result for one of the email templates now opens the accordion holding it, instead of leaving the option hidden behind a collapsed panel.
- Fixed: 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.
- Fixed: Clicking a second settings search result belonging to an accordion that was already open closed it, because the accordion was toggled rather than opened.
- Fixed: The Reviews add-on teaser said the WooCommerce ratings import skips guest reviews. The import includes them.
- Fixed: 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.
- Added: wpdScrollToOption() is exposed on the window object, so an add-on whose options sit in an accordion of its own can scroll to an option once it has opened it.
- Fixed: 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.
- Improved: Saved phrases are now merged into the default phrases instead of replacing them. Phrases introduced by a plugin update are no longer printed empty on websites where the phrases table has not been filled with them yet, which happens when the plugin is updated without the WordPress dashboard ever being opened.
- Improved: The comment editing information is not printed at all when its phrase is empty, instead of printing a lone edit icon which tells nothing about who edited the comment and when.
- Removed: The Phrases settings page had fields for the VKontakte and Odnoklassniki share button titles. Those share buttons are no longer part of wpDiscuz and the two phrases behind the fields were neither defined nor saved anywhere, so the page raised an "Undefined array key" warning on every load.
- Fixed: 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.
- Fixed: 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.