SapphireIT Editorial Workflow
| 开发者 | sapphireit |
|---|---|
| 更新时间 | 2026年10月18日 16:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- A real state machine. Only the moves in the transition graph are possible. Nobody jumps a draft straight to approved, whatever their role.
- Server-side enforcement. Every transition is re-checked in PHP against the graph, the capability map and the post's current stored status. The editor UI shows you what you can do; it does not decide it.
- Six dedicated capabilities, granted to roles at activation and editable with any capability-management plugin. No hard-coded role checks.
- Reviewer assignment and due dates, with an "overdue only" filter computed in your site's timezone.
- Workflow comments that stay in the editorial log and never appear on the front end.
- A complete activity history in a dedicated indexed table: who changed what, when.
- Conflict protection. If two editors act on the same post at once, the second one is told the post moved instead of silently overwriting the first.
- An admin dashboard with server-side search, filtering, sorting and pagination, row actions, and bulk actions across up to 100 posts.
- A documented REST API under
sit-cwm/v1. Everything the UI does is an endpoint you can call yourself. - Works with what you have. Posts, pages and any custom post type, through post meta. No custom post type of its own, and nothing to migrate.
- It does not send email. Assigning a reviewer notifies nobody in version 1.0.
- It does not publish anything. Reaching the "Published" workflow status records that the editorial process finished — it does not touch the WordPress post status. Publishing stays a deliberate action by a human. The two are separate fields on purpose, so that scheduled posts keep their schedule and live content can be re-edited without being unpublished.
- No Slack, no editorial calendar, no multiple workflows, no rules engine. Those are on the roadmap, not hidden behind an upsell in this plugin.
- Draft, Writing, Review —
sit_cwm_change_workflow - Needs Changes —
sit_cwm_review_content - Approved —
sit_cwm_approve_content - Published —
sit_cwm_approve_contentplus WordPresspublish_post
sit_cwm_status_changed,
sit_cwm_can_transition, sit_cwm_transition_map and more) so it can be
extended without editing its files.
安装:
- Upload the plugin to
/wp-content/plugins/sapphireit-editorial-workflow/, or install it through Plugins → Add New → Upload Plugin. - Activate it through the Plugins menu. Activation creates the activity table and grants the workflow capabilities to your existing roles.
- Go to Editorial Workflow → Settings and choose which post types the workflow applies to. Posts and pages are enabled by default.
- 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.
屏幕截图:
常见问题:
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.
Does it send email when I assign a reviewer?
Not in version 1.0. Notifications are on the roadmap. The
sit_cwm_reviewer_assigned action fires on every assignment, so a few lines in
a site plugin can send whatever you need today.
Can I change who is allowed to approve content?
Yes. The plugin adds six ordinary WordPress capabilities (sit_cwm_*), so any
role or capability manager can move them around. For finer rules — "only the
assigned reviewer may approve", say — the sit_cwm_can_transition filter has
the final word on every decision.
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/. Eight documented endpoints, all authenticated,
all with JSON schemas, and usable with application passwords.
Does the plugin contact any external service?
No. It makes no remote requests, loads nothing from a CDN, sets no cookies of its own and collects no usage data. Everything stays in your WordPress database.
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.
更新日志:
- Initial release.
- Six-status editorial workflow with a validated transition graph and rollback paths.
- Server-side transition and permission enforcement; the UI never decides.
- Six dedicated capabilities with sensible default role grants.
- Reviewer assignment, due dates and an overdue filter.
- Workflow comments and a full activity history in a dedicated indexed table.
- Optimistic concurrency: conflicting edits are rejected, not silently merged.
- Gutenberg sidebar with an activity timeline.
- Classic editor support: the same workflow controls in an Editorial Workflow meta box.
- Admin dashboard with server-side filtering, sorting, pagination, row actions and bulk actions.
- Settings screen for choosing workflow-enabled post types.
- REST API under
sit-cwm/v1, with actions and filters for extending the plugin.