| 开发者 | sapphireit |
|---|---|
| 更新时间 | 2026年11月19日 00:23 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
sit-cwm/v1. Everything the UI does is an
endpoint you can call yourself.post_status in wp_posts directly through $wpdb, without WordPress's
publishing functions, is not seen by the publish gate.sit_cwm_change_workflowsit_cwm_review_contentsit_cwm_approve_contentsit_cwm_approve_content plus WordPress publish_postsit_cwm_bypass_publish_gate (recorded every time it is used)sit_cwm_status_changed,
sit_cwm_can_transition, sit_cwm_transition_map,
sit_cwm_publish_gate_passes, sit_cwm_notification_recipients and more) so
it can be extended without editing its files.
/wp-content/plugins/sapphireit-editorial-workflow/, or
install it through Plugins → Add New → Upload Plugin.No, and that is deliberate. The workflow status and the WordPress post status are separate fields. Marking a post as Published in the workflow records that the editorial process is complete; a human still hits Publish. Keeping them apart is what lets a scheduled post keep its schedule while it is being approved, and lets an already-live article go back through a round of edits without disappearing from your site. With the publish gate on, it works the other way round too: content has to reach Approved before WordPress will publish it.
Yes, once you turn it on. Under Editorial Workflow → Settings → Publish gate, each content type has one of three modes:
post_status straight to the database is not covered. Imports
run from WP-CLI need --user=<an administrator> when the gate is set to
Enforce. Making content private is not gated.
No. Live content is never taken down: a published post that goes back through review stays published while it is edited. Content already scheduled is checked when its time comes; if it is not approved by then, it is put back to draft and its author sees a notice explaining why.
Only if you turn it on. Under Editorial Workflow → Settings → Email notifications you can switch on email for five events. All five are off until you turn them on.
By default, Administrators and Editors. Authors and Contributors cannot.
Approving is the WordPress capability sit_cwm_approve_content, so a
role-editor plugin (for example Members or User Role Editor) can give it to, or
take it from, any role. For finer rules ("only the assigned reviewer may
approve", say), the sit_cwm_can_transition filter has the final word on every
decision. Choosing roles from this plugin's own settings is not part of the free
plugin.
Not when "Prevent people from approving their own content" is ticked under Settings → Publish gate. Then nobody can move content they wrote to Approved, administrators included, and the author is not offered as its reviewer. Someone else with approval rights has to approve it. With the gate set to Enforce, administrators can still publish unapproved content, and that is recorded. "Own" means the author set on the post. Someone who rewrote a post they are not the author of can still approve it. The setting is off until you turn it on.
The sit_cwm_statuses and sit_cwm_transition_map filters replace the status
registry and the transition graph. Both results are validated, so a mistake in
your code cannot leave the plugin in a broken state. There is no settings screen
for editing statuses or building multiple workflows in version 1.0.
Yes. Any editorial content type (one with an admin UI, REST API support and the
editor feature) can be enabled in the settings. Back-office types such as shop
orders and coupons are not offered; developers can change the list with the
sit_cwm_available_post_types filter. The plugin uses post meta, so there is
nothing to migrate and nothing to convert.
Yes. In the classic editor the workflow controls appear in an Editorial Workflow box in the sidebar column. Changes there save immediately, independently of the Update button.
Deactivating changes nothing — your statuses, reviewers, due dates and history stay. Deleting the plugin keeps them too, unless you have ticked Delete all workflow data when the plugin is deleted under Editorial Workflow → Settings. With that option on, deleting the plugin permanently removes the activity table, workflow post meta, settings and capabilities.
In the plugin's own activity table, shown in the timeline in the sidebar (or the classic editor box). They are editorial notes, so they never appear on the front end and are not mixed in with your readers' comments.
Yes, at /wp-json/sit-cwm/v1/. Nine documented endpoints, all authenticated,
all with JSON schemas, and usable with application passwords.
No. AI use is declared, not detected. Whoever works on the content (a person in the editor, or an agent through the REST API) declares it as Human-written, AI-assisted or AI-generated. The plugin never inspects the text. It records each declaration in the activity log with the user who made it, and records the declared value again when the content is published. You can also set a default per content type in Workflow → Settings.
Yes. Give the agent its own WordPress user with the Author role and an
application password. It creates a draft through the WordPress REST API,
declares its AI use, and moves the draft to Review through
/wp-json/sit-cwm/v1/posts/{id}/workflow. An Author cannot approve, and with
the publish gate set to Enforce it cannot publish either, so a person always
signs off. The step-by-step recipe, with curl, n8n and MCP examples, is in
docs/AGENTS.md in the source repository at
https://github.com/rshalihin/sapphireit-editorial-workflow.
Users who can both view the activity history and manage workflows
(sit_cwm_view_activity and sit_cwm_manage_workflows), which by default
means administrators only. The same users can open the governance report. The
export is a CSV of the whole log, with spreadsheet formulas neutralised.
Only if you choose to. Your workflow data (statuses, reviewers, comments,
history) always stays in your WordPress database. The plugin loads nothing from
a CDN and sets no cookies of its own.
It includes the Freemius SDK. When an administrator first activates the
plugin, it asks whether to share some usage data with Freemius; you can click
Skip and the plugin works exactly the same. Nothing is sent unless an
administrator opts in, chooses to fill in the optional feedback form when
deactivating, or activates a licence for the paid Pro add-on. See Privacy
below for exactly what is shared.
Email notifications, when you turn them on, go out through WordPress's own
wp_mail(), the same way your site sends password-reset emails.
Yes. SapphireIT Editorial Workflow Pro is a separate, paid add-on for teams that coordinate many reviews: multi-stage approval, several workflows per content type or category, reviewer groups, checklist and sign-off gating, reminders and escalation, Slack and Microsoft Teams, per-user notification preferences and digests, and compliance exports with a tamper-evident log. This plugin is complete without it. Managers see a plain Pro link in the plugin's header and a few one-line hints on the plugin's own screens, each of which can be dismissed for good. They open https://sapphireitlabs.com/editorial-workflow/ in a new tab, where Pro is sold; nothing is bought inside WordPress. Nothing about Pro appears in the editor, in site-wide notices or on your site's front end, and none of it shows once Pro is active. This plugin never downloads or installs Pro: after buying, you get the Pro zip from the purchase email or your Freemius account and upload it under Plugins → Add New → Upload Plugin.
The editor sidebar, classic editor box and dashboard ship as compiled files in
assets/build/. The human-readable React source is in the src/ directory of
the public repository at
https://github.com/rshalihin/sapphireit-editorial-workflow. Run npm install
and then npm run build to rebuild the compiled files.
sit-cwm/v1, with actions and filters for extending the
plugin.