Comments
List by status, approve, hold, spam or trash, and reply beneath a comment. Everything here asks for the same permission the site’s own moderation screen asks for.
Sites where the queue is the chore, and the answer to most of it is the same three sentences.
Each of these is carried by named operations that exist in the release you can download today. The ids under every answer are the calls involved — nothing here is a plan.
Comments are listed by status and each one’s status set individually, every change recorded.
SiteHelm
comment-list needs moderate_comments comment-status-set needs moderate_comments The reply is authored by the acting WordPress user and posted approved. There is no anonymous or impersonated comment path.
comment-reply needs moderate_comments The moderation queue: list by status, approve, hold, spam or trash, and reply beneath a comment.
Nothing extra to install. This module runs on core WordPress alone.
1 operations that only report. A read still asks WordPress for a capability against the object.
2 that change something — each one previewed as a diff, snapshotted, verified by reading the site back, and reversible from wp-admin.
Free, permanently. Nothing in this area moves into a paid tier later.
A reply is always attributed to the real account that made it. An agent cannot post as somebody else, or as nobody.
A reply is authored by the acting WordPress user and posted approved. There is no anonymous or impersonated comment path.
Everything here asks for moderate_comments — the same permission the site’s own moderation screen asks for.
Get the free plugin How a write is guarded
Which forms the site holds, what each one asks, its embed shortcode, and its most recent entries. Nothing here writes. That is a design decision, not a gap.
3 opsEvery area of the catalogue, by what it lets you do.
indexEvery operation on the site in one list, with capability, risk and rollback.
reference