Reactions
| 开发者 |
pento
georgestephanis |
|---|---|
| 更新时间 | 2026年10月31日 00:45 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
reaction comment type), so they
inherit your existing comment moderation. They're also automatically excluded from your theme's
comment list, comment feeds, things like the Recent Comments widget, and the Comments screen in
wp-admin, so they never show up twice or inflate your comment count.
Additional background is at https://make.wordpress.org/core/2016/03/07/reactions/.
Settings
Settings > Discussion gains a Reactions section:
- Default reactions -- emoji shown under every post, even before anyone has reacted, so visitors can react in one click.
- Emoji picker -- turn off to hide the picker button, restricting reactions to the default set above.
- Skin tones -- turn off to record reactions with the default skin tone.
- Reacting -- require visitors to be logged in. Reaction counts stay visible to everyone; logged-out visitors get a link to the log in screen instead of a reaction button.
- Custom reaction icons -- upload your own SVG icons to use as reactions alongside emoji, registered through the Icon Registration API added in WordPress 7.1.
安装:
- Upload the plugin files to
/wp-content/plugins/react, or install through the WordPress plugins screen directly. - Activate the plugin through the 'Plugins' screen in WordPress.
- Optionally, visit Settings > Discussion to choose your default reactions.
常见问题:
Will reactions clutter up my comments?
No. Reactions are stored as comments, but they're filtered out of your theme's comment list, comment feeds, and comment counts, so they only appear as reactions. They're kept out of Comments in wp-admin too. To find one -- say, to delete it -- choose "Reactions" from the comment type dropdown on that screen.
Can visitors react without logging in?
Yes, by default. If you'd rather they didn't, tick "Users must be logged in to react" in Settings > Discussion. Counts stay visible to everyone either way.
Can I limit which emoji people use?
Yes. Set the reactions you want under "Default reactions", then untick "Let visitors react with any emoji". Only your chosen set will be offered and accepted.
Can I use my own icons instead of emoji?
Yes -- upload SVG icons under "Custom reaction icons" (this needs WordPress 7.1 or newer). They appear as one-click reactions under your posts, alongside your default emoji.
Why was my SVG icon rejected?
WordPress sanitizes registered icons quite aggressively, and only keeps <svg>, <path>
and <polygon> elements. It also strips stroke attributes.
That means outline-style icon sets render as solid shapes, and icons drawn with shapes like
<circle> or <rect>, or wrapped in a <g> group, would come out blank or misplaced.
Rather than let that happen silently, uploads that wouldn't survive are rejected with an
explanation. Flatten your artwork to filled paths in your vector editor first.
Your file is never added to your media library, and SVG uploads stay disabled site-wide -- only
the sanitized icon markup is kept.
Where can I report a bug or contribute?
Development happens at https://github.com/pento/react.
更新日志:
- Reaction tallies are now counted by the database and cached per post, instead of every reaction on a post being loaded on each page view. Both the reactions under a post and the REST endpoint use the same cached tallies.
- Reactions no longer show up in wp-admin's Comments screen, the dashboard's Activity widget, or the comment counts in the posts list. They can still be listed by choosing "Reactions" from the Comments screen's comment type dropdown.
- Added a Reactions section to Settings > Discussion: configurable default reactions, an optional emoji picker, a skin tone toggle, an option to require visitors to be logged in, and custom SVG reaction icons registered via the WordPress 7.1 Icon Registration API. Every setting is enforced on the server, and changing one never strands reactions that have already been left.
- Fixed a click on the reactions container's own padding being treated as a click on a reaction, which sent a malformed request.
- Fixed a reaction toggled back off keeping a stale count until the next page load.
- Swaps the hand-rolled emoji picker for the third-party
emoji-picker-element web component
(Apache-2.0 licensed, compatible with this plugin's GPLv2-or-later license via the "or later"
clause). This drops support for browsers old enough to lack
document.addEventListener(). Breaking: removes thereact_categoriesfilter -- the new picker manages its own category grid internally, with no equivalent per-category customization hook. - Fixes reactions always being attributed to "Anonymous", even when the reacting user is logged in.
- Adds the ability to remove a reaction by reacting again with the same emoji (a toggle), for
both logged-in users and logged-out visitors (via a per-browser identifier kept in
localStorage, never sent except with a reaction request). - Adds a GitHub Actions CI workflow (PHPUnit across PHP 8.1-8.3, phpcs, JS lint/tests on every push/PR) and a new JS test suite.
- Fixes WP 7.1 / PHP 8.5 compatibility issues.
- Fixes a stored-XSS vector where unescaped reaction comment content could be rendered on the front end.
- Fixes reactions being counted twice (in both the reaction widget and the normal comment count/list/feeds) by filtering them out of default comment queries, with a cache to avoid a per-post-per-page-load COUNT query.
- Fixes two DOM-based injection issues where post content containing an element with a reused,
unreserved ID could be picked up by the reaction picker's
getElementById()lookups and treated as trusted markup. - Adds
react_reaction_created,react_reaction_removedandreact_reaction_count_invalidatedactions, andreact_reaction_markup,react_reaction_count_cache_group, andreact_reaction_count_cache_ttlfilters. - Removes a committed, unused 683KB raw build artifact.
- Adds a WordPress Playground blueprint for a one-click demo.