Linux 软件免费装
Banner图

SapphireIT Editorial Workflow

开发者 sapphireit
更新时间 2026年11月19日 00:23
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

publishing editorial workflow reviewer content review approval workflow

下载

1.0.0 1.2.0

详情介绍:

AI can draft it. A human approves it. You can prove who approved what, and when. SapphireIT Editorial Workflow puts a real review step between writing content and publishing it, on the posts, pages and custom post types you already have: Every managed post gets a workflow status, an assigned reviewer, a due date, workflow comments and a complete activity history, managed from a Gutenberg sidebar, a classic editor meta box and an admin dashboard. Six statuses, one clear path: Draft → Writing → Review → Needs Changes → Approved → Published, with explicit paths for sending content back and for re-editing something that is already live. A Getting Started page (the Help link in the plugin's header, or Workflow → Getting Started) walks you through the setup steps, explains who can do what and what each setting does, and links to tutorials, docs and support. The page makes no external request until you click a link. What it does What it deliberately does not do Being straight about this matters more than a longer feature list: Who can do what Every change also requires WordPress' own permission to edit that specific post. By default administrators get everything, editors can review and approve, authors and contributors can move their own content up to Review, and subscribers get nothing. Only administrators can publish past the gate. Developers The plugin is built as a thin React client over a PHP workflow engine, and fires actions and filters at every lifecycle point (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.

安装:

  1. Upload the plugin to /wp-content/plugins/sapphireit-editorial-workflow/, or install it through Plugins → Add New → Upload Plugin.
  2. Activate it through the Plugins menu. Activation creates the activity table and grants the workflow capabilities to your existing roles.
  3. Go to Editorial Workflow → Settings and choose which post types the workflow applies to. Posts and pages are enabled by default.
  4. Open any post in the block editor and click the Editorial Workflow icon in the top-right toolbar. In the classic editor, use the Editorial Workflow box in the sidebar column instead.
Deactivating or deleting the plugin keeps your workflow data by default. To remove everything when the plugin is deleted, tick Delete all workflow data when the plugin is deleted under Editorial Workflow → Settings first; deleting the plugin then removes the activity table, the plugin's post meta, its options and its capabilities.

屏幕截图:

  • The activity timeline, showing content published while it was still at
  • The settings screen, open at the Publish gate section.
  • The admin dashboard, with server-side filtering, sorting and search.
  • The workflow box in the classic editor.
  • The governance report: how much was published after approval, publishing
  • The editor sidebar with declared AI use and the review confirmation an

升级注意事项:

1.2.0 Includes 1.1.0: publish gate, publication log, email notifications, declared AI use, approval confirmation, governance report, CSV export. All start off. Optional Pro add-on is bought on sapphireitlabs.com, not inside WordPress. 1.1.0 Adds an optional publish gate, publication logging, email notifications and a self-approval setting. All new options start off, so nothing changes until you turn them on. 1.0.0 First release. Activation creates the activity table and grants the workflow capabilities to your existing roles; no existing content is modified.

常见问题:

Does reaching "Published" publish my post?

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.

Can it stop unapproved content from being published?

Yes, once you turn it on. Under Editorial Workflow → Settings → Publish gate, each content type has one of three modes:

  • Off: publishing works as it always has. Publishing and unpublishing are still recorded in the activity history.
  • Log only: anyone allowed to publish still can, but publishing content that has not been approved is recorded as a publish without approval.
  • Enforce: content cannot be published or scheduled until it has reached Approved in the workflow. The editor offers Submit for Review instead of Publish, and blocked attempts on existing content are recorded.
Administrators can still publish, and that is recorded. The gate covers the block editor, the classic editor, Quick Edit, Bulk Edit, the REST API, WP-CLI, scheduled posts, and other plugins that publish through WordPress's own publishing functions. A scheduled post is checked again when its time comes, so content sent back for changes after it was scheduled does not go live. Code that writes 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.

Will turning on the gate unpublish anything?

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.

Does it send email?

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.

  • A reviewer is assigned: sent to the reviewer.
  • Content is submitted for review: sent to the assigned reviewer, or to nobody if no reviewer is assigned.
  • Changes are requested: sent to the author.
  • Content is approved: sent to the author.
  • A workflow comment is added: sent to the author and the reviewer.
Nobody is emailed about their own action, and nobody is emailed about content they are not allowed to read. The text of a workflow comment is only included for people allowed to read the workflow activity; everyone else is told that a comment was added, with a link to the content. Each email is written in the recipient's own language.

Who can approve content?

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.

Can someone approve their own content?

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.

Can I change the statuses or the order they go in?

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.

Does it work with custom post types?

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.

Does it work with the classic editor?

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.

What happens to my data if I deactivate it?

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.

Where are the workflow comments?

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.

Is there an API?

Yes, at /wp-json/sit-cwm/v1/. Nine documented endpoints, all authenticated, all with JSON schemas, and usable with application passwords.

Does the plugin detect whether content was written by AI?

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.

Can an AI agent submit content for review?

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.

Who can export the activity log?

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.

Does the plugin contact any external service?

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.

Is there a Pro version?

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.

Where is the source code for the JavaScript?

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.

更新日志:

1.2.0 1.1.0 1.0.0