0+
October 1, 2026
September 16, 2026
CommentAura turns the native WordPress comment section into a modern discussion experience, without taking your data hostage.
Everything is stored in wp_comments and wp_commentmeta, exactly where WordPress puts it. Deactivate CommentAura and every comment, every reply, and every permalink still works. That is not a migration path — it is the architecture.
1. Zero lock-in. Your comments are native WordPress comments. No iframe, no external service, no account for your visitors, no export step if you leave. Uninstalling removes CommentAura’s own data and never touches a single comment.
2. It works without JavaScript. The comment thread is rendered on the server, in your page’s HTML. Search engines index it. Readers with slow connections see it. Screen readers read it. Reading, posting, editing, voting and reacting all work as plain form submissions. JavaScript only makes them faster: a half-kilobyte script loads with the page, and the rest — including WordPress’s own React library — loads only when a reader scrolls near the comments. You can switch it off in Settings.
3. No ads, no trackers, no third-party requests. CommentAura sends nothing to anyone. There is no analytics beacon, no CDN call, no “sponsored” content injected into your discussions.
Under CommentAura Import / Export:
wp_comments already, which is where CommentAura reads from. What those plugins keep in their own tables is the material around the comments, so CommentAura brings across the part that would otherwise be lost: subscriber lists and votes. Nothing is deleted from the other plugin, and running it twice does not double anything.Note that Disqus exports produced since 2019 contain no email addresses and no IP addresses for guest commenters. CommentAura preserves the display name, imports with an empty address, and tells you how many were affected rather than letting you find out from a support ticket.
A page with CommentAura active but no comment thread loads zero CommentAura assets. Not a small file — none.
A page with a thread loads about 10 KB (compressed) until a reader reaches the comments. Everything CommentAura itself ships comes to about 19 KB. WordPress’s own React library, which the interactive parts use, loads only when the comments come into view. Reaction faces are small images, about 1 KB each, loaded only when they are shown.
Rendering a thread costs a fixed number of database queries regardless of how many comments a post has, because replies are fetched per level rather than per comment. A post with 10 comments and a post with 10,000 cost the same.
The reaction faces are Fluent Emoji by Microsoft (https://github.com/microsoft/fluentui-emoji), used under the MIT licence. The licence ships with the plugin in assets/reactions/LICENSE.txt. The faces are bundled inside the plugin; nothing is loaded from Microsoft or anyone else.
commentaura/v1assets/src, next to its build in assets/buildThe scripts in assets/build are compiled from assets/src with @wordpress/scripts 30, using the webpack.config.js included in the plugin. To rebuild them, run npm install @wordpress/scripts@30 and then npx wp-scripts build in the plugin folder.
Everything described on this page is free and stays free. A separate paid plugin, CommentAura Pro, sold at https://waafaa.com/product/commentaura/, adds tools for the people who run the discussion: a moderation queue, rules, AI triage and analytics. It is never needed to use anything in this plugin.
/wp-content/plugins/.Optional settings live under CommentAura Settings in your admin menu. There are deliberately few of them.
No. This is the entire point of the plugin. Comments live in WordPress’s own tables the whole time. Deactivate CommentAura and your theme’s normal comment display returns, with every comment, reply, and link intact.
Yes. The thread is rendered into the page itself and sets no cookies, so a post with comments caches exactly like a post without them. Posting goes through WordPress’s own comment handler as a normal form submission, which is never served from a cache — so commenting works on a fully cached page without the plugin having to punch a hole in it.
Yes. CommentAura integrates with both the classic comments_template() path and the block editor’s core/comments block, and produces identical output through either.
No. Reading, posting, editing, voting and reacting all work with JavaScript disabled. With JavaScript, those happen without a page reload, replies open under the comment you are answering, and an unsent draft is kept in your browser.
No. There are no third-party requests of any kind.
Yes. Under CommentAura Settings Engagement Reactions you switch faces on or off, drag them into order, rename them, swap their icons and add your own, with a live preview beside the settings. One face on its own turns the bar into a simple Like button. Stored reactions are never lost: a face you switch off keeps its counts and brings them back when you switch it on again.
In CommentAura’s own tables, because they do not fit WordPress’s comment schema. Your comments themselves are never copied, shadowed, or moved.
No, and that is deliberate. CommentAura uses an invisible honeypot and a timing check instead, which cost your readers nothing.
A new, familiar look with 3D reactions. Comments now work without page reloads, and two bugs that made comments look lost are fixed.
commentaura_island_scripts (load an add-on’s own script the same lazy way) and commentaura_collapse_after.commentaura_reaction_icon and commentaura_reaction_set_for_post, and the commentaura_reaction_settings_rendered action for adding fields to the Reactions settings.Opens CommentAura to add-ons, and fixes one way a vote could count twice.
commentaura_loaded action. Add-ons receive the objects that own CommentAura’s callbacks, so they can replace one with remove_action().commentaura_vote_cast, commentaura_reaction_set, commentaura_subscription_confirmed and commentaura_subscription_removed. None of them passes who acted.commentaura_comment_action_types adds links to every comment’s action row, and commentaura_thread_args sets page size, sort order and whether held comments are shown.commentaura_enqueue_job action.Released 16 September 2026. The first public release.